Create your account
Register as a merchant, a fulfilment partner or a supplier. Your role decides which side of the network you see.
SAP ⟷ FSN SAP fulfillment, over the interfaces you already run.
SAP holds your materials, stock and orders. What it cannot hand you is demand and capacity from outside your own company. FSN connects to it the way SAP integrations have always been built — EDI, REST or a scheduled file — and puts both on the other end.
- EDI, REST or file transfer
- AS2 / SFTP / HTTPS
- SAP stays the system of record
- Free for warehouses
FSNNetwork
Carriers, marketplaces and ERPs already on the network
The exchange
You already have the stock. What you are missing is the other side.
SAP runs your operation. FSN runs the network around it — and the network is where the merchants and the warehouses are.
What you put in
- Your catalogue, as it isProducts, variants and EANs stay in SAP. FSN reads deltas, never a full export.
- Live stockOne feed for every partner instead of a spreadsheet each.
- Your rulesWhich products, which countries, which partners. You approve every relationship.
What you get back
- Merchants who need fulfilmentPre-qualified, with volumes, categories and countries declared before you commit.
- Warehouses with free capacityLocations, categories, carriers and cut-off times, visible before you ask.
- Supplier cataloguesImport products with EAN, images and live stock. Ship them under your own brand.
- Carrier accounts and labelsResolved per shipment. Tracking normalised into one schema.
The connection
How SAP gets connected
Add SAP as a system
Enter the endpoint and credentials. They are encrypted at rest and never shown again after saving.
Read the first delta
Products, variants and stock come across incrementally and are matched to canonical variant IDs.
Go live
Accept a cooperation request, route your first order, and let tracking and status flow back automatically.
SAP
How an SAP connection is set up
No add-on inside SAP. We agree a format and a transport, and your existing middleware or basis team drives the SAP side.
- There is no dedicated SAP connector — the integration runs over the standard paths: EDI (EDIFACT, OpenTrans, cXML), REST, or XML / CSV files.
- Transport is whatever your landscape already uses: AS2, SFTP / FTPS or HTTPS.
- SAP remains the system of record. FSN reads what you export and writes orders, tracking and status back through the same channel.
| Data | Direction | Trigger |
|---|---|---|
| Products & variants | SAP → FSN | scheduled export |
| Stock | SAP → FSN | scheduled export |
| Orders | SAP ← FSN | EDI / REST on order |
| Tracking & status | SAP ← FSN | on shipment event |
Also included
The parts nobody advertises but everybody needs
Routing you can audit
Every order carries the decision that placed it: stock, country, SLA, cost, capacity, carrier.
One SKU language
Merchant, warehouse, supplier and marketplace identifiers all resolve to one variant.
Returns as their own domain
Handled as a first-class flow, not bolted onto orders.
Payouts reconciled
Completed shipments, balances and annual statements, traceable end to end.
11
steps in the routing pipeline<200ms
SKU mapping resolve p997
interface languages0
unmapped routes allowedFAQ
Is there an SAP connector we can install?
No, and we would rather say so than imply otherwise. FSN has purpose-built connectors for Odoo, JTL, PlentyONE and Dynamics 365 Business Central. SAP is integrated over the standard interfaces instead — EDI, REST or file transfer — which is how most SAP integrations are built anyway.
What do we have to build on our side?
An export of products and stock, and an import for orders, tracking and status, on the format and transport we agree. If you already run EDI or middleware against SAP, this is another trading partner on it rather than a new project.
Which SAP releases does this work with?
Any release that can exchange EDI messages or files, or call a REST endpoint — ECC and S/4HANA alike, on-premise or in the cloud. The integration talks to your interfaces, not to a particular SAP version.
Is FSN affiliated with SAP SE?
No. FSN is an independent fulfilment network and is not a partner, reseller or affiliate of SAP SE. SAP is a trademark of SAP SE, used here only to describe what FSN connects to.
What does it cost?
Merchants pay a flat $49 per month — no per-order fee, no setup cost. Warehouses, fulfilment partners and suppliers use the network for free.
Who sees our data?
A partner sees what the job needs and nothing else. Customer data stays on your side; FSN keeps the mappings, routing rules and audit trail — not a copy of your operational history.
Connect SAP, get the other side of the network
Registration takes minutes and changes nothing in SAP. Add the connection when you are ready — or talk to us first and we will walk through your setup.