E-Commerce and Shop: complete setup and orders
Configure catalog, theme, pages, SEO, delivery and notifications, then manage checkout, orders, serials, stock and documents.
Last updated: 2026-08-19
Architecture and setup order
The Shop publishes Warehouse articles in the Customer Area and, when enabled, through a public storefront. Its full process joins catalog data, prices and VAT, availability, domain and registration rules, customer addresses, delivery quotations, checkout, orders, notifications, stock movements, and administrative documents.
Configure it in this order: article master data → domain and visibility → header, footer, and pages → delivery → SMTP and communication channels → message templates → SEO and banners → end-to-end purchase test → order fulfilment. Opening the storefront before these prerequisites are ready can leave customers with carts they cannot complete.
Catalog: preparing sellable articles
The catalog is built from the ISP’s Warehouse articles enabled for Shop sales. Complete code, customer-facing name and description, net list price, article-specific or default VAT, category, brand, images, and availability. Categories may be hierarchical; the storefront displays only branches containing products.
Review unit, quantity, serial-number handling, and stock by site. A visible article with an incomplete price, VAT rule, or stock position can produce an incorrect total or an order that cannot be fulfilled. The description should clearly distinguish the product, any associated service, and what the customer receives.
General visibility and registration settings
Show Shop in Customer Area menu exposes the link to authenticated users. Enable public Shop makes the storefront browsable without login; Show prices to guests controls pre-login pricing, while Allow registration lets a new visitor create the account required for checkout.
Choose one coherent acquisition policy. If registration is disabled, new buyers need another invitation or account-creation process. Configure the custom Shop domain and its certificate before publishing campaigns or indexed links.
Header, logo, and storefront identity
Select a white or primary-color header and upload the dedicated Shop logo. Use an asset that remains readable on desktop and mobile and is consistent with the domain and favicon.
After saving, inspect the catalog, product, checkout, and information pages. Check contrast, crop, dimensions, and file weight; a logo containing very small text will not remain legible on a phone.
Information and legal pages
Create each page with a title, slug, published state, sort order, and HTML content. The slug becomes part of the URL, so keep it short, unique, and stable. Publication makes the page reachable; the order helps produce a predictable navigation structure.
Prepare at least sales terms, privacy and cookie information, shipping, payments, returns, and contacts, adapted to the ISP’s real commercial process. Before deleting a page, check footer links, campaigns, and indexed URLs that may still reference it.
SEO and measurement
The SEO switch enables measurement integrations. Settings can contain a Google Tag Manager container ID, a GA4 Measurement ID used as a fallback, Search Console verification content, and an AdSense publisher ID.
Prefer GTM when centralized tag governance is required and avoid deploying duplicate tracking through GTM and direct GA4 at the same time. These fields contain identifiers, not private credentials. Validate consent handling, the correct property, and the absence of duplicate page views before launch.
Delivery methods
Create either a Shipping method or a Pickup method, supplying a customer-facing name, optional carrier, gross base price, sort order, and active state. Radius-based shipping requires correct origin coordinates. Pickup always produces a zero delivery charge.
Deactivate a method rather than removing it when historical orders refer to it. The displayed name should explain delivery expectations, not merely expose an internal carrier label.
Delivery rules and precedence
Rules apply to shipping methods and define a minimum gross order value, geographical scope, and final gross delivery price. Scopes include all destinations, state or province, city, postal code, and kilometre radius.
When several rules match, the most geographically specific rule wins; ties are resolved by the highest qualifying minimum amount and then the lowest sort order. Radius matching requires coordinates for both origin and customer address. Test values immediately below, exactly on, and above each threshold before launch.
SMTP and automatic notifications
Select an already configured SMTP profile. Independently enable new-order and status-change notifications over email, SMS, WhatsApp, or ISP App, using only channels already configured for the tenant.
Test every enabled event with a fictional customer and verify recipient, sender, provider acceptance, delivery, duplicate prevention, and communication preferences. Keep automatic notifications disabled while unfinished templates are being prepared.
Message templates
Template sets cover order events across email, SMS, WhatsApp, and ISP App. Email supports HTML; SMS and WhatsApp need text appropriate to provider limits; ISP App uses a title and body. The on-screen legend defines the supported order and customer variables.
Use only declared placeholders and avoid hard-coded values that should come from the order. Test shipping and pickup, paid and unpaid orders, and orders containing several product lines.
Account, addresses, and checkout
Checkout requires authentication; a guest may register only when that policy is enabled. The customer selects or saves an address, requests the available delivery quotations, and chooses shipping or pickup. The server recalculates articles, VAT, eligibility, shipping, and the final total; browser-stored values are never the accounting source.
Complete street, postal code, city, state or province, and coordinates when radius rules are used. Before confirmation, show product lines, net amount, VAT, delivery, total, and the applicable terms.
Order confirmation and payment handling
Confirmation reloads enabled articles on the server, recalculates prices, VAT, and delivery, and stores an order snapshot containing customer, address, method, and totals. The order starts as New unpaid: the Shop checkout does not directly open a payment gateway, and the cart does not reserve stock.
To collect payment, create the required administrative document from the order and use the customer’s gateway on that document, or follow the ISP’s approved payment-recording process. Move the order to New paid only after collection has been verified. Customer Area confirmation, list, and detail show the order number, status, lines, total, and delivery.
Backoffice states and fulfilment
Backoffice states are New unpaid, New paid, Preparing, Shipped, Completed, and Cancelled; legacy New and Processing values are normalized. Change state only after the corresponding operational event, because enabled channels may immediately notify the customer.
If the delivery method or address changes, recalculate the quotation deliberately and review the new total before continuing fulfilment.
Serial numbers and Warehouse discharge
For serialized articles, assign as many available serial numbers as ordered units. Assignments can be removed before stock discharge and become locked afterwards. Discharge is triggered when the order moves to Shipped: the system creates the customer’s one-off sales, records outgoing Warehouse movements, and links them to the order.
Insufficient stock or missing required serials prevents the status change. Before shipping, reconcile site stock, serial count, cancellations, and any existing movement. Never create a second discharge to compensate for a display problem.
Administrative document and checklist
From the order detail, create one linked invoice, proforma, or receipt using the customer or default document type, due days, preferred gateway, order lines, VAT, and delivery charge. The order-document link prevents a second document from being generated for the same order. Open and review the document before final issue.
- Prepare articles, prices, VAT, images, and stock
- Configure storefront visibility and registration
- Verify domain, logo, and footer
- Publish current legal and service pages
- Avoid duplicate analytics tags
- Create and test delivery methods and boundaries
- Configure SMTP and every enabled channel
- Test every message template
- Verify server-side cart and checkout calculations
- Confirm the payment result
- Change status only after real events
- Assign serials before stock discharge
- Reconcile the Warehouse movement
- Review the generated document