Ecommerce development goes beyond the storefront.
Define what happens before and after a purchase.
All perspectives · · 2 min read
Start with the product record.
A product is more than a title and a price. Define variants, availability, descriptions, images, search metadata and the relationship between a catalog item and the record used to fulfill it. Decide who can create or change each field.
Import a representative sample before committing to a catalog structure. Include difficult products, incomplete supplier data and items with multiple variants. A clean demo catalog can hide the work that will dominate daily operations.
Follow the order through the business.
Map payment, confirmation, stock changes, fulfillment and support as one connected journey. Each system needs a clear source of truth and a way to reconcile differences. Decide what a customer sees when one part of that journey is delayed.
Retries deserve explicit attention. Stripe documents idempotent requests so an API operation can be retried without creating the same operation twice. The integration brief should describe how repeated requests and incoming events are handled.
Make management part of the scope.
Ask to see bulk changes, image optimization, manual editing and the path for correcting an import. The operating team will use these capabilities far more often than it changes the home-page layout.
Define acceptance around a complete order and its exceptions. Include a failed payment, an unavailable variant, a cancellation and a customer asking what happened. Assign responsibility for the work after launch.
Further reading.
Put the brief into practice.
Ecommerce development · Discuss the work your business needs to do.