Skip to content
Treblesys

Retail & E-commerce

Software for everything that happens after the checkout.

Storefronts are mostly a solved problem. The trouble starts behind them, in orders, stock, warehouses, stores, returns and the reconciliation between systems that were never designed to agree with each other. Most of our retail work is in that layer.

Discuss your projectSee related work

Constraints we build around

  • Peak-season load, handled with queue-based processing, backpressure and load testing against Black Friday volumes
  • PCI DSS scope kept minimal through hosted payment fields and tokenisation
  • Commerce platform, ERP, PIM, WMS and 3PL integration over API, EDI and flat files
  • Idempotent event handling and reconciliation, so an order is never lost or shipped twice
  • GDPR and consumer rights obligations around customer data and returns
  • Zero-downtime deployments, because retail doesn't get a maintenance window
A shop assistant at a counter taking a card payment

What we hear

What people in this sector tell us on a first call.

  1. 01

    Stock figures that disagree with the shelf

    The commerce platform, the ERP, the warehouse and the stores each hold their own stock figure, synced by a nightly batch. So you oversell, and someone spends Monday morning cancelling orders and reconciling the difference by hand.

  2. 02

    Orders held together by people

    Split shipments, store fulfilment, pre-orders and returns each need someone to step in with a spreadsheet or an admin panel. Every one of those exceptions costs margin, and the customer waits while it's sorted out.

  3. 03

    Peak season exposes every weakness

    Integrations that cope fine in March fall over in November. Queues back up and the batch windows overrun, and customer service ends up absorbing the fallout.

  4. 04

    Platform limits and vendor roadmaps

    The commerce platform does most things well and a few things badly. Somehow the few things are always the ones your business depends on, and they're never near the top of the vendor's roadmap.

What we build

The kinds of systems this sector tends to need.

  • Order orchestration and fulfilment routing

    An event-driven layer between the commerce platform, ERP, warehouses and stores that routes, splits and tracks orders in near real time. It replaces the nightly batch jobs and the manual reconciliation that goes with them.

  • Inventory and PIM integration

    One current stock figure across every channel, and product data flowing from the PIM to storefronts and marketplaces without anyone uploading a spreadsheet.

  • Headless storefronts and custom experiences

    Next.js front-ends over Shopify, commercetools or a back-end we build for you, for when the standard theme can't give you the experience or the page speed you need.

  • Returns, exchanges and customer service tools

    Self-service returns portals, exchange flows and agent tooling that shows the whole order history on one screen, wired into the warehouse and refund processes behind it.

  • 3PL, marketplace and carrier integrations

    API, EDI and file-based connections with warehouses, marketplaces and carriers, with monitoring around each one, so a failed shipment notice is caught the same morning, long before anyone has to chase it.

  • Trading and operational analytics

    Fulfilment lead times, cancellation rates, stock accuracy and margin by channel, fed from the same order and stock events as everything else, so trading and the warehouse agree.

Related work

A project from this sector.

All case studies
Retail & E-commerceSample

Real-time order orchestration in place of nightly batch for a specialist retailer

A specialist retailer selling online, through two 3PL warehouses and a network of stores was running its operation on nightly batch files between the commerce platform, the ERP and the warehouses. Stock was wrong by lunchtime. Split orders were handled by hand, and returns took days to reconcile. We built an event-driven orchestration layer that routes, tracks and reconciles every order in near real time. It went live two months before peak season.

fewer oversell cancellations in the first peak season
~60%
fewer oversell cancellations in the first peak season
from order placed to warehouse release, down from overnight
< 5 min
from order placed to warehouse release, down from overnight
of weekly manual reconciliation removed
~15 hrs
of weekly manual reconciliation removed
Read the case study
A large warehouse with racks of stock and yellow picking totes

Questions

Questions that come up before a first project.

Ask us directly
Do you build storefronts or work with existing commerce platforms?

Mostly the latter. Shopify, commercetools, Magento and similar platforms handle the storefront and checkout well. Our work usually sits behind them, in orchestration, integration and operational tools, or occasionally in front of them as a headless storefront when the standard theme is what's holding you back.

How do you make integrations survive peak season?

Queue-based, idempotent processing, so a burst of orders is absorbed instead of dropped, and retries with backoff for partners that slow down under load. Reconciliation jobs run behind that to pick up anything missed. Then we load test at several times last year's peak, well before the season starts, because finding the limit in November is expensive.

Can you connect us to our 3PL and marketplaces?

Yes. We've worked with 3PLs over API, EDI and SFTP file exchange, and with marketplaces on order import and stock feeds. Each connection is monitored, with an alert when it fails.

Relevant services

Other industries