The DC Invoice That Disappeared
The delivery challan was raised. The QC stamp was applied in Q2. The outward company picked it up — SRSCALES, based on the driver's manifest — but the stamping date in the system says Q3. Someone typed it wrong. Or maybe the entry was made a week late. Or maybe the inward batch it links to has a different model code than what actually shipped.
Three months later, a GST audit flags a mismatch between your outward register and the DC invoice numbers on record. You are now reconstructing a transaction chain from a combination of WhatsApp messages, a handwritten ledger someone photographed, and partial entries in a shared spreadsheet that two people have been editing simultaneously since April. This is the operational reality for any warehouse running outward dispatch without a linked database system.
The Field Architecture That Prevents the Cascade
The critical design choice in this template is the Inward Link field — a hard reference to the source batch from the Inward library. Every downstream field in the outward record — INWARD No, Serial No (batch number), Product, Brand, Item Code, Model — is calculated directly from that link. There is no manual re-entry of data that already exists.
This matters more than it sounds. In a warehouse environment where the same product SKU ships to five different outward companies in the same week, the temptation is to copy-paste or retype from the inward record. Copy-paste errors compound. A transposed digit in an Item Code will match nothing in your QC audit six months from now. The calculated fields eliminate that vector entirely: if the inward record is correct, the outward record inherits correctness automatically.
QC Status and Stamping Status are also calculated from the inward record rather than entered fresh at dispatch. The outward entry simply exposes what the inward system already decided. If the QC report says passed and the stamping status says complete, the dispatcher sees that in the outward record without touching either field. What the dispatcher does own is the Outward Company, Outward Mode, and DC Invoice Number — the logistics layer that is genuinely outward-specific. That clean division of ownership between the inward and outward records is what keeps the audit trail legible.
Stamping Quarter is a calculated pull from the inward side, and it matters specifically for excise and certification contexts where quarterly stamping cycles affect the validity window of the dispatch. An item stamped in Q2 that ships in Q4 may require re-certification depending on the product category. Seeing the stamping quarter on the face of the outward record — without having to navigate back to the inward entry — is a six-second shortcut that prevents a two-week compliance problem.
Moving the Batch Under Load
It's a Wednesday, third week of the month. You have seven outward transactions queued for SRSCALES and two for a secondary company. The driver is waiting. The QC supervisor is on the floor, not at a desk.
You pull up the Memento outward record, tap Inward Link, and the batch number auto-populates — along with the product, model, item code, brand, QC status, and both stamping fields. The only fields you're entering are Outward Mode (road), Outward Company (SRSCALES), and the DC Invoice Number from the challan in your hand. Twenty seconds per record. Seven records.
If the stamping status on one of those batches comes back blank — because the inward record was never updated after the stamping was done — you see it before the driver leaves, not after the challan is signed and the goods are already in transit.