MYOB and UPS integration

What moves between them

The main flow is MYOB into UPS. Sales invoices and customer contacts flow from MYOB into UPS shipment creation, mapping customer names and addresses from MYOB contacts and deriving shipment line items from invoice detail. Tracking events flow back from UPS into MYOB via Track Alert webhooks or Quantum View polling, updated into the corresponding sales invoice record for visibility. UPS does not expose billing data, so no financial reconciliation is possible.

How ml-connector handles it

ml-connector stores MYOB OAuth token, API key, and company file credentials encrypted, and refreshes the OAuth token when a call returns 401. It also stores UPS OAuth client credentials encrypted and manages token lifecycle (refresh at 3.5-hour mark to stay under the 4-hour lifetime). When creating a UPS shipment from a MYOB invoice, ml-connector reads the invoice detail lines and customer contact from MYOB, maps the customer name and address into the UPS shipment payload, and creates the shipment. It then subscribes to UPS Track Alert webhooks where available, or polls Quantum View for tracking updates, and writes the tracking status back to the MYOB sales invoice record. MYOB rate limits at 8 requests/second and 1,000,000 requests/day; ml-connector backs off on HTTP 429. UPS Track Alert subscriptions expire after 14 days and must be renewed, so ml-connector tracks expiry and re-subscribes. MYOB's RowVersion field must be included on updates; ml-connector reads the RowVersion before every PATCH. Every shipment creation and tracking update carries a full audit trail.

A real-world example

A mid-sized e-commerce business in Melbourne sells direct-to-consumer across Australia and New Zealand using MYOB for all accounting. Before the integration, the warehouse team received sales orders in one system, manually created shipments in UPS, and then copied tracking numbers back into MYOB invoices. With MYOB and UPS connected, each confirmed sale in MYOB flows to UPS with customer address and phone number pre-filled, and UPS tracking updates appear in the MYOB invoice record automatically. The team spends less time on data entry and can promise customers accurate tracking information on their invoices.

What you can do

• •Create UPS shipments directly from MYOB sales invoices with customer address and contact information mapped automatically.
• •Sync UPS tracking events back to MYOB sales records so your team sees delivery status without switching systems.
• •Validate customer addresses in UPS before creating shipments, catching incomplete or ambiguous data early.
• •Manage OAuth2 credentials on both sides and auto-refresh tokens before expiry to keep the integration running.
• •Track UPS shipments via webhooks where available or poll Quantum View, with automatic Track Alert subscription renewal every 14 days.

Questions

Which direction does data move between MYOB and UPS?

The main flow is MYOB into UPS. Sales invoices and customer contacts flow from MYOB to create UPS shipments. Tracking events flow back from UPS into MYOB via webhooks or polling so your sales records show delivery status. MYOB payments and general ledger entries do not move to UPS since UPS has no billing API.

Does MYOB's three-header authentication add complexity?

Yes. MYOB requires OAuth2 bearer token, API key, and Base64-encoded company file credentials on every call, and the bearer token refreshes every 20 minutes. ml-connector stores all three encrypted, includes them on each request, and refreshes the token automatically when a 401 response arrives.

How does UPS Track Alert subscription expiry affect the integration?

UPS Track Alert subscriptions expire after 14 days and must be renewed to continue receiving webhook notifications. ml-connector tracks the expiry date and automatically re-subscribes before it lapses. If webhooks are not available, ml-connector falls back to polling Quantum View on a schedule you control.