Factory data.
Kept in order.

Start free. While SmartFACT Data is in early access, registration is closed: your enquiry tells us what data you need to bring in, where it is kept now and which SmartFACT products rely on it. We then agree the scope and the people who need access, enable your organisation through SmartFACT Accounts and stay involved while the first data arrives. Sending the form does not open an account by itself.

Uploaded sheets, whether laid out as expected or mapped to that layout, cost nothing while SmartFACT Data is in early access, and neither do the Shopify, WooCommerce and PrestaShop connectors. Connecting anything else, such as SAP, an ERP or MRP system, EDI or a bespoke API, is a paid integration, and its price is agreed with you before work begins. Nothing is paid through this website. To start a paid integration, tell us about the system at https://data.smartfact.ai/integration-enquiry.

No. A sheet upload, a pasted block of rows or the grid itself is enough, and once saved the table stands on its own without the original file. A Google Sheet kept live and connected counts as a paid integration, scoped with you.

Shop orders, customer and supplier codes, lookup values and the structured inputs your SmartFACT products need. Together we set the fields and test them with representative values. It is not a stock ledger, and it does not hold product manufacturing rules.

A receiving product works from a saved version and accepts it only after its own review. LabelRules activates a reference table once reviewed, and KitProof takes reviewed job files. Each product also keeps its own import, and data from SAP, an ERP or other software comes through a paid integration built through data.smartfact.ai and reaches the product the same way.

Only as a paid integration we scope and build for you. By default data comes in and nothing goes back. Where you want a result returned, such as a stock figure, a goods receipt or a purchase order, it is agreed with you, priced before work starts and reviewed before it goes live. Tell us about the system at https://data.smartfact.ai/integration-enquiry.

No. A save only adds a table version. Preparing a supported output is a separate, deliberate step, and the receiving product still runs its own review and activation. Exports made earlier, and KitProof files already generated, stay linked to the versions that produced them.

No. Only people your organisation authorises through Accounts can see it. A file you download is for your own authorised workflow, and where it goes next is up to you. Saving a table never publishes a dataset.

Yes, as the place where the customer, supplier and internal values behind a mapping are kept and checked. Linking your EDI software or provider so that messages are actually sent or read is a paid integration, scoped with you and built through data.smartfact.ai.