E-commerce automation: orders, stock and customer messages

Automate the order-to-cash path first, marketing second. Order, payment, accounting and fulfillment run on every sale, so each manual step there costs time on every order and causes most of the errors customers notice. Cart reminders and win-back campaigns come after, once order and customer data are reliable. Use your shop platform’s apps where they cover the case; build an integration layer when shop, ERP, accounting and warehouse need to agree on the same order.

Shop apps, integration layer or custom build?

For a standard Shopify or WooCommerce shop with one accounting tool, apps and plugins often cover the basics. When several systems must agree on orders, stock and customers, a dedicated integration layer gives you control over mapping, retries and error alerts. A custom shop or module is worth it for B2B ordering, configurators or pricing rules the platforms cannot express.

	Shop apps and plugins	Integration layer	Custom shop or module
Good for	Standard flows on one platform	Shop plus ERP, accounting, warehouse, CRM	B2B ordering, configurators, special pricing
Speed to launch	Fastest	Medium	Slowest
Control	Limited to each app’s settings	Full control over mapping and error handling	Full
Typical risk	Several apps writing the same data	Needs monitoring and a clear owner	Maintenance is yours

How is the order flow put together?

The payment provider’s webhook, not the checkout click, starts the flow. The integration verifies the webhook signature, checks whether it has already processed this event, and only then creates the customer and order in the ERP or accounting system. Stock is reduced in the system of record and pushed back to the shop. Fulfillment gets a picking list; the shipping label returns a tracking number that goes into the shipping email.

Invoice payments close the loop: the bank delivers credit notifications in ISO 20022 format (camt.054), and the integration matches each payment reference to its open invoice. Anything that doesn’t match goes to a review list instead of being guessed.

We have built this kind of plumbing before: a Shopify app with Shopify Flow extensions, WhatsApp cart recovery, app billing and GDPR webhooks, and a WooCommerce plugin that turns new orders into CRM deals. The Shopify app verifies every incoming webhook by its HMAC signature and ignores events it has already processed.

Example: an outdoor-gear shop in Graubünden

Illustrative scenario, not a client project.

A shop with a store in Chur and an online shop sells climbing and ski-touring equipment in German, Italian and English. Orders are copied from WooCommerce into Abacus, stock is corrected in a spreadsheet at night, and two people answer order-status emails.

After the project, a paid order (card or TWINT) creates the customer and invoice in Abacus through its REST API. Abacus becomes the single stock record for store and web shop, and the web shop reads stock levels from it every few minutes, so boots that just sold in the store are not sold again online. The customer gets a confirmation in their language, then a shipping notice with tracking. The chatbot answers status questions from live data. Business customers who pay by QR-bill invoice are matched automatically from the bank file. Customers who opted in get a reminder when they leave a cart, and a message before the next ski-touring season.

Which rules and local systems matter?

For a shop selling in Switzerland, the Unfair Competition Act sets two rules. Art. 3 para. 1 let. s requires clear seller identity and contact details, a transparent ordering process, a way to correct input errors and an electronic order confirmation without delay. Let. o requires consent for advertising by email or SMS, with a narrow existing-customer exception.

Beyond that, the Swiss Price Disclosure Ordinance requires consumer prices in CHF including VAT (standard rate 8.1% since 1 January 2024; reduced rates apply to some goods, such as food). The QR-bill replaced the old red and orange payment slips on 30 September 2022, and invoices can carry a structured reference (QR reference or Creditor Reference) that makes automatic matching possible. TWINT is available online through payment providers such as Stripe and Swiss payment service providers. Under the revised FADP, your privacy notice must name the countries where your shop, payment and email providers store customer data if that is outside Switzerland.

Shops that sell into the EU work under the equivalent EU rules: an electronic acknowledgment of each order under the E-Commerce Directive, consumer prices shown including VAT, national consent rules for marketing email and the GDPR for customer data. In discovery we list the rules for each market you sell in.

How does a project run?

1. Discovery. We follow ten real orders from checkout to delivery and payment, and note every manual step.
2. Architecture. System of record for customers, orders and stock; field mapping; event list; error handling.
3. Build. Integrations and message templates on a staging shop with test payments.
4. Launch. Order sync first, then messages, then stock; old and new flows run side by side for a short period.
5. Iterate. Error lists and support emails reviewed to find the next step worth automating.

After discovery you receive a fixed-price or phased proposal. Customer-facing messages across channels are covered in more depth in customer communication.