Planner

1. Choose the source

PDAFile import or authenticated APISAPFile import or authenticated APIDatatexFile import or authenticated APIAnother authorised applicationFile import or authenticated API

Connection nameFactory

Order and product frequencyReference and order facts may update hourly.Production update cycleProduction updates remain separate from the hourly feed.

Factory time zoneDaily cut-offSource version

2. Required Planning data

Data	Example source field	Rule
Product reference	`P.CODE`	Stable product identity
Operation routing	`P.OPN, P.Sequence`	Every planned operation in sequence
Work content or target	`P.WC / target pcs/hr`	Required for every planned operation
Order and product link	`O.CODE, O.PROD`	Garment order reference and product link
Quantity, colour and size	`O.QTY, order-size feed`	Planning quantity and variant
Customer and delivery date	`O.CUST, O.DELIVERY`	Customer commitment
TNA event update (when supplied)	`E.CODE, E.EVENT, E.DONE`	Order receipt, fabric PO, fabric receipt, grey receipt, and other mapped event actuals

Reporting-only fields: O.UD... may be retained as source evidence, but cannot alter planning readiness, dates, capacity, status, or calculations.

3. Preview validation result

SAFE SAMPLE

Pilot factory order feed

Source: Another authorised application
Order/product mode: Hourly API synchronisation
Actuals: Daily at 21:00
Source version: To be confirmed

Product and route	Ready
Work content / pieces per hour per operation	Mapping required
Order reference and product link	Ready
Quantity, colour and size	Mapping required
Customer delivery date	Ready
TNA event actual updates	Mapping required
Production-update format	Mapping required

An incomplete mapping is quarantined for review. Planner does not partially apply a batch or silently create a plan.

4. Safeguards on every import

Record source, version, received time, extraction time, and factory cut-off.
Re-importing one batch cannot double-count quantity or completion.
A missing record is closed, with history retained.
E.CODE equals garment order reference O.CODE.
O.DELIVERED is cumulative and time-stamped.
TNA updates keep the external event reference, source timestamp, and reconciliation result; they can trigger a readiness review but cannot silently overwrite a published plan.