Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: SmartFACT Data

Start here: Operator

Maintain permitted table versions, refresh sources and prepare controlled data outputs.

Review edition · 25 October 2026 · For Operator

On this page

Use SmartFACT Data to maintain permitted reference data and inspect the exact source versions behind an output. The application includes native reference tables, external-sheet snapshots, saved selections, file feeds and shop connections. Each workflow has its own authority and confirmation.

Check the source before using it

Open Reference tables for data owned here or External sheets for received snapshots. Confirm the source name, current revision, receipt time and status. An external source's freshness interval is a check, not an automatic refresh schedule. A failed or stale source needs investigation before its values are treated as current.

Owner OR Operator can edit ordinary native reference tables. The WooCommerce SKU mapping template instead requires Author. For a permitted table, edit only the intended saved data and inspect the proposed changes. Review removals explicitly and record a meaningful reason before Save new version. A matching key, row identity and displayed row position are different concepts.

Prepare output deliberately

Test a query helps inspect matching data without changing source records. Run released selection uses an already reviewed selection; its result is current data, not a new rule approval. Data feeds need Preview current inputs before generating the exact file.

For a KitProof feed, inspect jobs, warnings and source revisions. Generating the file does not deliver it automatically or make KitProof accept it. Import it through KitProof's own preview and acceptance workflow. Do not infer cancellation from a job missing in a later file.

Handle shop work within its controls

Where a connected shop is available, inspect order mapping, held lines, stock outcomes and delivery evidence. Use only the operational actions offered to your role. A changed SKU table does not itself activate a shop mapping or rewrite an earlier accepted conversion.

If an answer is uncertain, use its retained original request or refresh the recorded state as directed. Starting another save, generation or order decision can create conflicting work. Give a Supervisor or Owner the source, version, order and visible reason when escalating.

Follow Review and save table data, Refresh external sheets and Generate a feed file. Keep the current data result separate from the approval that selected its rules.