| **Note** If you believe you should have access but do not see the module in your list, coordinate with the IMD Head for authorization, then with MIS to have the access enabled. |
| **Term** | **Stands For** | **Meaning** |
| TRQ | Transfer Requisition | The initial request that starts the delivery process. |
| TPL | Transfer Picklist | The picklist generated from the requisition. |
| TD | Transfer Delivery | The delivery document for the goods being sent to the store. |
| Checklist | — | A list of TDs. It lets you see whether a TD has already been added to a checklist or not. |
| VDR | Vendor Delivery Receipt | The receipt confirming the vendor delivery. |
| TR | Transfer Receipt | Created by the promo once goods are received. When created, a TR number is generated and appears here in the monitoring screen. |
| **Column** | **What it shows** |
| TRQ – TPL | Store | The Transfer Requisition and Transfer Picklist numbers, the store code, and the date the TPL was created. |
| Status | The current stage of the delivery (see Section 5). |
| TD | The Transfer Delivery number and its date, or “None” if not yet created. |
| Checklist | The checklist number and date, or “None” if the TD is not yet on a checklist. |
| VDR | The Vendor Delivery Receipt number and date, or “None” if not yet available. |
| Dispatch | The dispatch timeline showing each delivery attempt and its result. |
| TR / Pick Return | How the delivery ends: either the Transfer Receipt status/number, or a Pick Return if the goods were sent back. This is also where notice buttons appear (see Section 6). |
| **Reading the badges** **Green badge with a number — **the record exists (for example, a TD or TR number has been created). **Red “None” badge — **that record does not exist yet. |
| **Status** | **Meaning** |
| Queue | The delivery is queued and has not yet been picked. |
| Picked | The items have been picked. |
| Assembling | The TD is on a checklist and is being assembled. |
| Ready for Shipment | A VDR exists; the delivery is ready to ship. |
| Out for Delivery | The delivery is on its way to the store. |
| Delivered | The goods have been delivered to the store. |
| Delivery Failed | A delivery attempt failed. Click the dispatch timeline to view attempt details. |
| Declined by Promo | The promo declined to process the TR. Click the status to view the reason. |
| Open (Free Items) | The transfer is open for free items. |
| Completed | A TR has been created — the delivery is fully complete. |
| Pick Return | The goods were sent back or reversed before delivery. This is an end state — no TR is expected. |
| Cancelled | The delivery was cancelled. |
| **Notice** | **Sent to** | **Purpose** |
| **First Notice** | The store's Promo | A first warning asking the promo to process the pending TR. |
| **Second Notice** | The Area Supervisor | Escalation: the promo was already notified but the TR is still unresolved. |
| **Third Notice** | The Audit Team | Final escalation: neither promo nor supervisor acted; audit takes necessary action. |
| **Important — notices are sent manually** The system decides when a notice button becomes available, but it never sends anything on its own. The button simply appears; you review the message and recipients, then click Send. Nothing goes out until you do. |
| **What you see** | **What it means** |
| A green TR number | The TR has been created. The delivery is complete and nothing further is needed. |
| **Pick Return** | The goods were sent back or reversed before delivery. This is an end state — no TR is expected and no notice applies. |
| For TR | The goods are delivered and a TR is expected, but the waiting period before the first notice has not yet passed. |
| **First / Second / Third Notice ***(button)* | A notice is now due. Click the button to open the compose window and send it. |
| First / Second / Third Notice Sent | That notice has already been sent. The row waits until the next notice becomes due. |
| None | No TR exists and the delivery is not yet at a stage where a notice applies. |
| **Tip** The recipient list matches the notice level — the promo for a First Notice, the Area Supervisor for a Second Notice, and the Audit Team for a Third Notice. Always confirm the list before sending. |
| **One day per store, per notice** Within a single notice level, each store code can be assigned to only one day. For example, if store SNE is placed on Day 5 of the First Notice, it cannot also be added to Day 6 of the First Notice — the system will not allow the duplicate. Each store does, however, get its own day under each of the three notice levels. |
| **Notice** | **Becomes available when…** |
| **First Notice** | Delivery date + the store's First Notice days have passed, and the promo still has not created the TR. |
| **Second Notice** | The date the First Notice was sent + the store's Second Notice days have passed. |
| **Third Notice** | The date the Second Notice was sent + the store's Third Notice days have passed. |
| **Example** Suppose store SNE is set to Day 5 under the First Notice. • The delivery is completed on June 1. • The system waits 5 days (June 1 + 5). • On June 6, if the promo still has not created the TR, the First Notice button appears and you can send the warning SMS. The Second and Third Notices then follow the same idea, counted from the day the previous notice was sent. |
| **At a glance** **Send notices manually — **the button appears automatically, but you review and click Send. **Scope matters — **choose one TD or all TDs for the store before sending. **Schedule drives timing — **Settings decides how many days pass before each notice appears. |