Push orders to your ERP or your 3PL, automatically

When someone else does your accounting or your shipping, they need the order promptly and in their own shape. easySales routes qualifying orders to your ERP or your fulfilment partner and tracks what came back, so a rejected submission is visible rather than lost.

  • Orders routed by rule, not by export file
  • Stock levels flowing back from the external system
  • Per-order submission status you can filter on
No card required
Automation flow diagram showing an order routed to an ERP or a fulfilment centre based on a condition Trigger Order ready to fulfil Condition Warehouse is the 3PL Action Send to fulfilment centre Action Send to ERP

HOW IT WORKS

Connect, route, reconcile

The external system stays authoritative for its own domain.

1

Connect the system

Register your ERP or stock software as a connection, and your fulfilment provider as a fulfilment service, with the credentials each one needs.

2

Decide what goes where

A flow action sends the order onward, gated by whichever conditions describe your split — by warehouse, by channel, by product, by destination.

3

Watch what comes back

Submission state is tracked per order, and stock updates from the external system flow back into the levels your offers use.

Exporting files vs routing orders

Doing it by hand

  • Export a CSV and email it to the fulfilment centre
  • Re-key orders into the ERP each morning
  • Discover a rejected order days later
  • Stock in the ERP and stock on the channels disagree
  • Cancelled orders still get shipped by the 3PL

With easySales

  • Orders arrive at the external system as they qualify
  • No manual re-keying and no daily export ritual
  • Rejected submissions visible on the order
  • Stock flows back so the numbers reconcile
  • Cancelling an order withdraws the submission

EXTERNAL SYSTEMS

Handing work over without losing sight of it

01

Route only what should be routed

Most sellers do not send everything to one place. Conditions let you split by fulfilling warehouse, by channel, by product type or by destination country, so your own warehouse and your 3PL each receive exactly the orders they are meant to handle.

Per-warehouse Per-channel Per-product Per-country
Routing rules showing which orders go to which fulfilment provider or to the ERP Routing rules Active CONDITION DESTINATION STATE Bulky items Fulfilment A On Marketplace B Fulfilment B On Own warehouse ERP only On B2B orders ERP only On
02

Submission status per order

Handing an order over is not the same as it being accepted. easySales keeps the submission state on the order and refreshes it against the external system, so orders that were rejected or are still pending are a filter rather than a surprise.

Per-order state Recurring refresh Filterable
Submission list showing accepted, pending and rejected orders at a fulfilment provider Submissions Fulfilment A ORDER SENT STATE #300429 08:12 Accepted #300430 08:12 Accepted #300431 08:40 Pending #300433 08:41 Rejected
03

Stock coming back the other way

A fulfilment centre holding your inventory is the authority on how much of it is left. Stock updates flow back into easySales, roll up into the levels your offers use, and reach your channels — so you are not selling units that a 3PL has already shipped.

Stock-in Receptions Feeds offer stock

See stock control →

Diagram showing fulfilment stock updates flowing back into offer availability Trigger Fulfilment reports stock Action Update warehouse stock Action Push availability to channels
04

Cancellations that actually withdraw

An order cancelled after it was handed over needs to be withdrawn, not just marked cancelled locally. Where the provider supports it, cancelling the order cancels the submission too — which is the difference between a stopped shipment and an unwanted parcel.

Withdraw submission Prevent wrong shipments Provider-dependent
Diagram showing an order cancellation withdrawing the fulfilment submission Trigger Order cancelled Condition Submission still open Action Cancel the submission

Route orders from every marketplace and online store into the systems you already run

5 stars

"No more CSV emails"

5 stars

"Rejections surface early"

5 stars

"Stock finally reconciles"

No card required
14-day free trial
Cancel anytime

Ready to stop emailing order exports?

Connect your ERP or fulfilment partner and let qualifying orders route themselves.

Start free trial

Frequently Asked Questions

Have a question? Contact us and we'll be happy to help.

easySales integrates with a range of ERP and stock-management systems and with third-party fulfilment providers. The integrations page lists what is available, and the developer API covers anything not yet supported natively.

Yes — that is the normal setup. Conditions on the routing flow split by warehouse, channel, product type or destination, so each order goes where it belongs.

Submission state is stored on the order and refreshed against the provider, so accepted, pending and rejected are all visible and filterable rather than something you find out about later.

Yes. Stock updates from the external system flow into easySales and roll up into the availability your marketplace offers publish, which is what stops you overselling inventory the 3PL has already shipped.

Where the provider supports cancellation, cancelling the order withdraws the submission too. Provider behaviour differs, so it is worth confirming for the specific integration you use.

No. That is the point — orders are routed as they qualify, so there is no daily export ritual and no re-keying.