Skip to content

SOLUTIONS

A commerce stack that survives contact with an accountant.

Catalogue, cart, tax, shipping, coupons, payments, orders, returns, and legally compliant invoicing. The parts that get postponed to year two are already here.

A typical online store installation. The unlit squares are features this one does not run — and does not show anyone.

The situation

You can get a storefront live quickly. What's hard is everything after the first sale: VAT that has to display inclusive, a distributor who needs their own prices, a return that has to put stock back and refund part of a payment, and an auditor who wants invoice numbers with no gaps.

What you get

Each one links to the feature page that proves it.

Pricing that handles reality

A base price list, dedicated price lists per customer group, and time-limited campaigns — all resolved by one engine to a single final price. Bundles derive their stock from their components automatically.

Commerce

Tax and shipping that match your market

Tax zones, tax classes, and customer tax profiles for business buyers. Shipping priced by order value, weight, volume, or geography, with bookable delivery slots where you need them.

A coupon engine, not a discount field

Conditions compose: limited to a role, a date range, days of the week, a minimum order value, a total usage cap, a per-customer cap. An unusual promotion is a new rule, not a modified core.

Orders operators can actually work with

Create and edit orders from the panel using the same pricing logic as the storefront. Free-form lines for bespoke charges. Discretionary discounts capped, with a mandatory reason and a full audit entry.

Audit & history

Returns and invoices done properly

A full returns workflow that restocks and refunds. Invoices as immutable legal documents with gapless numbering, credit notes referencing the original, and retention per legal requirement.

Card data never arrives

Payment happens on the gateway's own secure page. There is no code path where a card number could be stored, because it is never received.

Security

Features on / features off

The toggle model, made concrete on one installation.

13 of 27 switched on for a typical online store installation. Everything unlit is off — the named ones below are simply the ones people ask about.

Typically on

  • Product catalog
  • Shopping cart
  • Shipping
  • Checkout & orders
  • Coupons & discounts
  • Customer wallet
  • Full-text search
  • Reviews & ratings
  • Newsletter
  • Notifications
  • Admin dashboard
  • Saved views
  • Bulk actions

Present, routed, and in the menu.

Typically off

  • Case engine
  • Public profiles
  • Comments
  • Spec sheets

Not hidden — absent. The routes stop answering.

Off means gone — those routes stop answering and the menu entries never appear.

Selling something with awkward rules?

Unusual tax, distributor pricing, appointment delivery — that's usually the interesting part. Tell us about it.

  • We reply within one working day
  • No sales sequence, no drip campaign
  • NDA before the call if you'd prefer