Skip to content
Book a demo

Integrations · Amazon Business

Amazon Business inside OmniPATH.

Connect through OAuth in two clicks. Orders sync into the same approval flow as your traditional suppliers. Invoices land de-duplicated, attributed to the right site and ready for posting, with no separate inbox to chase.

Live · purchasing Two-click OAuth UK, US and EU
Your booksXero · Sage · QuickBooksApprovedCodedEvidenced
Bills enter a funnel of 5 rings around the ONE FLOW stamp: Read (Read, classified and extracted, however it arrived: email, upload, photo or folder.), Identify (Is this a real, verified supplier? Is it the one we think it is?), Match (Does it match the order, the delivery and the agreed price?), Check (Have we seen it before? Is the VAT rate right? Do the lines and dates add up?), Approve (Approved by the right person, under the rule on the screen.). A bill that fails is held on its ring with a named reason and one fix. Only bills that pass every ring drop into your books: approved, coded, evidenced.

How it fits

Same approval flow. Every supplier.

Whether the order came from FS Foodservice or Amazon Business, it lands in the same purchasing pipeline: same approvers, same coding, same posting rules.

1Step 01Order placed on AmazonThe site team buys through Amazon Business as normal.
2Step 02OmniPATH syncsThe order and invoice are pulled in every four hours.
3Step 03Standard approvalThe same flow and the same approvers as FS Foodservice.
4AutomaticPosted to your ledgerOne ledger entry per invoice, with no duplicates.

Three steps to live

Connect once. Forget about it.

OAuth handles authentication, defaults pin the sync targets and the sync history confirms it’s working.

Step 1

Connect through OAuth

From the integrations page, click the Amazon Business tile. You’re sent to Amazon to grant OmniPATH read access to your order and invoice history. Two clicks: log in, approve.

Separate connections for Amazon Business UK, US and EU

Step 2

Set sync defaults

Pick the default site and supplier record that incoming orders should be attributed to. You can override per order from the Configuration page, but for most operators one default each is enough.

Site, supplier and sync frequency

Step 3

Watch it sync

Sync runs automatically every four hours, or click Sync Now to pull on demand. The sync history shows start time, trigger, outcome and order and invoice counts, with errors shown inline if anything bounces.

Auto Manual Webhook coming

01 · Auto de-duplication

One invoice in. One invoice out.

Amazon emails the invoice. The Amazon API delivers the same invoice. Someone uploads a saved PDF copy. Three sources, one document.

OmniPATH detects duplicates by Amazon order ID, invoice number and file hash, collapsing all three sources into a single record before approval. No duplicate payments and no manual reconciliation.

  • Order ID match across email, API and upload
  • Hash check on identical PDFs from different sources
  • Original copies kept as audit attachments
  • Shown as one record in the approval queue

Amazon Business authorisation

Illustrative

OmniPATH asks for read access only:

  • Read order history
  • Read invoice attachments
  • Read account organisation

02 · Sync history audit

Every sync, logged.

The sync history table is the audit trail for the integration. Every pull, automatic or manual, is timestamped, attributed and shows what came back. If a sync fails, you see why and where it stopped.

For finance and IT, this is the table to point auditors at when they ask how Amazon Business spend gets into the books.

  • Start time and trigger (auto, manual or webhook)
  • Outcome, with an inline error message on failures
  • Order and invoice count per sync
  • Filter by date range, trigger or outcome

Sync history · last 7 days

Illustrative
TimeTriggerResultRecords
2 May 14:18ManualSuccess8 orders, 12 invoices
2 May 10:00AutoSuccess3 orders, 5 invoices
2 May 06:00AutoSuccess0 orders, 2 invoices
1 May 22:00AutoFailed (429 rate limit)0 orders, 0 invoices
1 May 22:04RetrySuccess2 orders, 3 invoices
Clean books

What the books looked like before the gate.

Day zero is sealed from the accounting system before OmniPATH changes anything. This is what one year of ledger data looked like going in.

What the gate found at day zeroMeasured
Duplicate supplier records23%

of profiled spend belonged to suppliers keyed under more than one name: one retailer four ways, a food supplier twice, another with a typo.

Dormant supplier contacts9 in 10

supplier contacts in the accounting system carried no spend in the sealed year. Every dormant record is a door left open.

Spend with no lines62.9%

of a year's ledger spend was a total on a bill. The largest supplier, nearly a third of profiled spend, had no lines at all.

VAT at stake8.7%

of spend seen is VAT at stake on rate mismatches. The customer has already actioned 4.0%; 4.6% is still open.

Future-dated bills1.9%

of the year's bills carried a date still in the future when the baseline was sealed. Each one pulls spend into the wrong period.

Off-contract top-ups11%

of profiled spend went to supermarkets, outside any agreed price or catalogue.

From the sealed day-zero epoch of one live single-site hospitality operator (sealed 10 Sep 2026, covering the previous 12 months) and the findings read on 23 Oct 2026. Supplier groupings are our reading of the sealed spend records. How we measured this

Questions

The integration details.

Which Amazon Business regions are supported?

The UK, US and EU Amazon Business marketplaces. Each region needs its own OAuth connection, but the resulting orders all flow into the same OmniPATH workspace. Multi-region operators can run several connections in parallel.

Do I ever need to download invoices manually?

No. The integration pulls invoice PDFs directly from the Amazon Business API and attaches them to the matching order. They land in OmniPATH already linked to the right purchase record, ready for the standard 2-way match against the order summary.

How are multi-site orders attributed?

The default site is set per integration on the Configuration page. If your team uses Amazon Business Groups (one per site), the integration can map each Group to a site automatically. For one-off cases, such as a manager buying on the wrong account, the attribution can be reassigned in the approval queue before posting.

What happens when I disconnect?

You’re asked to confirm before the OAuth token is revoked. Once disconnected, no further syncs run, but existing synced orders, invoices and audit history stay in OmniPATH. You can reconnect at any time; historical syncs aren’t replayed.

Does this work with Amazon Business Prime?

Yes. Prime status is detected automatically and shown on the order record. Free shipping savings flow through to OmniPATH spend analysis as a separate savings line on the supplier overview, so the value of the Prime subscription is visible.

Can sync run more often than every four hours?

Four hours is the default for the automatic pull. Manual sync is unlimited: click Sync Now whenever you like. Webhook-driven sync, where Amazon notifies OmniPATH the moment an order is placed, is on the roadmap and will replace polling once Amazon’s webhook scopes are generally available.

Ready when you are

Connect your Amazon Business account in minutes.

From OAuth to first sync in under five minutes. Bring your Amazon Business account to the demo if you want to connect it live.

No setup fees · No minimum term · UK-based support