Describe a SmartFACT Data SKU mapping in plain English
Type a shop SKU mapping in plain English, answer the AI's question about the missing details, inspect the complete proposed SKU table and save it deliberately as a draft.
For authors
Type a shop SKU mapping in plain English, answer the AI's question about the missing details, inspect the complete proposed SKU table and save it deliberately as a draft.
Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.
Plain English to a checked draft
- Load the spares shop SKU table
Load the spares shop SKU table
Load the spares shop SKU mappings from SmartFACT Data. Each row maps one shop SKU to a stock item and the base units one shop unit represents. Only the washer pack is mapped so far.
- Choose Complete shop SKU mapping rows
Choose Complete shop SKU mapping rows
Choose Complete shop SKU mapping rows as the configuration task, so the change covers the whole table: every existing row stays visible next to the new one.
- Start from the current SKU table
Start from the current SKU table
Start from the current approved SKU table, revision 1, with its washer pack row.
- Load the SKU table controls
Load the SKU table controls
Load the controls for the whole SKU table. This reads SmartFACT Data and does not save anything.
- Choose the SKU table to describe
Choose the SKU table to describe
Choose Complete shop SKU mapping rows under Change to describe, so the proposal covers every row of the table and the reason saved with the change.
- Type the requirement in plain English
Type the requirement in plain English
Type the requirement as the team wrote it: use stock item CB-HINGE for shop SKU CB-HINGE-PAIR at two base units per shop unit.
- Ask for a proposal
Ask for a proposal
Ask for a proposal. The AI replies with a question instead of guessing: every row needs its own permanent row ID, and Data saves a reason with every table change.
- Add the details the AI asked for
Add the details the AI asked for
Keep the requirement and answer the question: give the row the ID hinge-pair and save the reason "The spares shop sells control box door hinges in pairs."
- Ask for the complete proposal
Ask for the complete proposal
Ask again. The AI now returns the complete SKU table with the new row. Nothing is saved until you choose to save it.
- Read the restatement of the change
Read the restatement of the change
Read the restatement. It says in plain words that the proposal changes the complete shop SKU mapping rows. Every value it saves is listed next.
- Check what will be saved
Check what will be saved
Read what the change will save, field by field. Every column has its name: Shop SKU, Stock item and Base units per shop unit.
- Check the new hinge pair row
Check the new hinge pair row
Check the new row hinge-pair: shop SKU CB-HINGE-PAIR uses stock item CB-HINGE at 2 base units per shop unit, so one pair sold takes two hinges.
- Check the washer pack row is kept
Check the washer pack row is kept
Check the washer pack row is unchanged: WASHER-PACK-04 still uses WASHER-M6 at 0.25 base units per shop unit. The change replaces every row with this complete list.
- Check the saved reason
Check the saved reason
Check the reason saved with the change: "The spares shop sells control box door hinges in pairs."
- Confirm you checked the whole proposal
Confirm you checked the whole proposal
Confirm that you checked every row and the reason. SmartFACT Data still validates the complete table when it saves.
- Save the proposal as a draft
Save the proposal as a draft
Save the proposal as a draft. Saving does not approve, release or apply the mapping, and no shop order or stock changes: the expected results, proof and an independent review come next.
Only a draft was saved. The expected results, the native proof and an independent review come next. Nothing reaches a shop order or stock until a reviewed release is activated.