Syncing Vendor Catalogues Between Counterpoint And Ecommerce

When a retailer moves away from NCR Retail Online, connecting Counterpoint to a replacement ecommerce platform becomes a practical systems project rather than a simple plug-in installation. Vendor catalogues, stock quantities, customer orders, pricing rules and product images all need to travel between systems without creating duplicate or inaccurate records.

For Australian retailers, the issue is especially visible when a store sells through several channels. A fashion shop in Melbourne may receive online orders while staff serve customers in-store. A gift retailer in Brisbane may rely on supplier drop-shipping for some lines, while a regional store needs dependable stock figures despite longer delivery routes.

Counterpoint should remain the operational source for inventory, purchasing and retail sales where possible. The non-NCR ecommerce platform should handle the online storefront, checkout, search, merchandising and customer experience. A carefully designed integration keeps those responsibilities clear and reduces manual catalogue maintenance.

The process begins with vendor data quality. Supplier spreadsheets often use inconsistent SKUs, descriptions, pack sizes, tax settings and image names. Before synchronising anything, the retailer must decide which fields belong to the supplier, which belong to Counterpoint and which are maintained exclusively online.

Define Data Ownership First

A reliable catalogue feed starts with a field ownership map. The vendor may provide product name, barcode, wholesale cost, case quantity and basic specifications. Counterpoint can hold the sellable SKU, retail price, stock-on-hand and purchasing information. The ecommerce platform may control search keywords, category placement, promotional copy and lifestyle photography.

This division prevents a nightly import from overwriting carefully written online content. It also makes troubleshooting easier. If a price is wrong, the team can identify whether the problem began in a supplier file, a Counterpoint export, a transformation rule or the storefront import.

Create a master product key before importing vendor records. The preferred identifier is usually a stable SKU or manufacturer barcode, not a product name. Names change frequently, while a consistent key allows the connector to update an existing item rather than create a second listing.

Prepare Counterpoint Catalogue Data

Counterpoint data often needs cleaning before it can support an online catalogue. Review inactive items, discontinued products, duplicate SKUs, missing descriptions, invalid barcodes and products with no sell price. Separate stock items from non-stock services, deposits and internal-use records so they do not accidentally appear in the web shop.

Vendor feeds also need normalisation. Convert measurements into consistent units, standardise colour and size values, and agree on how parent products and variants will be represented. A shoe supplier might use “8,” “08” and “AU 8” for the same size; the ecommerce platform should receive one approved value.

Bulk processing can save substantial time during migration or seasonal range changes. Retailers replacing an old NCR workflow may find this bulk upload approach useful when designing a Magento import process, provided that validation occurs before records reach the live store.

Choose An Integration Pattern

A scheduled CSV or XML exchange is often sufficient for a modest Australian retailer. A job can export catalogue and inventory changes from Counterpoint, transform them into the format required by WooCommerce or Magento, and import them at set intervals. This approach is easier to audit, although stock may be delayed by an hour or several hours.

Middleware is more suitable when a business has many suppliers, multiple warehouses or different rules for each product family. It can store a supplier feed, apply transformations, log rejected rows and send alerts when an import fails. APIs offer closer to real-time updates, but only when Counterpoint, the connector and the ecommerce platform can all support stable endpoints and appropriate authentication.

Stock frequency should reflect the product. Fast-moving electronics or limited-release collectibles may need frequent updates to reduce overselling. Slower homewares can often tolerate scheduled synchronisation. Australian delivery expectations also vary: a Sydney customer may expect rapid dispatch, while a buyer in regional Western Australia may accept a longer lead time, making accurate availability and delivery messaging essential.

Map Products Prices And Tax

A product mapping document should define every important field, its source, its destination and its transformation rule. Include SKU, parent SKU, barcode, title, description, brand, category, variant attributes, images, cost, retail price, sale price, stock quantity, shipping weight and availability status.

Australian tax treatment deserves specific attention. Standard taxable goods generally require GST handling, while some products may have different treatment. The online platform, accounting settings and Counterpoint configuration must agree on whether prices are stored inclusive or exclusive of GST. The display price, tax calculation and invoice total should be tested together rather than checked independently.

Use a controlled pricing rule instead of copying every vendor price directly to the storefront. A retailer may apply a margin by category, round prices to an approved ending, or maintain a separate promotional price. Record the original source value and the applied rule so staff can explain why an online price differs from a supplier spreadsheet.

Personalisation adds another layer. A gift shop may sell engraving, monograms or colour choices that are not simple inventory variants. Before publishing these products, define whether the customisation is stored as an order option, a separate SKU or a production instruction; examples of personalised product options illustrate why these details need to reach fulfilment accurately.

Protect Orders And Customer Records

The flow should usually be two-way. Counterpoint sends products, prices and available stock to the ecommerce platform. The store sends confirmed online orders back to Counterpoint for fulfilment, payment reconciliation and stock reduction. Order status should then return to the storefront so customers receive accurate updates.

Avoid importing an order twice. Each order needs a unique external identifier, an import status and an error state. If an order contains a product that has become unavailable, the integration should hold it for review rather than silently substituting another item. Refunds, cancellations, partial shipments and backorders also need explicit handling.

Security controls must cover API credentials, administrator accounts, payment data and customer information. The retailer should review PCI guidance when moving from NCR Retail Online to another platform, especially where payment gateways, hosted checkout pages or third-party extensions change the scope of compliance work.

Australian businesses should also consider the Privacy Act and the Australian Privacy Principles when customer data moves between systems or suppliers. Keep only the information required for fulfilment, restrict staff access and establish retention rules. The Australian Consumer Law also makes accurate descriptions, pricing and availability important operational controls, not merely marketing concerns.

Test Monitor And Reconcile

Testing should begin with a small sample of vendors and products. Compare the supplier record, Counterpoint record and storefront listing line by line. Test new products, edits, discontinued items, variants, missing images, changed prices, zero stock and products with unusually long descriptions.

Run order tests using realistic Australian conditions, including GST, delivery to a metropolitan postcode, delivery to a remote postcode, click-and-collect and an address requiring manual review. Confirm that stock decreases once, the correct tax appears, fulfilment receives the right customer notes and the customer receives the intended email.

After launch, monitor import counts, rejected records, stock discrepancies and processing times. A daily reconciliation can compare Counterpoint stock with ecommerce stock for high-value or fast-selling products. Alerts should identify a failed supplier file, a sudden price change, a large quantity swing or an unusual number of products set to unavailable.

The retailer should keep a change log for mappings and integration rules. When a vendor changes column names or introduces a new variant value, the log helps staff identify the cause and restore service quickly. Scheduled backups and a documented rollback process are equally important during catalogue refreshes.

Establish A Sustainable Workflow

Assign ownership across the business. A buyer can approve supplier data, an inventory manager can verify stock behaviour, an ecommerce manager can maintain online content and a technical partner can support the connector. Without named responsibility, catalogue errors tend to remain unresolved because each team assumes another team owns them.

Set a regular supplier onboarding routine. New vendors should provide a sample feed, agreed identifiers, image standards, tax information and update frequency before their products are activated. Existing vendors should be reviewed when they change packaging, pricing, variant structures or fulfilment arrangements.

The practical next step is to select one vendor with a manageable product range, document its fields against Counterpoint and the chosen ecommerce platform, then test ten products and one complete order through the full synchronisation cycle.