Pre-rollout check
How many of your products carry the mandatory fields in the ERP?
The template simulator asks whether the mandatory fields fit on the screen; the compliance checker asks whether they exist in the template. This tool asks the third question: for how many of your products are they actually populated in the ERP? On paper labels the unit price and country of origin were often handwritten — once labelling is automated there is nobody left to write them in.
The calculation uses the fill rates you declare; we never see your data and nothing is stored. To measure the real rate, pull a random 100-row product list from your ERP and count how many rows carry each field — do not estimate.
1. Your scope
Which fields are mandatory depends on your goods. Your selection determines the list of fields asked below.
2. Your product count
The number of stock items to be labelled. Without it, percentages say nothing.
3. Fill rate per field
For each field, enter the percentage of products for which it is populated in your ERP. Leave it at zero if you do not know — assuming an unknown field is populated would be the most harmful answer this tool could give.
Result
We call it a lower bound because the gaps may fall on different products. At least as many products are incomplete as the worst field's gap; if the gaps are spread out, more. Only a real export from your ERP gives the exact number.
Work order
The field awaiting the most records comes first. This list is a work plan: each row shows how many records must be filled before rollout.
This is not a field, it is a software capability
In a discounted sale, the previous price to display is the lowest price applied in the ten days before the discount. This is not solved by populating a field; the software must have access to ten days of price history. Ask about it separately when collecting quotes.
Pre-discount price — Fiyat Etiketi Yönetmeliği
What this tool does not cover
The two items below are template matters, not ERP data; the compliance checker and the template simulator measure them.
- All information in Turkish The most commonly missed requirement. Default templates prepared for other markets often leave field names in English.
- Easily visible and legible The regulation requires the label to be legible. Shrinking type to fit mandatory fields on a small screen creates a compliance risk — the template simulator measures this.