Deltek and Walmart Marketplace integration

What moves between them

The flow runs from Walmart Marketplace into Deltek. ml-connector pulls Walmart reconciliation reports and order data, then posts the resulting accounting into Deltek's accounting module: settled order revenue becomes AR invoices, and marketplace fees, refunds, and adjustments become journal entries, each mapped to the matching Deltek project and GL account. Returns and refunds pulled from Walmart reduce the corresponding AR and post offsetting journal lines. Walmart is treated as a read-only accounting and sales source, so ml-connector never writes financial entries, projects, or invoices back into the marketplace. Order and report webhooks trigger the work as activity settles, and a scheduled poll backfills anything a push missed.

How ml-connector handles it

ml-connector stores both credential sets encrypted and re-requests a fresh Walmart client credentials token before the 15-minute expiry rather than waiting for a 401, attaching the WM_SEC.ACCESS_TOKEN and WM_SVC.NAME headers and a unique correlation id on every Walmart call. On the Deltek side it accepts the full company URL and database name per customer, since Deltek publishes no shared base URL, and runs the OAuth2 password grant against that tenant. Because Deltek has no idempotency header, ml-connector queries Deltek by invoice number before posting so a replayed settlement never creates a duplicate AR invoice. SKUs are mapped to Deltek projects and revenue accounts first, so every settlement line references a project and GL account that already exists. Walmart reconciliation pulls use feed and report endpoints rather than the heavily throttled single-item calls, and 429 responses are retried with exponential backoff and jitter. The 180-day order window means historical orders are pulled and archived before they age out. Every record carries a full audit trail and can be replayed if a Deltek post fails.

A real-world example

A consumer-products company of about 60 staff sells direct on Walmart.com while running its books in Deltek Vantagepoint, where each product line is tracked as a project. Before the integration, an accountant downloaded Walmart settlement reports every payout cycle and hand-entered the gross sales, marketplace fees, and refunds into Deltek, then spent the first days of month-end close reconciling the Walmart payout against the bank deposit and the ledger. With Deltek and Walmart Marketplace connected, each settlement posts into Deltek automatically as an AR invoice with the fees and refunds booked as journal lines, allocated to the project for each product line. Month-end close starts with marketplace revenue already reconciled, and the manual re-keying step is gone.

What you can do

• •Post Walmart Marketplace settled order revenue into Deltek as AR invoices against the correct project and GL accounts.
• •Book marketplace fees, refunds, and adjustments into Deltek as journal entries from each reconciliation report.
• •Map seller SKUs to Deltek projects and revenue accounts so marketplace activity lands on valid accounting dimensions.
• •Authenticate Walmart with the OAuth2 client credentials token and required headers, and Deltek with its tenant password grant.
• •Reconcile on a schedule with duplicate checks by invoice number, retries on 429, and a full audit trail on every record.

Questions

Which direction does data move between Deltek and Walmart Marketplace?

The flow is one direction, from Walmart Marketplace into Deltek. Settlement reports and order data move into Deltek's accounting module as AR invoices and journal entries, while returns and refunds reduce the matching AR. Walmart is a read-only accounting source, so ml-connector does not write invoices, projects, or financial entries back into the marketplace.

Can ml-connector push product or inventory data from Deltek to Walmart Marketplace?

No. Deltek Vantagepoint is a project-based accounting ERP and has no product item or inventory master to publish, and Walmart has no GL or vendor objects to receive. The integration is shaped around what each side actually holds: Walmart order and settlement data flows into Deltek as accounting records. Item and inventory sync would require a product-based source system rather than Deltek.

How does the integration handle Walmart's short-lived tokens and Deltek's lack of an idempotency key?

Walmart client credentials tokens expire after 15 minutes, so ml-connector requests a fresh token before expiry on every cycle and sends Walmart's required WM_SEC.ACCESS_TOKEN and WM_SVC.NAME headers. Deltek has no idempotency header, so ml-connector queries Deltek by invoice number before posting. That way a replayed or re-pulled Walmart settlement never produces a duplicate AR invoice.