Prima and Virtualstock
Integration Agency & Consultants
Scaling marketplace sales creates immediate friction when Virtualstock orders and Prima inventory levels drift apart. This usually becomes painful when manual reconciliation can no longer keep pace with order volume, leading to oversell risks or missing financial entries. We connect these systems so sales orders post into Prima for fulfilment while inventory availability stays in step across every channel. This ensures finance can trust the sales ledger and operations can fulfil from a single source of truth.
Auditing your stock and ledger architecture
Cogent2 connects your Prima and Virtualstock integration swiftly, ensuring your ERP and Marketplaces work together effectively. Our consulting services are invaluable, with system audit services that uncover inefficiencies and integration gaps across Prima, Virtualstock, ERP, and Marketplaces. These audits empower both our consultants and your team to take decisive action, helping your technology ecosystem run smoothly and efficiently. This means you can deliver a consistently excellent experience to your customers, with confidence that your systems are optimised for performance and reliability.
Solution Design
For the Prima and Virtualstock integration, we design with Prima as the master for product data and inventory. Sales orders are typically sequenced to post from Virtualstock into Prima on a defined interval, ensuring the finance team has a single ledger for all marketplace revenue. A key design trade-off involves inventory sync frequency. We prioritise accuracy over immediate updates, using a defined cadence to push stock levels from Prima to Virtualstock. While this introduces a minor operational latency, it avoids the risks of inconsistent data and ensures marketplace availability is backed by actual warehouse capacity. This design enables finance to reconcile revenue within Prima while operations teams fulfil orders from a single source of truth. It protects the financial trust boundary by ensuring every sale is recorded in the ERP correctly.
Mapping product data and order flows
The integration establishes Prima as the system of record for product master data and inventory, while Virtualstock pushes marketplace orders into Prima for fulfilment and financial processing. Data mapping ensures that pricing, descriptions, and attributes remain synchronised, preventing fragmented product data across sales channels. Timing rules are configured to post orders on a defined schedule, reducing the window for stock discrepancies. By anchoring the flow in Prima, the integration maintains data integrity for the financial team, while monitoring surfaces any missed order ingestion or attribute mismatches that could stall fulfilment.
Orchestrating workflows on secure IPaaS infrastructure
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations ensures secure, efficient integration between Prima, Virtualstock, ERP, and Marketplaces. Prima and Virtualstock integrations are delivered with ease, connecting ERP systems and Marketplaces while maintaining strict data protection. IPaaS platforms simplify complex connections, automate processes, and support compliance, making integrations more reliable and scalable for businesses needing robust, secure solutions.
Surfacing record level sync exceptions
Standard dashboards often miss the subtle data mismatches that cause month-end reconciliation to fail. Visibility depends on surfacing failures at the record level, such as when a marketplace order cannot map to a Prima product ID or when a stock update is rejected by a specific channel. Hidden issues compound when stock levels drift over time without being flagged. The Cogent platform provides operational intelligence by prioritising these exceptions, allowing teams to resolve sync errors before they impact customer experience or financial accuracy.
Practical handover for finance and operations
We hand over the operating model to your finance, operations and ecommerce teams so they can manage the integration confidently. Training focuses on daily oversight: finance learns to reconcile Virtualstock marketplace reports against Prima sales orders, while operations teams are taught to identify and resolve SKU mapping exceptions. We define who owns each exception type, ensuring that missing product codes or failed order imports are corrected at the source. All documentation is operational, written for the people running the business rather than a technical manual. This ensures your team can detect and resolve issues before they impact month-end reporting.
Post launch governance and data integrity
After launch, we monitor the integration to identify and resolve operational drift before it impacts reporting. Support focuses on maintaining data integrity between Virtualstock sales and Prima records by tracking order ingestion health, stock sync latency, and SKU mapping exceptions. When new products are listed without corresponding Prima records, we surface these gaps for correction. This ensures finance and warehouse teams manage the daily flow without chasing unexplained variances. We act as the technical bridge, ensuring the architecture remains stable during peak trading periods. Our objective is to ensure orders post correctly for fulfilment without manual intervention.
Common failures
Inventory latency and overselling
Operational impact: Virtualstock sells SKUs that Prima has already allocated to other channels. This results in cancelled Sales Orders, harms the customer experience, and forces fulfilment teams to manage exceptions. It also erodes trust in inventory data across all sales channels, complicating demand planning.
Prevention / Action: Establish Prima as the sole source of truth for stock levels. The integration should synchronise Prima’s 'available to sell' figure, not just the 'on hand' quantity, to account for existing allocations. Schedule frequent delta updates (syncing only changed SKUs) to Virtualstock to minimise latency and consider configuring a small stock buffer in Virtualstock as a final safety measure.
Inaccurate product data
Operational impact: Incorrect pricing, descriptions, or attributes are pushed to Virtualstock, leading to non-compliant marketplace listings or incorrect prices being published. This can result in financial losses on unprofitable sales and requires significant manual effort from merchandising and finance teams to correct data across hundreds or thousands of SKUs.
Prevention / Action: Centralise all product master data ownership within Prima. The integration logic should be configured to always treat Prima as the master record, overwriting corresponding product data in Virtualstock on each sync. Define a strict operational process where all product information changes are made only in Prima to maintain a single source of truth.
Dispatch confirmation and tracking failures
Operational impact: If Prima's dispatch records, including carrier and tracking numbers, do not update Virtualstock promptly, marketplace SLA breaches are likely. This jeopardises the seller's account status and can delay payouts. Customer service teams are then forced to handle customer queries without reliable tracking information, increasing ticket volume and resolution time.
Prevention / Action: Ensure Prima's carrier list is correctly mapped to the specific carrier codes required by Virtualstock. The integration's logic should trigger an immediate push of the fulfilment update to Virtualstock as soon as the dispatch record is created in Prima. Implement robust monitoring and an exception handling queue for any failed updates, allowing the operations team to investigate and resolve issues without delay.
Sales order and financial mismatches
Operational impact: Sales Orders created in Prima do not precisely match the values on the Virtualstock order, especially concerning discounts, promotions, or shipping fees. This creates significant reconciliation challenges for the finance team. They must manually investigate discrepancies between marketplace payout reports and Prima's sales ledger, delaying the month-end close process.
Prevention / Action: The integration must accurately map all financial data from the Virtualstock order to the corresponding fields on the Prima Sales Order. This includes line-item values, tax, and any separate charges. Document a clear exception handling process for the finance team to manage any unavoidable discrepancies, ensuring that financial reporting remains accurate.
Frequently asked questions
Which system holds the master record for product information and stock levels?
In this operating model, Prima acts as the system of record for product master data, including SKUs and pricing. Inventory levels are also mastered in Prima, which then updates Virtualstock to ensure accurate availability is shown across marketplaces. This helps prevent overselling by ensuring Virtualstock stock figures reflect Prima actual on-hand and available quantities.
How does the integration handle stock that is allocated to other orders but not yet shipped?
To avoid overselling, the integration is typically configured to subtract Prima 'Allocated' stock from the total on-hand quantity before syncing the final 'Available' number to Virtualstock. If this logic is missed, stock shown on marketplaces remains inflated, leading to orders for items already promised to other customers.
Our teams use generic 'non-stock' codes in Prima. How does the integration handle these?
Using generic item codes in Prima is a common point of failure. When Virtualstock pushes a sales order containing a marketplace SKU that lacks a specific match in Prima, the order import may fail or require manual intervention. The integration works best when every marketplace SKU maps to a unique product record to ensure clean fulfilment and financial processing.
How does this help with financial reconciliation?
The integration addresses this by posting each marketplace order from Virtualstock into Prima as a unique Sales Order. This creates a traceable link for the entire order-to-cash process, simplifying reconciliation and reducing the manual re-keying that often leads to month-end discrepancies between marketplace reports and your internal ledger.