How a best-practice SAP Business One re-implementation with Produmex WMS uncovered a major insurance shortfall and gave a fragrance manufacturer a trustworthy ERP
| Industry | Fragrance Manufacturing & Distribution |
| Starting Point | SAP Business One, live but configured by a previous implementation partner |
| Solution Deployed | SAP Business One (reconfigured to best practice) + Produmex WMS |
| Core Challenge | No inventory traceability, no system-based quality control, and no safeguards against unauthorized transaction changes |
Zero
Unauthorized deletions of inventory or production records after go-live
~55%
Of true inventory value left uninsured, now identified and closed
100%
Batch, expiry, pallet & bin traceability at a single click
Executive Summary
A global fragrance manufacturer and distributor was running SAP Business One, implemented and managed by a previous partner. On paper, the ERP was live. In practice, it gave management no real visibility or control over inventory, quality, or production. Warehouse stock could not be tracked by pallet or bin, quality control lived entirely outside the system in spreadsheets and hand-applied stickers, and there were no controls in place to stop users from altering or deleting production transactions. The result was a system that technically existed but couldn’t answer the questions that matter most: what inventory does the business hold, where is it, and can the numbers be trusted?
Pinnacle was engaged to take over the client’s SAP Business One environment, correct its configuration, and close these gaps at the root. We deployed Produmex Warehouse Management System (WMS) on top of SAP Business One, rebuilt the ERP configuration to best practice, and enabled transaction-level, stored-procedure controls to lock down unauthorized changes to inventory-impacting records. As part of the rollout, we mandated a full physical inventory count — and it revealed that actual physical inventory was worth more than double (roughly 2.3 times) what the business had insured, leaving over half of its true inventory value completely uncovered and undetected under the previous system.
The Challenge
When Pinnacle took over the environment, the existing SAP Business One system was, in practice, unable to give the business reliable information. Four gaps stood out:
1. No warehouse-level inventory tracking
- Inventory was tracked only at a generic item/warehouse level — there was no visibility of stock by pallet or bin.
- Warehouse staff had no system-driven way to locate stock, which meant inefficient picking, put-away, and cycle counting.
2. Quality control performed entirely offline
- QC checks were recorded manually in spreadsheets, completely disconnected from the ERP.
- Approved items were identified by pasting stickers onto cartons and pallets — a manual, error-prone, and non-auditable process.
- No QC results existed in SAP Business One at all, so status could never be verified, reported on, or tied back to a batch or transaction.
3. No transaction-level controls
- No stored procedures or validation controls were enabled anywhere in the system.
- Users could freely delete inventory-related entries during production postings.
- This created ongoing misreporting of inventory quantities, product costing, and profitability, since production and consumption records could be altered or erased without a trace.
4. A system that couldn’t be trusted
Taken together, these gaps meant that although the business had a live ERP, management could not rely on it for accurate inventory positions, cost of goods, or margin reporting. The system simply wasn’t producing the information the business needed to make decisions — effectively, leadership was flying blind.
The Solution
Pinnacle proposed retaining SAP Business One as the core ERP while re-platforming warehouse operations onto Produmex WMS, a purpose-built warehouse management add-on for SAP Business One, and rebuilding the underlying configuration to close every control gap left behind by the previous implementation.
1. Reconfiguring SAP Business One to best practice
- Reviewed and corrected the existing configuration against standard SAP Business One implementation best practices.
- Enabled stored-procedure-based controls to prevent unauthorized deletion or backdated modification of production and inventory transactions.
- Restricted user actions that had previously allowed uncontrolled creation or removal of inventory, cost, and production entries.
2. Deploying Produmex WMS
- Implemented pallet- and bin-level tracking so every unit of stock is tied to a physical location in the warehouse.
- Digitized the quality control process, so QC results are captured and stored directly in the system against the relevant batch.
- Enabled batch and expiry tracking, replacing the manual, sticker-based identification process.
- Gave warehouse and management users single-click visibility of inventory by batch, expiry date, pallet, and bin.
3. Verifying with a full physical inventory count
As part of go-live, Pinnacle required the client to carry out a full physical inventory count rather than carrying forward the unreliable opening balances inherited from the previous system. That count was the mechanism that surfaced the true inventory value — more than double what was actually insured — and the resulting coverage gap equal to roughly 55% of the client’s true inventory position.
Before vs. After
| Area | Before | After |
|---|---|---|
| Inventory tracking | No pallet- or bin-level visibility | Full batch, expiry, pallet & bin tracking via Produmex WMS |
| Quality control | Manual spreadsheets and physical stickers; no system record | QC results captured and stored in-system against each batch |
| System controls | No stored procedures; unrestricted deletion of production entries | Stored-procedure controls restrict unauthorized addition/deletion |
| Inventory accuracy | Unknown; understated or misreported cost and inventory | Verified via physical count — true value ~2.3x prior assumptions |
| Insurance exposure | Coverage set against an unknown actual position | ~55% coverage gap identified and flagged for correction |
| Reporting | System could not provide reliable information | Real-time, accurate inventory, cost, and QC reporting |
Results & Business Impact
- Uncovered an insurance shortfall equal to roughly 55% of the client’s true inventory value — actual stock was worth more than double (~2.3x) what was insured — a critical financial risk the client had been unaware of, now actionable with their insurer.
- Eliminated uncontrolled deletion of production and inventory transactions, removing a root cause of inventory, cost, and profit misreporting.
- Digitized quality control end-to-end, replacing manual logs and physical stickers with in-system QC records tied to each batch.
- Enabled single-click inventory visibility by batch, expiry, pallet, and bin — real-time traceability that simply didn’t exist before.
- Restored management’s confidence in the ERP as a single source of truth for inventory, cost, and production data.
Conclusion
This engagement illustrates a gap we see often: the difference between having an ERP system and having one that’s properly configured and controlled. A prior SAP Business One implementation had left the client without warehouse traceability, without system-based quality control, and without safeguards against data manipulation — and those gaps had quietly masked an insurance shortfall equal to roughly 55% of true inventory value until a disciplined, best-practice re-implementation brought it to light.
By pairing SAP Business One with Produmex WMS and enforcing proper transactional controls, Pinnacle delivered more than a functioning system — we delivered a trustworthy one: accurate inventory records, auditable quality control, and protection against the kind of unchecked transaction deletion that had been distorting the client’s financial picture.
Is your ERP telling you the truth about your inventory?
If your SAP Business One environment isn’t giving you reliable visibility into stock, quality, or margins, it may be a configuration problem — not a platform problem. Talk to Pinnacle about an environment health check.
