Catalogue
Products, variants, options, media, collections, related products and structured attributes for filtering, with editorial content alongside.
Solution
Ecommerce Platforms
Storefronts built for the catalogue and the fulfilment model you actually have, with checkout through a processor and orders that reach fulfilment without manual steps.
Overview
What the system does
A custom storefront is worth building when the product model, the pricing rules or the fulfilment path do not fit a hosted platform, or when the platform fee on volume has become the largest line in the budget.
Typical reasons are configurable products, customer specific pricing, mixed fulfilment across stock and print on demand, wholesale alongside retail, or a checkout that has to collect information the platform will not model.
The parts that decide whether a store works are catalogue structure, checkout reliability and the order pipeline behind it.
Who needs this
Merchants needing catalog, checkout and fulfillment workflows beyond a standard storefront configuration.
What we build
We build the operational back office with the customer journey: variants, order states, refunds, shipment tracking and administrative permissions. Decide whether custom commerce or an extension to WooCommerce is the better fit before replacing working systems.
Modules
Core modules
Pricing
Base price, sale price with a schedule, customer group pricing, quantity breaks, bundles and promotion rules applied in a defined order.
Search and browse
Faceted filtering against indexed attributes, sensible sorting, synonym handling and a results page that stays fast as the catalogue grows.
Cart and checkout
Persistent cart, guest checkout, address validation, shipping options calculated from the basket, tax handling, and payment through a processor managed checkout or hosted fields.
Order pipeline
Orders created from a verified payment webhook rather than a browser redirect, then allocated, fulfilled and tracked through a state machine.
Fulfilment
Stock picking, dropship routing and print on demand submission, with tracking written back to the order and to the customer.
Accounts
Order history, reorder, saved addresses, subscriptions where relevant, and returns initiated by the customer.
Administration
Catalogue editing, order management, refunds, stock adjustment and reporting, built for the people who use it all day.
Architecture
How it fits together
A typical implementation flow, with explicit responsibilities at each boundary.
Integrations
- Payment processors for checkout and refunds
- Print on demand and dropship suppliers
- Shipping carriers and rate services
- Tax calculation services
- Transactional email providers
- Inventory and accounting systems
- 01
Shop
Resolve catalog, availability and permitted purchase options.
- 02
Pay
Use processor-managed capture and verified events to establish payment state.
- 03
Fulfill
Send eligible order lines to fulfillment and reconcile shipment or refund updates.
Security and controls
Design for the exceptions, not just the happy path.
Protect administrative actions, verify webhooks and keep card capture with the processor. Inventory and payment changes need idempotency and recovery paths, not browser-only success checks.
Technology options
We select the final stack after reviewing your existing systems and operating requirements.
Security and IP practicesFit
Industries that use this
FAQ
Questions people actually ask
Why create the order from a webhook rather than the success page?
Because a customer can close the tab between paying and being redirected. The payment webhook is the reliable signal, so it creates the order, and the success page just reads it.
What stops a duplicate webhook creating two orders?
The handler stores the processor event identifier and the session reference. A repeat is acknowledged and dropped, and order creation is keyed so it cannot run twice.
Can we sell wholesale and retail from one catalogue?
Yes, with customer group pricing, minimum quantities and separate visibility rules, so a trade customer sees trade terms on the same product.
Do you handle card data?
No. Payment runs through a processor managed checkout or hosted fields, so card details go straight to the processor and never reach your systems. That keeps card data out of scope for you.
Can we combine stocked products with print on demand?
Yes. Routing is per line, so an order can pick some items from your own stock and submit others to a fulfilment partner, with tracking merged on the order.
Is a custom store faster than a hosted platform?
It can be, because you control what ships to the browser and how pages are rendered. Speed is a design and measurement discipline, not an automatic result of building custom.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.