eCommerce · Websites
A product page is the product record, shown. The price is the line on the list this visitor is on, the stock is the warehouse's count, and the delivery date is read from what is available and what is on order.
A product page is the product record, shown. The price is the line on the list this visitor is on, the stock is the warehouse's count, and the delivery date is read from what is available and what is on order.
Which lists the shop reads, who may pay on invoice, and where an order is collected are yours to set.
Colour temperature, size, finish: each variant is a stock line, so the shop shows 4000 K available and 3000 K on order rather than one number for both.
The visitor picks a shop; the order is reserved on that shop's stock and the shop sees it on its own list until it is handed over.
Card and bank transfer for everyone, pay on invoice for a business on terms, a deposit for what is made to order. The method is a rule on the customer, not a setting on the shop.
A basket left for a day gets one message, once. A line that goes on backorder tells the customer the date. A delivered order asks for a review a week later. Each is a rule you can read and switch off.
What adapts: what a line is (a case, a bottle, a made-to-order piece), which price list a visitor lands on, whether the order is paid in full, on terms or by deposit, whether there is a stock line at all, and what leaves the warehouse and when. Two businesses can run the shop and agree on none of those.
A bar signs in and sees the Horeca list by the case of 24, pays on invoice at 30 days, and its order joins Thursday's delivery round with the crate deposit on a line of its own. A private customer sees bottles at the VAT-included price, pays by card and collects at the brewery on Saturday.
There is no stock line: the order creates a work order in the workshop, takes a 30% deposit by card at checkout, shows the lead time as the delivery date, and invoices the balance when the piece is delivered and signed for.
A business that buys from you is not a second shop with a login. It is the customer record you already have, with a segment that picks the price list, terms that make pay on invoice a method at checkout, a buyer who may order and an admin who approves above a ceiling, and an order history to reorder from. Atelier Nord sees Trade 2026 because the record says Trade, and the order it places at 23:10 is the order the account manager sees at 08:00.
What a visitor sees, and where each figure comes from: the price from the list their record is on, the stock from the warehouse, the delivery choice from the shops that hold the article. Signed in as Atelier Nord, the same page shows trade prices and the ceiling left.
The shop does not show a count that was true this morning. When Maison Berger orders 30 panels at 14:05 there are 14 available, because Atelier Nord's 24 and Léa's 2 are reserved on the same line, and the purchase order to the supplier says 60 more land on 24 September. So the order reserves 14, puts 16 on backorder with that date, and the customer reads "14 ship today, 16 ship 24 Sep" before paying, not in an email afterwards.
Which lists the shop reads, who may pay on invoice, and where an order is collected are yours to set.
An article has one record, one cost, one stock line per place and one description, and the shop, the till at Shop Sablon and the quote to Atelier Nord read that record. Change the price once and it is changed online, at the counter and on the next quote; sell it in any of the three and the same stock moves.
The order reserves the line, the delivery moves it, and the reorder point drafts the purchase order that fills it before the backorder date passes.
The invoice is drafted from the delivery, numbered in the same series as the counter's, and leaves through the Peppol access point for every business customer.
The order placed at 23:10 is in the customer's portal at 23:10, with its delivery state, its tracking and the invoice to pay, because the portal is a role on the same record.
The product block on the site and the shop read the same product, so the stock figure on the page is the one the checkout reserves from.
The shop, the till and the quote share one catalogue and one customer
An article has one record, one cost, one stock line per place and one description, and the shop, the till at Shop Sablon and the quote to Atelier Nord read that record. Change the price once and it is changed online, at the counter and on the next quote; sell it in any of the three and the same stock moves.
A catalogue with variants and a checkout
The stock shared with the counter and the warehouse
A business customer with their own list, paying on invoice
The backorder date shown before paying
The delivery note and the carrier label from the order
The invoice sent on Peppol
The quote before the order and the ticket at the counter
Time to live
| What you need | A spreadsheet | A shop platform | A suite module | Enobase |
|---|---|---|---|---|
| A catalogue with variants and a checkout | No | Yes | Yes | Yes, read from the product record |
| The stock shared with the counter and the warehouse | Typed in | Synced with their own till | Yes | Yes, one line, reserved by the order |
| A business customer with their own list, paying on invoice | No | On a higher plan | Sometimes | Yes, the same customer record |
| The backorder date shown before paying | No | Rarely | Sometimes | Yes, from the purchase order |
| The delivery note and the carrier label from the order | No | Yes | Yes | Yes, from the same order |
| The invoice sent on Peppol | No | No | Yes, in their invoicing | Yes, drafted from the delivery |
| The quote before the order and the ticket at the counter | No | No | Sometimes | Yes, on one customer |
| Time to live | A day | A week | Months | One week |
Yes. On its own it is a catalogue, a basket, a checkout and an order list. Turn Inventory on and every order reserves a stock line; turn Invoicing on and every delivery drafts an invoice, on Peppol when the customer is a business.
© 2026 Enobase, Inc. All rights reserved.