Sage 50 and Orderful integration

What moves between them

Purchase orders, invoices, and payments move from Sage 50 into Orderful. ml-connector polls Sage 50 at intervals you configure (typically every 5 to 15 minutes), reads newly created or modified purchase orders and vendor invoices, queries payment records, and POSTs them to Orderful's REST API as EDI documents. Orderful then translates them to the correct EDI format (X12 or EDIFACT per partner) and delivers them via the configured channel (AS2, SFTP, VAN, or HTTP). There is no reverse flow; Orderful delivery confirmations are logged in ml-connector's audit trail but do not write back to Sage 50.

How ml-connector handles it

ml-connector stores the Sage 50 Windows user credentials and company data path encrypted, and on each poll cycle opens a local SDK session to query for changes using LastModifiedDate filters. Because Sage 50 runs on Windows desktop and requires exclusive access to its data files, the integration must run on a Windows machine where Sage 50 is installed or can be installed headless. ml-connector maps Sage 50 purchase orders, invoices, and payments to Orderful's standard EDI message types (850, 810, 820), and posts them with ISA sender and receiver identifiers that you configure per trading partner. Orderful's API requires a static API key; ml-connector stores it encrypted and includes it in every request header. Because Sage 50 has no webhooks, ml-connector relies on polling; new transactions are detected by comparing LastModifiedDate against the last poll timestamp, so gaps in the schedule do not cause data loss. Rate limits and transient failures are handled with exponential backoff and retry; every record carries a full audit trail and can be manually replayed if a downstream delivery fails. The data lives in different regions (Sage 50 local, Orderful US or EU cloud), so ml-connector includes configuration to select the correct Orderful endpoint for your region.

A real-world example

A mid-sized wholesale distributor runs Sage 50 on Windows for accounting, procurement, and inventory. They ship to retail partners across North America who receive orders via EDI (X12 850). Before the integration, the procurement team exported purchase orders from Sage 50 as CSV, manually converted them to X12 in a legacy tool, and uploaded to a VAN for delivery. With Sage 50 and Orderful connected, each purchase order created in Sage 50 flows automatically to Orderful, translates to X12, and lands at each retail partner within minutes. The procurement team now works only in Sage 50; the manual conversion and upload steps are eliminated.

What you can do

• •Poll Sage 50 on a schedule and detect newly created or modified purchase orders, invoices, and payment records.
• •Translate Sage 50 purchase orders into EDI 850 format and post them to Orderful for partner delivery.
• •Map vendor invoices and payment transactions to EDI 810 and 820 messages for accounting reconciliation at receiving partners.
• •Authenticate Sage 50 with Windows credentials and company data path, and Orderful with a static API key, storing both encrypted.
• •Retry failed Orderful API calls with exponential backoff, track every record in an audit log, and allow manual replay if a delivery fails.

Questions

Can ml-connector run Sage 50 integration on a cloud server or remote machine?

No. Sage 50 is a desktop application that requires a Windows machine with the software installed and direct access to company data files on the same machine or local network. ml-connector must run on a Windows machine where Sage 50 is present. If you do not have a dedicated integration server, you may run ml-connector on the same desktop where Sage 50 is installed, outside business hours when no user is logged in interactively.

Which Sage 50 regions are supported - US or UK edition?

Both. The US edition (Sage 50 US, formerly Peachtree Accounting) uses the .NET SDK, and the UK edition (Sage 50 Accounts, formerly Line 50) uses COM/ActiveX. ml-connector detects your edition via configuration and uses the appropriate integration layer. Licensing and feature differences between regions are respected; some transaction types may be accessible only via legacy COM or ODBC in the US edition.

How does ml-connector know which purchase orders are new since the last sync?

ml-connector queries Sage 50 using LastModifiedDate filters. On each poll, it requests all purchase orders modified after the previous poll timestamp, so there is no manual cursor maintenance. If a poll cycle is missed or delayed, the next cycle picks up all changes since the last successful sync; no records are skipped.