Area 10 · Development and web

E-commerce and integrations

A customer pays by card at twenty to midnight. By morning the order is already waiting in the accounting package, the Factur-X invoice has been issued, the Mondial Relay label is printed and the quantity shown on Amazon.fr has dropped by one. That is what a properly wired shop looks like. We join the selling platform to accounting, payments, carriers and marketplaces, so that nobody on your side copies orders from one window into another.

4
services in this area
Factur-X
the invoice is born from the order
Cards
plus instalments and SEPA
1 stock
for the shop and every marketplace

What moves, and how often

“Everything live” only sounds good in a meeting. A whole catalogue pushed every minute saturates marketplace interfaces and slows the accounting package down, so each flow gets a pace of its own.

Available quantities

Every five to fifteen minutes, from stock out to every channel. The busiest exchange of all. Stretch it further and you sell goods that already left the shelf.

Prices and promotions

Several times a day, or on request. Separate tables for the shop, for each marketplace and for trade customers, with commission already built in.

Descriptions, images, attributes

Once a night. Large volumes that would bring the server hosting Sage or Cegid to its knees during the day.

Orders

As soon as payment clears, down to the accounting package. Picking can begin before the buyer has closed the browser tab.

Invoices and statuses

Once the document exists, back towards the shop. The invoice reference joins the order, and the customer finds both document and tracking in their account.

Integrations seldom break because of code. They break because of data. The same article sold by the unit here and by the pack there, missing barcodes, a reduced rate applied where the standard one belongs, mandatory fields nobody ever filled in. So before linking anything we walk the catalogue with your accountant and whoever owns the product range. That tidy-up almost always costs less than the workarounds written for every exception.

How a project runs

Everything is proven on a copy of the database and in the test environments of the payment provider and the carrier. A mistake in live accounts is paid for in credit notes, and nobody enjoys raising those.

01

Map the flows

We draw the journey of an order, from basket through to recorded payment, and mark every spot where somebody currently copies a piece of information by hand.

02

Write the rules

When goods are reserved, what becomes of a part-paid order, how a marketplace return is handled. The answers are written down before the first line of configuration exists.

03

Dress rehearsal

A full cycle in the test environment: order, card payment, invoice, label, return and credit note. Live service opens only once every figure agrees.

04

Launch and watch

We set the schedules and the email alerts, then compare shop data against accounting data at regular intervals through the first few weeks.

Questions and answers

Usually yes, though it takes more work than an online package. Older on-site versions do not always expose an open interface, so we go through the publisher's exchange module, an intermediate connector, or a file dropped at regular intervals. Sometimes upgrading to a current version pays better than the workaround, and we say so plainly once we have looked at the installation remotely.

No, the accounting package raises the invoice and submits it through the route agreed with your accountant. Our job is to produce that document without anyone retyping, with the right buyer details and the right rates, then to bring its reference back into the order. We also define what happens while the submission service is down, so that no order sits stuck in a queue nobody is watching.

The shop keeps running on the last known figures, orders wait in a queue and travel on to accounting as soon as the link returns. A named person at your end and our team both receive an alert, so by morning you know what happened before any customer notices.

For most modest shops a platform such as Lengow, Shoppingfeed or Iziflux is a sound choice: connections to marketplaces, carriers and accounting packages already written, a subscription instead of a build. We suggest a direct link when your pricing rules are unusual, when several warehouses are involved, or when volume pushes the subscription past the cost of something of your own.

Remotely only, over encrypted links and through restricted accounts that you open and close whenever you wish. We do not come on site, we do not sell hardware and we do not handle your parcels. If something physical has to happen near the server, we write out the steps for whoever will carry them out.

Show us where someone is still retyping data

Tell us which platform your shop runs on, which accounting package you use and where else you sell. We reply within one working day with a scope and a timescale.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.