E-commerce integrations

The shop is the part your customers see. The integrations sit in what happens after they buy: the order has to reach the ERP, stock levels have to get back to the shop, and the parcel has to go out and sometimes come back. That holds whichever platform the shop runs on, and it’s where the manual work piles up when the connections are missing.

What has to connect after the sale

1. The order into the ERP with the right customer, item, price and VAT. Order by order or as a daily batch is a choice for your finance team, not something the integration happens to decide.
2. Stock levels back to the shop at a pace that holds when an item sells out in the middle of a campaign.
3. Shipping labels and tracking out to the logistics partner and on to the customer.
4. Returns and refunds all the way back, including stock levels and the credit note.

What happens when the campaign goes live?

That’s when the integrations come under real load. A connection that asks the ERP for stock levels on every page view sends as many requests as the shop has visitors, and the ERP is built to take orders, not to answer that. The first thing to look at is which calls grow with traffic. That’s where caching, or updates sent when stock changes, may be needed. Where volumes are low, the simple solution is enough.

Overselling is the error you want to avoid: the customer has paid for something you don’t have. What it takes to prevent it depends on how many channels sell from the same stock, when stock is reserved, how long the reservation lasts and what happens if the payment never arrives. Those are questions to answer before the integration is built, not after the first campaign.

Connecting to the ERP is covered under ERP integration. If customers pay with Swish or Klarna, see payment integration, and if they need to identify themselves, BankID is separate work.