Items vs. Inventory, and the Ctuit/Radar/Compeat Connection

Items and inventory are different jobs

• Items in Ottimate are what you bought, as captured from invoice lines: the product, pack size, price, and its GL mapping.  Items power coding, price tracking, and item validation.

• Inventory is what you have on hand, tracked in your inventory or store-management system — not in Ottimate.  Ottimate feeds your inventory system with what was purchased; counting and costing stock stays in that system.

So "why doesn’t Ottimate show my on-hand counts?" — because that is inventory.  Ottimate’s job is getting clean, item-level purchase data into the system.

The Ctuit export (Radar, now part of Compeat)

Ctuit’s restaurant platform (branded Radar, later acquired by Compeat, now part of Restaurant365) takes item-level purchase data from Ottimate through a dedicated export, separate from your accounting export:

• Invoices are exported to Ctuit with their line-item detail once processed.

• Pack sizes matter: Ctuit tracks items in your units, so Ottimate pack sizes are mapped to your Ctuit pack sizes.  Maintaining those mappings is the "Map Pack Sizes" permission; running the export is "Export to CTUIT."

• Invoices can be marked as exported or un-exported to Ctuit independently of the accounting export, and a Ctuit export report shows what has gone across.

The same pattern applies to other inventory integrations: the accounting export sends the financials to your ERP, and the inventory export sends item detail to your inventory system.  One invoice, two destinations, each in the format that system needs.