# Cross-channel stock-promise worksheet

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

| Quantity | Units | Definition |
|---|---:|---|
| Physical on hand | 4 | Includes the damaged and committed units below |
| Damaged/unavailable | 1 | Cannot be promised |
| Already committed | 1 | Separate from the damaged unit |
| Available for a new promise | 2 | 4 − 1 − 1 |

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

| Case | Required handling | Evidence/result |
|---|---|---|
| One request for two available units | Exactly one accepted reservation for two | NOT RUN |
| Competing requests exceed available units | Accepted commitments cannot exceed sellable units | NOT RUN |
| Same request is resent | Recover existing result, no second order | NOT RUN |
| Write response is lost | Check accepted state before retrying | NOT RUN |
| One reserved unit is physically missing | Hold readiness; resolve alternatives within authority | NOT RUN |
| Hold expires | Release only under approved policy; reconcile channels | NOT RUN |
| Customer cancels after preparation | Verify current state and policy before releasing stock | NOT RUN |

## 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.
