Blank editorial worksheet · E72-OL-01

One-order ledger card

One card covers one order system, one code report and one link report for one window. Use the blank CSV ledger for the rows. The ledger map shows the flow.

Local blank template. No submit action, no saving, no example order or result. Keep real order exports in your own workspace and leave customer details out of the ledger.

A. Pin the sources

Order system that decides what counts as an order

Key field and store (for example internal ID, or order name within one store)

Code report: source, export date and filters

Link report: source, export date and filters

Window and time zone

Ledger owner

Normalization rule written once (case, spaces, prefix) and the sample that proved it

Rule for cancelled and refunded orders, agreed by the owner

B. Row counts before merging

Rows in the code report

Rows in the link report

Distinct keys in the code report

Distinct keys in the link report

Keys found in both reports

Rows held (blank, reused or unmatched format)

Check: distinct code keys + distinct link keys - keys in both = distinct orders in the ledger. Write the result and whether the ledger agrees.

C. Held rows

Each held row: report, row number, reason, owner of the next step

Sentence for the report: orders counted once, how many appear in each report or both, how many rows are held