Skip to main content
web-development

Ecommerce Product Substitutions: A Store Brief

Define replacement product proposals, customer approval, stock allocation, verified financial adjustments and packing for online orders.

Mocky Digital
16 November 2026
7 min read

An ecommerce product substitutions brief defines what happens when an ordered item cannot be supplied exactly as requested. A different colour, size, brand or pack quantity may look like a convenient replacement to the warehouse but change what the customer agreed to buy. The website and staff workflow should preserve that distinction.

When planning ecommerce website development in Kenya, decide how replacement proposals are reviewed before adding an order edit feature. The examples below are illustrative requirements, not a universal customer policy, legal advice or permission to modify any live order. The business should approve its actual terms and exceptions separately.

Define when a substitution may be proposed

Start with the operational trigger. An item may be damaged during packing, missing from the shelf or no longer available from the supplier. Record how staff identify the problem and who can propose an alternative. A stock mismatch should become a visible exception rather than a quiet change to the picking list.

Separate proposing a replacement from accepting one. Staff may identify a suitable alternative, but that does not establish that the customer wants it. Decide whether any narrowly defined preferences can be supplied before purchase and how those preferences are represented without becoming blanket permission for unrelated changes.

Also distinguish substitution from cancellation or a partial shipment. The correct solution may be to remove an item, wait for stock or ask the customer to choose another product. The system should support the approved choices rather than force every shortage into a replacement workflow.

Describe the differences the customer needs to see

A replacement proposal should identify the original product and the proposed alternative clearly. Include the relevant variation, quantity, pack size and other characteristics that affect suitability. A small thumbnail and a generic product name may conceal a meaningful difference.

For example, replacing a pack with individually sold units can change both quantity and price interpretation. Use the ecommerce quantity rules brief to define sale units and stock conversions. A warehouse convenience should not change the delivered amount without an explicit approved decision.

Have the business decide which differences make a product ineligible as an alternative. Do not let a matching category or similar price automatically establish equivalence. The store's responsible staff need to own that judgement, especially where specifications affect the customer's intended use.

Choose an approval route and record the decision

Define how the customer receives the proposal and how the store recognises a valid response. A support conversation, an authenticated account action and a secure order-specific link require different handling. The project team should explain how ownership is checked for the chosen route.

Show the proposed change as pending until the required approval is received. The customer should understand whether the store is waiting, whether their response was accepted and whether further payment or fulfilment review is required. Avoid a confirmation message that implies goods have already been dispatched.

Keep a suitable decision record: original item, proposed item, approved quantity, any price effect and the relevant authorisation reference. Staff should not have to reconstruct the agreement from separate informal messages. Restrict access because the surrounding order record can contain private customer information.

Recalculate the order through the trusted system

Decide how the proposal affects item prices, discounts, delivery eligibility and the final amount. The server should calculate the result from authorised product and order data. A price entered in the browser should not become the financial authority for an amended purchase.

For a more expensive alternative, explain the approved process for any additional payment before the store treats the change as complete. For a less expensive alternative, decide how the adjustment is handled through the verified financial workflow. Do not mark money received or returned merely because a support note says it happened.

Review the ecommerce refund workflow brief where a refund is required. Product replacement approval and financial settlement are separate states. The implementation should keep both understandable without inventing provider capabilities or charging arrangements that the store has not verified.

Coordinate stock for the proposed alternative

A proposed replacement needs a stock rule. Decide whether the store holds the alternative while waiting for approval, and what releases that hold. A customer should not approve a product that the system has already promised elsewhere without receiving an accurate follow-up state.

Record how the original allocation changes. The item might remain unavailable because it is damaged, or return to sellable stock after a corrected count. Do not assume that replacing a line item automatically performs the right inventory adjustment for every cause of the shortage.

Check components as well as individual items. If an order contains a bundle, substituting one component may affect the offer and packing requirements. The product bundles brief helps distinguish shared component stock from the customer-facing bundle. Agree how the change is represented before staff improvise it during dispatch.

Understand the platform's editing limits

Ask the developer to demonstrate the intended workflow on the actual proposed platform. An administrator being able to edit an order does not mean a customer approval process, stock hold or financial reconciliation already exists. Identify which parts are standard configuration and which need additional implementation.

WooCommerce's order editing documentation describes individual-order controls and editing restrictions associated with order states. Review the current behaviour for the chosen setup. Do not promise that every paid or dispatched order can simply be edited in place.

For a custom system, describe the state transitions and server checks as part of the project requirements. Staff should not be able to apply an obsolete proposal after another approved change or dispatch. The trusted system needs to reject changes that no longer fit the current order state and provide a clear review route.

Keep packing and customer messages aligned

Define when the warehouse may continue. A proposed substitution should not appear on a final packing slip as though it were already accepted. Conversely, an approved replacement should reach the actual picking and dispatch outputs rather than remain visible only in a support screen.

Prepare messages for proposal received, awaiting response, approved, declined and unable to complete. Each message should describe the state actually established. A message provider accepting an outgoing email proves neither customer approval nor financial settlement.

Identify the owner of uncertain cases. If a customer approves but the alternative sells out before acceptance completes, staff need an accurate exception rather than an automatic success notice. Avoid repeated proposals or charges when an interrupted request leaves the first outcome unclear.

Test realistic exceptions before handover

Use controlled orders with external delivery and payment effects blocked. Cover a same-price variation change, a different pack size, an unavailable alternative, a declined proposal and a request arriving after dispatch. Include repeated approval attempts and a staff permission change while a proposal is open.

Ask reviewers to follow the record through customer approval, stock allocation, financial status and packing. The acceptance result is not just that a new product name appears. The order should reflect the authorised goods, correct amounts and a traceable decision without duplicating work.

Document the policy owner, permitted staff roles, communication route and recovery process. Request an ecommerce project quotation with those scenarios and the actual fulfilment integrations. A clear exception workflow can then be assessed as part of the build, without claiming it guarantees customer acceptance or eliminates every shortage.

Frequently asked questions

Can staff replace an item with a similar product?

Only under the business's approved process and the relevant customer authorisation. Similar appearance or price does not establish equivalence.

Does approving a replacement confirm extra payment?

No. Any required payment must be verified separately through the store's trusted financial workflow.

Should the original order details be overwritten?

Preserve an appropriate history of what changed and why. The implementation should explain the accepted order without losing the decision record.

Can every platform support the same substitution flow?

No. Review the actual platform, order-state restrictions and integrations before agreeing the scope or promising an editing capability.

Share this article

Ready to Start Your Project?

Tell us what you need designed, built, or printed. We will reply with a clear price and timeline.

Book a Call

Preparing your booking calendar…

Having trouble? Open the booking calendar directly.

Mocky Digital

Let’s talk about your project

Choose a service and leave your details. We’ll follow up with you.

By submitting, I agree that Mocky Digital may save my details on its website and in Cal CRM and email me relevant service tips and offers. I can unsubscribe at any time.

Your details are used to respond to your enquiry. Privacy policy.