Retail orders in. Invoices out. No re-keying.

NovexERP connects to SPS Commerce via their Transaction API using OAuth2. A background job polls for new documents on a schedule — when a purchase order arrives, it's downloaded, stored, and queued for processing. Each event is processed exactly once using a claim-lock pattern that prevents duplicate handling, even across multiple workers.

For inbound 850s, the system resolves the trading partner to a NovexERP customer, then resolves each line item by checking buyer item number, vendor item number, and UPC in sequence until a match is found. The order is created atomically with all line items, pricing, and the requested delivery date. Change orders (860s) follow the same resolution logic and apply modifications — adding new lines, removing cancelled ones, and adjusting quantities or prices on existing items. If inventory was already assigned to a line that changed, it's unassigned and returned to stock automatically.

Outbound invoices are generated after fulfillment. NovexERP finds orders that originated from SPS Commerce and have a finalized invoice, builds a compliant 810 XML document, and uploads it. The sent document is tracked with its status and payload so you have a complete record of what was transmitted.

If processing fails for any reason — an unmapped product, a missing customer, a network issue — the event is retried with exponential backoff up to eight attempts. The admin panel shows every event with its status, error details, and linked order, so nothing gets lost in the shuffle.