Skip to content
Bitween AI is on the way

Retail & e-commerce

Every order, stock level and supplier feed, in step across every channel.

Retailers run on a web of marketplaces, suppliers, warehouses and store systems that each speak their own dialect. Bitween gives them one pipeline and one record, so an order number typed into a search box shows exactly where that order went.

Talk to an architectRead the docs

The challenge

What makes retail & e-commerce integration hard.

01

Partners multiply faster than code

Every marketplace and supplier brings its own API, file drop or format. Point-to-point scripts stop being maintainable long before the tenth partner.

02

Peaks don't wait

Promotions and seasonal peaks multiply volume overnight. One slow partner endpoint shouldn't hold up everyone else's orders.

03

“Where is order 10482?”

When a customer calls, support needs an answer in seconds, not a log search across five systems.

Flows you can run today

How Bitween handles it.

Each flow below uses capabilities that exist in Bitween now, with links into the documentation that describes them.

Flow 1

Marketplace orders into your ERP

Amazon Selling Partner API notifications arrive on your SQS queue. Bitween unwraps them, deduplicates by notification id, maps each order to your ERP's format and posts it with OAuth2. The ERP's acknowledgement is published as a new message that starts fulfilment.

  1. 1SQS bus gateway
  2. 2Unwrap & dedupe
  3. 3Rules-based mapper
  4. 4HTTP · OAuth2
  5. 5Publish “order-accepted”

Flow 2

One endpoint for every supplier

Suppliers post order confirmations and ship notices to the same API gateway URL. Each supplier's API key selects its own pipeline, validator and mapping, so onboarding a supplier is configuration, not a deployment.

  1. 1API gateway
  2. 2Partner key → pipeline
  3. 3Validator
  4. 4Map per supplier
  5. 5Deliver to ERP

Flow 3

Stock and price feeds on a schedule

A scheduled job polls the ERP database with a timestamp cursor and turns each changed row into an exchange. Deliveries publish feed files to S3 or a marketplace's SFTP, and an aggregation rolls the day's exchanges into one list for reconciliation.

  1. 1Scheduled job
  2. 2Timestamp cursor
  3. 3Map
  4. 4S3 / SFTP upload
  5. 5Daily aggregation

Controls that matter here

Capabilities behind the flows.

Work groups isolate peaks

Give marketplace orders their own processing lane with its own prefetch, so a slow supplier never delays checkout-critical flows.

Docs

Search by order number

Promoted properties make order ids, SKUs and customer references searchable across every exchange.

Docs

Retries that respect partners

Exponential back-off with per-message caps and shared budgets stops retry storms against a struggling endpoint.

Docs

Partner properties

Account numbers, base URLs and identifiers live on the partner and are resolved into adapters with {{partner.KEY}}.

Docs

Good to know about formats and scope

Bitween maps JSON and XML natively. EDI X12 or EDIFACT documents can be translated to JSON or XML by a custom adapter before the rules-based mapper takes over.

Related use cases

Go deeper on the patterns.

B2B partner integration

Onboard partners with their own keys, properties and pipelines: configuration, not code.

ERP & database sync

Poll named SQL statements into exchanges and write deliveries back to tables and procedures.

File & mailbox automation

Pick up files from S3, Azure Blob, SFTP and mailboxes; transform and deliver them safely.

Plan your retail & e-commerce integrations with us.

Share your partners, systems and volumes. We'll show you how the flows would run on Bitween in your own environment.

Talk to an integration architectRead the docs