Joony CommerceDiscuss your project
Ecommerce fulfilment planning

Plan fulfilment before the storefront promises too much.

A practical discovery guide for delivery, collection, inventory responsibility, order status and customer communication before an ecommerce launch.

Defined fulfilment ownerClear delivery promiseException and recovery pathsTestable order statuses
Online-first · early access

The customer promise is only credible when the business knows who accepts an order, where availability comes from, how goods are prepared, which carrier or collection point is responsible, and how exceptions are communicated.

01

Map the physical journey behind the digital order.

Document where products are held, who confirms availability, when the order becomes committed and how preparation is recorded. If more than one location can fulfil, define allocation and transfer responsibilities before launch.

  • Name the source location and fulfilment owner
  • Define when inventory becomes committed
  • Record preparation and hand-off evidence
02

Design delivery and collection separately.

Delivery zones, fees, time slots, carrier hand-off and tracking create different failure modes from customer collection. Each route needs its own promises, status changes and customer-service procedures.

  • Confirm zones, fees and service windows
  • Define carrier and collection hand-offs
  • Plan late, failed and unclaimed orders
03

Test exceptions before accepting production traffic.

The launch test plan should include unavailable items, partial preparation, payment uncertainty, address problems, customer cancellation, carrier failure and support escalation. A happy-path demonstration is not enough.

  • Run customer and operator acceptance scenarios
  • Verify notifications and support ownership
  • Agree rollback and manual recovery procedures