Process / 01

Paid discovery first, then fixed-scope phases

We open with a two-week discovery sprint that maps product catalog structure, local payment adapters, and inventory rules before a single storefront page is built. After that, the build runs in fixed-scope phases, each closed with written acceptance tests.

Discovery is billed separately from the build. Hosting, licenses, SMS, delivery API and provider fees are quoted apart from our fee.

See the build phases
Phase scope and what you receive
Stage Duration You receive
Discovery paid 2 weeks Catalog matrix, payment status map, inventory exception list
Build phases 3 to 5 weeks Fixed scope, per-phase estimate, acceptance tests
Evidence Per phase Provider status ledger, redirect map, test results
Handover 1 week Runbook, admin training, transfer checklist

Scope changes are re-estimated in writing before work resumes. Review the handover evidence or request a discovery call.

05 / Build phases

Five ruled phases from catalog map to handover

Each phase closes with a signed artefact. If the artefact is missing, the next phase does not open, so scope drift shows up in week one instead of launch week.

  1. 01

    Discovery sprint

    Categories, variants, attributes, filters, and import files get mapped before a single storefront template is built. Legacy URLs are collected in the same pass.

    10 working daysArtefact: catalog matrix

  2. 02

    Catalog build

    Templates, facet filters, and product imports follow the approved matrix, with stock rules attached per variant rather than per page.

    3 to 4 weeksArtefact: redirect map

  3. 03

    Local payment integration

    Adapter setup and status mapping for the approved providers, with a ledger that names every order state: created, authorised, captured, refunded, failed. Merchant approval and provider terms stay with the provider.

    2 weeksArtefact: status ledger

  4. 04

    Inventory and fulfillment

    Reserved carts, low stock, negative stock, multi-warehouse mismatch, and oversell rules are scripted as acceptance tests, then wired to delivery and pickup flows.

    2 to 3 weeksArtefact: exception table

  5. 05

    Launch and handover

    Acceptance tests re-run on production, monitoring and alert thresholds are set, and credentials move to your team with a written checklist.

    5 working daysArtefact: handover checklist

Build time is quoted per phase, not as one closing date. See the handover evidence or start with the discovery scope.

Handover evidence

Nothing goes live without a signed evidence pack.

Every phase closes with items you can inspect yourself: acceptance tests run against real order data, a redirect map for each indexed address, and a checklist the merchant approves before credentials change hands.

Acceptance tests

TestPass conditionResult
Variant to cartSize and colour resolve to one SKUPass
Payment callbackStatus maps to paid, failed or reversedPass
Oversell guardReserved carts block a second saleRetest
Warehouse syncStock delta lands within one minutePass

Redirect map

Old addressNew addressType
/catalog/old-1/catalog/sku-1301
/product/legacy/catalog/sku-2301
/shop/cart/cart301
/index.php?id=9/catalog/group-3302

Handover checklist

  1. Catalog matrix exported with attributes, filters and stock rules.
  2. Provider status ledger signed by the merchant contact.
  3. Test order reconciled end to end, refund path included.
  4. Admin roles, warehouse links and API keys rotated.
  5. Two-hour walkthrough recorded for the operations team.

Provider approval, hosting and delivery fees stay with the merchant. We hand over the map, not the bill. Request a handover review

Next step

Bring your integration questions to the review call.

We work through catalog structure, payment status mapping, and stock exceptions before quoting a build tier.