Infor CloudSuite and FedEx integration

What moves between them

Shipment tracking events flow from FedEx into Infor CloudSuite. When a FedEx shipment is created, picked up, in transit, or delivered, ml-connector updates the matching purchase order line in CloudSuite with the tracking number, current location, and estimated delivery date. Goods receipt records in CloudSuite are marked received when FedEx confirms delivery. Optional reverse flow: when a CloudSuite PO is created or modified with shipment instructions, ml-connector can query FedEx for matching shipments and link them to the PO. The sync runs on a schedule aligned with your receiving window, or in near-real-time if FedEx webhooks are enabled.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the CloudSuite .ionapi file (base URL, tenant ID, OAuth endpoint, client ID/secret) and the FedEx API Key and Secret. On the FedEx side, it caches bearer tokens for up to 1 hour to stay within the 3-tokens-per-second auth limit, and backs off on 403 responses with exponential jitter. On the CloudSuite side, it refreshes the OAuth2 token before expiry (tokens last 1 to 24 hours per tenant configuration) and polls the PPS100MI and PPS200MI APIs for PO headers and lines. For each FedEx shipment, ml-connector uses the transactionId field for idempotency dedup to avoid duplicate CloudSuite records. Tracking numbers are matched to CloudSuite PO items either by exact line reference or by a configurable fuzzy matcher on supplier name and ship date. If FedEx webhooks are enabled and active, ml-connector subscribes to tracking events instead of polling, significantly reducing API volume. Sandbox testing uses the FedEx virtualized sandbox (with static response validation) and a CloudSuite non-production tenant if available.

A real-world example

A mid-sized industrial distributor runs Infor CloudSuite M3 for procurement and inventory, and ships most goods via FedEx. Before integration, the logistics team logged into FedEx separately to track inbound receipts and copied tracking numbers by hand into CloudSuite PO notes every morning. Receiving dock staff had no visibility into expected arrival times and often missed shipments. With CloudSuite and FedEx connected, each inbound FedEx shipment automatically updates the matching PO, showing current location and estimated delivery in the CloudSuite receiving dashboard. Dock staff see which shipments are arriving that day and can prioritize unloading and putaway without manual cross-checking.

What you can do

• •Sync FedEx shipment tracking events into Infor CloudSuite purchase order lines, updating delivery status and estimated arrival in real time or on schedule.
• •Map FedEx tracking numbers to CloudSuite PO items by line reference, supplier name, or date-based fuzzy matching.
• •Authenticate FedEx with OAuth2 client credentials and Infor CloudSuite with ION API Gateway OAuth2, managing token refresh and rate-limit backoff for both.
• •Receive FedEx tracking push events via paid Advanced Integrated Visibility webhooks, or fall back to free Track API polling for up to 30 shipments per batch.
• •Create a full audit trail of every tracking update in CloudSuite, linked to the originating PO and goods receipt, with the ability to replay or reconcile tracking history if a delivery is disputed.

Questions

Does ml-connector require FedEx Advanced Integrated Visibility webhooks?

No. Webhooks are optional and require a separate FedEx paid subscription. ml-connector works with free Track API polling by default, querying FedEx for shipment status on a schedule aligned with your receiving process. If you enable webhooks, ml-connector will subscribe to them and update tracking in near-real-time instead, reducing API load.

How does ml-connector handle Infor CloudSuite's per-customer base URL and token lifetime?

ml-connector accepts the full CloudSuite .ionapi file per customer, which contains the unique base URL, tenant ID, OAuth endpoint, and credentials. It proactively refreshes the OAuth2 bearer token before expiry (which can range from 1 to 24 hours per tenant admin configuration) so token refresh never causes a missed tracking update.

What if a FedEx shipment does not match any Infor CloudSuite purchase order?

ml-connector logs unmatched shipments and holds them in a quarantine queue for manual review. You can configure the fuzzy matcher threshold and add custom PO reference logic, or match by supplier master data and expected ship date to catch unlinked shipments during the receiving process.