You can add up to 100 custom attributes and unlimited number of metrics. If you need to add more than 100 custom attributes, please let your Customer Success Manager know.

Please see below the character limits for different set of attributes.

Below are the recommended historical data for validation. This give Toolio enough sample set to iron out the kinks in your data.

We recommend importing all the historical data that will be helpful to your future decisions. We suggest loading the following data durations into Toolio.

Data update frequency will depend on the needs of the business, but our suggested approach is sending data daily.
If daily is not an option, you can send it weekly, after the last day of the week on your retail calendar.

When you are updating data, you only need to send the relevant data, i.e. you don’t need to send a full data dump every week. Below are some rules of thumb on how much data to send every week.

We recommend having the integrations or data feeds to be synced as early as possible within the day at a time after which you know the sources of record (e.g. ERP or Data Warehouse) are fully updated. A typical recommendation would be some time between 1-4AM in your organization local time.

Let's say that you have set up your data warehouse to be the source of truth for your Toolio integration. Review with your tech team, when your data warehouse is typically updated. We typically see the update process starting at midnight and taking a few hours. Accordingly, set the Toolio integration trigger time to be 30-60 mins after the time your database would be updated.

Yes. Toolio receives your data as separate feeds (Sale, Inventory, Purchase Order, Receipt, Product, and so on), and each feed can come from a different system. You don't need one system that covers everything. For example, many customers send Sales and Inventory from their ecom platform, and Purchase Orders, Receipts, and Product data from their ERP.

When deciding which system should send each feed, choose the system where that data is created or is most accurate.

If your team already combines data from several systems in a data warehouse (e.g. Snowflake or BigQuery), you can send all feeds to Toolio from that one connection instead.

This is common during a system migration, or when sales come from more than one place (for example, ecom sales from one system and store sales from another). How Toolio handles it depends on what each system sends:

Toolio decides whether two rows are the same record using the unique ID for that feed:

Every business's mix of systems is different. Your Implementation Specialist will work with you to map out what you need from each source and plan how to send it, so every system contributes its data without overwriting what another system sends. If you're already live and plan to add or change a source, reach out to your Customer Success Manager first.

Toolio defines a unique inventory record using the combination of:

If duplicate records exist for the same combination, Toolio will take the latest value from the feed as the source of truth.

In some cases (though this is not the expected pattern), you may want to aggregate duplicate values instead of overwriting them. Toolio supports this through the organizational feature flag aggregateDuplicatesOnInventory, which combines duplicate values (e.g., units).

If the feature flag aggregateDuplicatesOnInventory is turned on, Toolio enforces a limit of 1,000,000 rows for each inventory feed upload.

If your feed exceeds this limit, you’ll need to:

This happens when you are sending POs incrementally and have deleted POs on your system vs. marking them as inactive on your end. To prevent these "stale POs", we can update your configuration to assume that you're sending all Open POs at any point, so that Toolio automatically deletes all POs that are not included in your latest PO feed.
If you would like to make this configuration change to allow "Full Purchase Order Import", please get in touch with us and we can make the change.