29

Customer orders

3 Oct 2026 · Customer: SAIF & SA-AD · orders by order date, deliveries by delivery date

No order for 3 Oct 2026 · Customer: SAIF & SA-AD is in the data.

Waiting for delivery
AED 0no order in scope
Units delivered so far
None0 of 0 orders have a delivery
Delivery notes, no invoice yet
Noneevery note in scope is invoiced
Against earlier orders
Noneno delivery names an order before 1 Oct
Reservations are not in the Tally export
The Day Book records orders, deliveries, invoices and receipts, but nothing marks an order as reserved, when the reservation started, or whether goods are waiting for collection. A countdown built on order dates alone would guess, so the monitor stays off until the records exist.
Makes this live: Reservation records (customer, order, items, time reserved, payments, collection) and the Tally event that starts the 5-day clock. With them, the monitor counts down every reservation, prompts staff to contact the customer when the window closes, and tracks the review before any release.

How the monitor will work

The client's 5-day rule, as the platform will apply it.

  1. Reserved

    Goods held for the customer. The 5-day clock starts.

  2. Pay and collect within 5 days

    Paid and collected in time: the reservation closes.

  3. 1. Contact the customer

    Past the deadline, staff call first and record the outcome.

  4. 2. Review release

    Only after contact does a person review whether to release the stock.

Nothing is released automatically and nothing is written to Tally. The platform records who contacted the customer, when and with what outcome, and who reviewed a release: its own workflow log, never a Tally entry.

Questions for the client

Answers needed before the monitor can run on real records.

  1. 1Which Tally event starts the 5-day clock: the sales order, the custom status MLKT_SOSTATUS changing (for example to “Approved”), an advance receipt against the order, or something recorded outside Tally?
  2. 2Where is a reservation recorded today: a voucher type, a custom field, a reserved-stock location, or a list kept at the branch?
  3. 3Does a part payment stop the clock, or must the order be paid in full?
  4. 4What counts as collected: the delivery note, the invoice, or the customer signing for the goods?
  5. 5Who reviews a release, and is a release recorded in Tally (for example a stock journal back to free stock) or only decided?

Meanwhile, in the actual data

Orders that a reservation rule would watch.

Of the 0 orders placed 3 Oct 2026, 0 (AED 0) have no delivery in the export. They are listed oldest first in the exceptions queue, aged to 3 Oct 2026, the end of the data. Without reservation records the platform cannot tell which of them are reserved.
Orders with no delivery in the export