Unleashed
Key Info:
Details
Inventory and costing
Unleashed tracks stock across warehouses and can use batch or serial information where traceability is required. Product records, units, stock movements and valuation support operational and financial control. Buyers should reconcile opening quantities and costs, then test transfers, adjustments, returns, landed costs and a backdated transaction. The proof should explain any difference between operational stock, available stock and accounting values.
Purchasing, sales and fulfilment
Supplier records, purchase orders and receiving connect incoming supply to inventory. Sales orders, allocations, picking and shipment activity coordinate customer demand, while replenishment and reporting help teams plan stock. A representative scenario should include a partial delivery, substitute supplier, customer return, split shipment and order cancellation to expose how commitments and availability are recalculated.
Production and integrations
Manufacturing functions support bills of materials, assemblies and production activity for businesses that transform stock. Integrations connect accounting, ecommerce and other operational systems. Teams should verify which system owns product, price, tax, customer and cost data and how synchronization errors are surfaced. Test one failed connector run and confirm that administrators can replay or reconcile it without duplicating orders.
Fit and evaluation
Unleashed may suit product businesses that want inventory and light manufacturing control connected to accounting and sales channels. It may be less appropriate where deep shop-floor scheduling or highly customised enterprise processes are essential. Evaluate location limits, transaction volumes, traceability, permissions, reports, API, onboarding, support, backup and integration costs, then complete a month-end stock and margin reconciliation using representative data.
Decision record
Record the tested stock model, location structure, exception scenarios, required edition, verified integrations, data ownership, migration assumptions and named operational owner. Define opening-balance approval, cutover reconciliation, user training, support escalation and the measures that will determine whether the rollout is successful. Include a rollback threshold and a dated review of data quality after the first operating cycle. Keep unsupported pricing, customer-size, language and device values blank until a current official source maps them exactly to a BBS field.