Sage 50 and UPS integration

What moves between them

Purchase orders and customer records flow from Sage 50 to UPS. ml-connector reads purchase orders and customers from Sage 50 at regular intervals, then creates corresponding shipments in UPS and retrieves ratings and shipment identifiers. Tracking data flows back from UPS into Sage 50 as shipment events and status updates are polled from Quantum View or received via Track Alert webhooks. Address validation happens in both directions: customer and vendor addresses from Sage 50 are validated against UPS standards, and delivery confirmation data is written back to associated Sage 50 purchase order records.

How ml-connector handles it

ml-connector runs on a Windows machine with Sage 50 installed and uses the Sage 50 SDK (US .NET SDK or UK SDO COM layer) to authenticate with local Windows username and password and poll purchase orders by last-modified date. Because Sage 50 has no webhooks and requires exclusive access to company files (no interactive user session while SDK queries run), ml-connector polls at 15-minute intervals, the minimum practical frequency for near-real-time sync. On the UPS side, it stores OAuth 2.0 credentials encrypted and refreshes the bearer token every three hours (within the four-hour lifetime) to avoid service interruptions. Shipment creation requests include customer addresses from Sage 50, which UPS validates and corrects if needed; ml-connector surfaces validation failures so addresses can be fixed before retry. Tracking subscriptions are renewed every 14 days to maintain continuity. Every shipment ID and tracking event is recorded with a full audit trail, linked to the originating purchase order, so the status is visible where your team works.

A real-world example

A mid-sized wholesale distributor uses Sage 50 on Windows to manage vendor relationships, purchase orders, and customer master data. Orders are picked and packed in a warehouse, then shipped via UPS. Before the integration, a shipping clerk manually entered tracking numbers from UPS into Sage 50 after each shipment left the dock, and address discrepancies between Sage 50 and UPS caused delays and costly reshipping. With Sage 50 and UPS connected, outbound purchase orders automatically become shipments in UPS with customer addresses validated against UPS standards. Tracking updates flow back into Sage 50 without re-entry, so the team can see shipment status in the order record, and address problems are caught and resolved before the package ships.

What you can do

• •Create shipments in UPS from purchase orders and sales orders in Sage 50, with addresses validated against UPS standards.
• •Poll purchase orders and customer records from Sage 50 every 15 minutes and sync outbound shipment details to UPS.
• •Track shipment status from UPS via Quantum View polling and Track Alert subscriptions, linked to Sage 50 order records.
• •Validate and correct customer and vendor addresses between Sage 50 and UPS, surfacing mismatches for correction before shipment.
• •Authenticate Sage 50 via Windows-local SDK credentials and UPS via OAuth 2.0, with token refresh and exclusive-access polling on a schedule you control.

Questions

Does the integration handle both outbound sales orders and inbound purchase orders?

The integration is primarily designed for outbound sales orders and customer shipments to UPS. Inbound purchase orders from vendors can be tracked if the vendor ships via UPS, but since UPS has no billing or invoice API, purchase invoice data cannot be synchronized back to Sage 50. Address validation and tracking status work for both directions where the carrier is UPS.

Why does ml-connector poll Sage 50 instead of triggering immediately on a new order?

Sage 50 has no webhooks or remote event API and requires exclusive access to company data files while the SDK is active. This means an interactive user cannot be logged into Sage 50 at the same time the integration queries it. Polling every 15 minutes is the practical minimum frequency that respects Sage 50's architecture and provides near-real-time sync without conflicts or high resource overhead.

What happens if a customer address in Sage 50 fails UPS validation?

ml-connector returns the validation error with a specific reason (e.g., ambiguous street, missing postal code, invalid city). The record is marked for review in Sage 50 and the shipment is not created until the address is corrected. Once fixed, the next polling cycle retries the address validation and shipment creation, with a full audit trail of the corrections applied.