Keep one stock promise across website, marketplace and store

Give each quantity a clear meaning

Start with one location and item. Physical on-hand stock may include damaged goods and existing commitments. A system's available quantity may already exclude them. Confirm its definition before subtracting reservations again. Record the source and timestamp beside the number.

Map customer and channel references to the approved item, variant and pack. Two cartons are not necessarily two individual units. Hold an uncertain match for clarification rather than allowing a familiar product name to hide a quantity error.

Decide which system can make the promise

Several channels may display the same availability, but only a supported reservation process can establish a commitment. Record which system owns that decision and how other channels receive changes. A channel allocation is not necessarily another physical stock pool.

Consider two customers ordering at nearly the same time. Both can read an available quantity before either reservation completes. The implementation must rely on accepted results and supported concurrency controls, not a promise based only on the earlier read.

Treat uncertainty as an operating state

If a write times out, the process must inspect whether it succeeded before retrying. Reuse the supported operation identity rather than generating a new independent order. If status remains unknown, hold the customer commitment and give the case an owner.

The same discipline applies to cancellations and expired holds. Releasing stock without checking the current fulfilment state can make units available while a parcel is already being prepared. Define what each state permits and who can override it.

Confirm the physical step

Reservation is not readiness. The store or fulfilment team must confirm the correct item and preparation status before a ready message is sent. When physical stock disagrees with the system, the discrepancy needs investigation and correction across the affected channels.

If an alternative changes the customer's offer, obtain the appropriate agreement. Do not silently substitute an item or promise a transfer whose transport and receiving arrangements have not been confirmed. A resolved cancellation may be the honest completion of the case.

Keep local rules attached to local work

US and UAE operations need their own location calendars, coverage, currency presentation and approved commercial terms. Arabic and English descriptions must resolve to the same verified product facts when both languages are used. A common interface does not make cross-border stock immediately fulfilable.

Review the value of a proposed store transfer across both locations. Include transport and handling as well as the demand the sending store might lose. Moving inventory is not automatically additional business.

Close the record, not just the conversation

Check that the authoritative order, reservation, physical state and customer message agree. Record the final result and unresolved limitations. Track how often specialists intervene and why; that information identifies the next repair and keeps the true operating cost visible.

Read the reasoning behind the worksheet

Coordinate marketplace and website stock

Evaluate a store transfer

Keep product records consistent

Work through the artifact

Looqus Editorial · Version 1 · 15 September 2026 Editable starter worksheet. The lamp example is synthetic. Expected outcomes are acceptance criteria, not passed tests or customer results.

Use this worksheet

Start with one product and location. Identify the system authorized to reserve stock. Confirm whether each quantity already includes commitments before subtracting anything. A product displayed by several channels is not separate physical stock in each channel.

Product and authority

Approved item, variant and pack:

Location and market:

Channel references:

Physical count source and time:

Reservation authority:

Unavailable-stock categories:

Collection/dispatch prerequisites:

Override authority:

Looqus exception owner:

Synthetic stock basis

Request: reserve two blue lamps for collection tomorrow. Two available units permit a proposed reservation, subject to current state, preparation capacity and approved rules. Availability is not a completed reservation. Reservation is not physical readiness. The final customer message must match the state actually confirmed.

Cases to test

Promise record

Customer request reference; avoid personal data in shared worksheet:

Product match evidence:

Current sellable quantity and timestamp:

Accepted reservation/order reference:

Physical readiness confirmation:

Customer approval if offer changed:

Customer confirmation state:

Cross-channel reconciliation:

Remaining exception, owner and next review:

Market settings

For each US/UAE location record timezone, operating calendar, local currency display, language review, service coverage and approved commercial terms. A common dashboard does not authorize cross-border delivery or make one market's policies valid in another.

Completion decision

The job is complete only when the agreed customer outcome and system records agree, or an explicitly resolved alternative/cancellation is documented. Do not call a drafted reply a fulfilled promise.