What you need to know before getting started

The platform is built for retailers operating two or more physical store locations who need a unified view of inventory across all of them. It works across product categories: apparel, home goods, sporting goods, electronics accessories, specialty food retail, and others where stock management across locations is a recurring operational challenge.

The platform is not designed for single-location retailers or for e-commerce only operations. It is specifically oriented around the multi-location inventory coordination problem: knowing what is where, moving it when needed, and planning for what each location will need next.

The platform connects to point-of-sale systems to receive real-time sales data, which is what drives the live inventory counts. It also connects to ERP systems where retailers use them for purchasing and inventory control. The technical team handles integration setup during onboarding.

Where a retailer uses a POS or ERP system that requires a custom integration, the team assesses compatibility during the discovery phase before any commitment is made. Not every system can be connected without additional development work, and the team is direct about that upfront.

Setup time depends on the number of locations and the complexity of the existing systems being connected. For retailers with standard POS integrations and a manageable SKU catalog, the technical setup typically completes within two to four weeks of contract signing. Training adds time on top of that depending on how many staff need to be brought up to speed.

Retailers with more complex environments, multiple POS systems across locations, or very large SKU catalogs should expect a longer integration phase. The team provides a realistic timeline estimate after the initial discovery conversation.

For the real-time dashboard and alert features to work from day one, the platform needs a live connection to the POS system at each location. For the forecasting module to produce meaningful projections, at least one year of historical sales data by location is needed. The team imports this during setup.

Dead-stock identification works from the moment the platform has current inventory counts and a defined threshold period. It does not require historical data to function, though having history makes the reports more informative about how long items have been stagnant.

The platform has role-based access so different team members see what is relevant to their work. Store managers typically access the dashboard for their location, receive alerts relevant to their store, and initiate or respond to transfer requests. District managers see across multiple locations. Buyers and merchandisers access the forecasting and dead-stock reporting tools.

System administrators at the retailer control user permissions and can configure which alerts go to which roles. The platform does not require a dedicated IT resource to maintain on an ongoing basis.

Inventory and sales data is transmitted over encrypted connections and stored on servers located in the United States. Access to the platform requires authentication, and all user sessions are logged. The platform does not share retailer data with third parties for any purpose other than the operation of the service itself.

Retailers retain ownership of their data. On termination of service, the team provides a full export of the retailer's data in a standard format before access is closed. The full terms of data handling are described in the platform's service agreement and privacy documentation.