Skip to content
All work

Monster Notebook · 2026

Multi-market commerce backend

An API-first commerce core and staff back-office, built inside a third-party platform and wired to the systems the business already runs on.

Role
Building the backend and the staff back-office
Year
2026
Status
In progress
Stack
TypeScript · Cloudflare Workers · REST APIs · WebSockets · Payment integrations · ERP integration

This is client work described in general terms. Screenshots and internal details are intentionally left out.

The problem

A brand selling in several markets needs one commerce core that plugs into the systems it already depends on (payments, ERP, stock) instead of rebuilding them.

Approach

The system is built on a third-party app platform running on Cloudflare Workers. Instead of fighting the platform, I work with its conventions and keep our own logic behind clear boundaries.

Every external system sits behind its own integration seam: payment providers, a pull-based ERP sync, and a queue for middleware jobs. The back-office talks to the API through a server-side layer with permission-filtered access.

Architectural choices go into an append-only decision log — around sixteen of them in the first nine days — so the reasoning survives the people who made it.

How it flows

  1. 01

    Staff back-office

    Permission-filtered sections

  2. 02

    Server-side layer

    Calls the API on the server, never from the browser

  3. 03

    Commerce core

    Orders · catalog · stock · campaigns

  4. 04

    Integration seams

    Payments · ERP pull sync · middleware queue

What it covers

  • Orders, catalog and product families
  • Stock and warehouses
  • Campaigns and coupons
  • Payments and contracts
  • Content management for the storefront
  • An AI assistant for staff

Where it stands

In progress, with the first market launch ahead. Details stay general until it ships.