“Connect Accredo to the website” sounds like one task. In practice, it is a set of decisions about products, categories, stock, pricing, customers, orders and the direction each piece of information should travel.
The best integrations do not synchronise everything simply because they can. They keep Accredo in charge of operational data while giving the ecommerce platform what it needs to create a strong customer experience.
Products and variants
Begin with identifiers. A stable product code or SKU needs to match across systems. Decide how variants, components, kits, discontinued items and web-only products are represented.
Accredo may own the core name, code, dimensions, tax settings and status. The website may hold richer marketing copy, search terms or presentation fields. If ownership is split, document it field by field so one sync does not erase the other system’s work.
Categories and images
Operational product groupings do not always make good website navigation. Some businesses can map Accredo categories directly. Others need a web-specific structure built from attributes or controlled rules.
Images may come from Accredo, a product information source or the CMS. Define how new assets are detected, resized and ordered. Large original files should not be pushed straight into customer pages without an image workflow.
Stock and backorders
Choose the stock concept the website will display: physical, available, branch-specific or aggregated. Account for allocations and incoming purchase orders if the customer promise depends on them.
Backorders need explicit rules. Identify eligible products, the status shown online and how expected dates move from Accredo to customers. Decide how often stock updates and whether checkout performs a final availability check.
Pricing and promotions
Retail, wholesale and customer-specific pricing can be driven from Accredo so teams do not manage price rules twice. Define priority when contract pricing, quantity breaks, sale pricing and promotions overlap.
Tax display, currencies and rounding require test cases. A few cents of difference between the website and final order can create disproportionate support work.
Customers and groups
New ecommerce registrations may need approval before creating or linking an Accredo account. Existing customers need a dependable matching process; email alone is not always a safe unique identifier.
Customer groups, contacts, delivery addresses, credit settings and price rules should have clear ownership. For B2B customers with several users, preserve the relationship between individual login and company account.
Orders and status
Agree when an order enters Accredo: at checkout, after payment, after fraud review or after staff approval. Map products, freight, discounts, tax, addresses, reference numbers and payment information.
Status can then return to the website as the order is accepted, allocated, dispatched or backordered. Tracking and invoice information may also be exposed where appropriate.
Operational controls
The integration layer should provide connection status, activity history, useful errors and safe retries. A staging mode lets teams test data mappings and new releases without affecting the live store.
Permissions matter. Not every website user should be able to trigger a full sync or view customer data. Documentation should explain data ownership and recovery, not just installation.
Scope a complete path first
Start with a representative product, customer and order. Follow them from Accredo through the store and back again. Include a price change, stock movement and failure case. Once that path is dependable, extend the catalogue and edge cases.
Web Paste, through Australis Integrations, provides Accredo-to-CMS middleware for ecommerce platforms including BigCommerce. The model keeps teams working in Accredo while the storefront stays current, with a dedicated interface for managing and monitoring the connection.
