QuickBooks Desktop and Walmart Marketplace integration

What moves between them

Orders and inventory flow from Walmart Marketplace into QuickBooks Desktop. Each new Walmart order becomes a QuickBooks Invoice linked to a Customer record created from the buyer's shipping address and email. Walmart Inventory quantities sync to QuickBooks Item stock levels at a regular polling interval. Price updates from Walmart Marketplace flow into QuickBooks Item selling prices. The main direction is Walmart to QuickBooks because Walmart order fulfillment is read-only for inventory and financial reconciliation purposes. No data flows back from QuickBooks to Walmart because Walmart orders are external events that QuickBooks records, not sources of truth for marketplace operations.

How ml-connector handles it

ml-connector runs a QBWC session by authenticating with QuickBooks' SOAP session-token handshake on each poll cycle, then submitting QBXML queries for Invoices, Customers, and Items modified since the last poll. It retrieves Walmart Marketplace orders by re-authenticating with Walmart's OAuth 2.0 endpoint every 14 minutes (before token expiry at 15 minutes) and requesting orders and inventory via REST GET operations. Order data from Walmart Marketplace is mapped to QuickBooks Invoice records: the order number becomes the reference, the line items become invoice line detail, and the buyer email becomes a QuickBooks Customer lookup or creation. Inventory quantities are matched by SKU and updated in the QuickBooks Item quantity field. ModifiedDateRangeFilter queries in QBXML ensure duplicates are avoided on retry. Walmart Marketplace orders older than 180 days are not available via the API, so reconciliation starts from the integration date. Every record is logged with timestamps and payload snapshots for audit and replay on failure.

A real-world example

A small-to-mid sized retailer operates a QuickBooks Desktop company file for accounting and sells on Walmart Marketplace alongside their own website. Before the integration, the owner manually downloaded Walmart orders daily, entered them into QuickBooks as invoices, and updated inventory counts by hand whenever stock was depleted on Walmart. Month-end reconciliation required cross-checking Walmart order totals against QuickBooks sales journals. With QuickBooks Desktop and Walmart Marketplace connected, each order is automatically invoiced in QuickBooks the next time ml-connector polls (typically within 15 minutes), inventory updates in real time via Walmart webhooks, and the sales journal is complete and reconciled by month-end without manual intervention.

What you can do

• •Create QuickBooks Invoices automatically from Walmart Marketplace orders with customer details and line-item amounts.
• •Keep QuickBooks Item inventory quantities in sync with Walmart Marketplace stock across fulfillment nodes.
• •Update QuickBooks Item prices from Walmart Marketplace pricing changes on a regular polling schedule.
• •Manage QBWC session authentication and Walmart OAuth token refresh without manual intervention.
• •Track every order and price change with a complete audit log for month-end reconciliation and replay on error.

Questions

How often does the integration sync data between Walmart Marketplace and QuickBooks Desktop?

ml-connector polls both systems on a configurable interval, typically 5 to 15 minutes. Walmart order events can also be delivered via webhooks if they are enabled in your developer account, which shortens latency. QuickBooks Desktop must be running and logged into the company file on the Windows machine for any poll cycle to succeed.

Does the integration handle QuickBooks Web Connector authentication automatically?

Yes. ml-connector manages the QBWC session-token handshake on every poll cycle: it sends credentials to your SOAP service, receives a session token (GUID), and uses that token for all QBXML queries in that cycle. You provide the QBWC credentials once during setup; ml-connector handles authentication and re-authentication on every poll.

What happens if a Walmart order is more than 180 days old or an inventory update fails?

Walmart Marketplace orders older than 180 days are not available via the API, so the integration can only process orders from the setup date forward. If an inventory update fails, ml-connector retries with exponential backoff and logs the error in the audit trail so you can replay it once the issue is resolved.