Skip to main content
Talk to an expert
Kerridge Commercial Systems ERP system

Kerridge K8 integration for ecommerce

Connect K8 stock, pricing and orders to every ecommerce channel cleanly. Kerridge K8 holds the commercial record for wholesale stock, trade-account pricing and customer credit. iWeb connects K8 with ecommerce storefronts, trade portals and branch systems so inventory stays accurate, customer pricing rules are respected and orders flow to fulfillment without manual rework. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: connector, plugin, extension, API integration, system integration.

Kerridge K8iWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Magento Open Source · Adobe Commerce · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Kerridge K8 integration gives you.

Ecommerce stock accuracy

Online inventory matches warehouse reality. Stock depletes consistently across channels and branches, reducing oversell, refund surprises and customer disappointment.

Trade-account pricing trust

Customer-specific pricing, volume discounts and credit limits flow cleanly from K8 to trade portals and ecommerce, so buying teams see the prices they negotiated and checkout doesn't reject orders on credit grounds.

Order-to-despatch clarity

Web and trade orders move through K8 without manual rework. Customers see order acknowledgements, tracking and despatch confirmations in real time. Finance reconciles invoices against orders correctly.

Multi-channel stock planning

Buyers and merchandisers see stock allocated fairly across branches, ecommerce and trade channels. Peak trading no longer creates gridlock or requires emergency stock moves between systems.

Returns and credit velocity

Returns flow from ecommerce or branches into K8 without delay. Credits post to customer accounts on time. Refund disputes drop because K8 sees the full financial and stock picture.

02 · When it's worth it

Where a Kerridge K8 integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publishing live stock levels from K8 to ecommerce and branch tills
Syncing customer-specific pricing and credit limits to trade portals
Capturing web orders into K8 for acknowledgement and despatch
Handling returns, credits and customer account changes across channels
Reconciling invoices, payments and despatch confirmations back to K8
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Stock sync lag

K8 does not push live inventory updates to ecommerce by itself. Manual batch exports or third-party connectors are often required, leaving gaps where online stock becomes stale relative to warehouse reality, especially during peak trading.

Trade-account pricing complexity

K8 holds customer-specific pricing, volume breaks and credit limits, but delivering these rules to ecommerce storefronts or trade portals requires careful mapping and testing. Discrepancies between K8 rules and what is shown online cause confusion and margin leakage.

Order handoff friction

Orders from ecommerce must be mapped into K8's sales-order structure, including customer lookups, credit checks and stock reservations. Manual intervention or custom coding is often needed to bridge differences in data structure and business logic.

Multi-channel stock allocation

K8 does not natively understand ecommerce channels, marketplaces or branch stock separately. Without clear allocation rules, online stock can oversell while branches hold inventory, or vice versa.

Returns and credit flow

Returning goods and issuing credits through ecommerce or branches back into K8 often requires manual keying or disconnected processes, causing delays, duplicate credits or lost adjustments.

04 · The real work

Wholesale operators often run tight credit limits and negotiated customer pricing, so the integration has to bridge K8's trade-focused rules with ecommerce checkout without breaking mid-transaction.

05 · Where it sits

Where this integration sits in your estate.

Kerridge K8 holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Built for your platform, not a specific one. Kerridge K8 integrates with any ecommerce core through the same contract.

System of record
Source / owner
Kerridge K8
System of record for stock, pricing, customer accounts and order processing across wholesale and trade channels
  • Stock levels by location and availability
  • Base pricing and trade-account pricing rules
  • Customer master records and credit limits
  • Sales order creation and order acknowledgement
  • Despatch and shipment tracking
  • Invoices, credit notes and financial records
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Product catalogue and merchandising on the storefront
  • Shopping cart and checkout experience
  • Customer account login and profile management
  • Order placement and customer-facing confirmation
Connected neighbours
Integration layer
PIM
Product attributes, descriptions, media and taxonomy feed the storefront and ecommerce catalogues. K8 does not own product content.
Integration layer
OMS
Order orchestration, multi-channel stock allocation and fulfilment routing sit between K8 sales orders and warehouse or branch operations.
Integration layer
WMS and branches
Warehouse and branch operations execute picks, packs and despatches triggered by K8 orders. Stock movements feed back to K8 to update inventory.
Integration layer
Marketplaces and trade channels
Amazon, category sites and trade partner portals receive orders which are ingested into K8 for fulfillment. Channel-specific stock and pricing are managed by the integration.
Integration layer
Accounting and finance
K8 invoices, credit notes and financial records integrate with accounting systems for reconciliation and reporting.
Integration layer
CRM and marketing
Customer data and order history flow to CRM and marketing platforms for campaigns and retention, but K8 remains the source for customer accounts and credit.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Magento Open Source
  • Adobe Commerce
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • PIM (product content and enrichment)
  • OMS (order orchestration and stock allocation)
  • WMS (warehouse and branch picking)
  • Marketplace connectors (Amazon, eBay, category sites)
  • Search and merchandising (indexing and discovery)
  • CRM and marketing (customer data and campaigns)
  • Accounting and BI (invoicing, reconciliation and reporting)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into ERP
←From ERP
↔BOTH WAYS
Stock and pricing updates: Stock availability, base pricing, trade-account pricing and promotion data flow out of K8 to ecommerce storefronts and branch systems
Updates are typically batched but can run frequently to keep online inventory current and customer pricing accurate.
Web order intake: Orders from ecommerce storefronts, mobile apps and trade portals are captured into K8 as sales orders
K8 acknowledges receipt, assigns order numbers and triggers pick, pack and despatch workflows.
Despatch and tracking: Despatch confirmations, carrier tracking, and despatch notes flow out of K8 back to ecommerce platforms and customer-facing systems so shoppers and trade customers see real-time shipment status.
Customer account and credit changes: Customer master data, credit limits, payment terms and account status flow both ways between K8 and ecommerce or branch systems
Changes to credit or account status in K8 must propagate quickly to prevent overselling or broken checkout.
Returns, credits and adjustments: Returns authorisations, credit notes and stock adjustments from ecommerce, branches or customers flow into K8 to update inventory, customer account balances and financial records.
Invoice and remittance data: Invoices, credit notes and payment instructions flow out of K8 to ecommerce platforms, accounting systems and customer portals for reconciliation and payment processing.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Stock and pricing sync design

    iWeb designs the extract from K8, the transformation layer and the delivery to ecommerce platforms, branch systems and marketplaces. We set frequency (batch or event-driven), monitor for gaps and handle K8 downtime gracefully.

  2. 02
    Order ingestion and mapping

    iWeb builds the connector to capture ecommerce and trade-portal orders into K8 as sales orders. We handle customer lookups, address standardisation, credit checks and stock reservations so orders are acknowledgeable on arrival.

  3. 03
    Multi-channel stock allocation

    iWeb defines how available stock is divided across branches, ecommerce, marketplaces and trade channels. Allocation rules are codified in the integration layer and reviewed against peak trading patterns to prevent gridlock.

  4. 04
    Customer account and pricing governance

    iWeb maps K8 customer records to ecommerce customer accounts and ensures credit limits, payment terms and trade-account pricing rules stay in sync. Changes in K8 propagate to checkout and trade portals without delay.

  5. 05
    Returns, credits and exception handling

    iWeb builds the reverse flow: returns authorisations and credit notes from ecommerce flow into K8, adjusting stock and customer balances. Failed orders, credit-limit blocks and price mismatches are captured and reviewed.

  6. 06
    Monitoring and observability

    iWeb instruments the integration to track stock sync latency, order ingest lag, pricing mismatches and failed customer-account changes. Alerts surface problems before they reach customers.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataStock availability by location and channel
Source / ownerKerridge K8
Maintained byWarehouse and branch operations; sync layer publishes to ecommerce
NotesK8 holds the definitive inventory position. Ecommerce and branch systems receive calculated available-to-sell figures based on allocation rules and reservations.
DataBase pricing and trade-account pricing
Source / ownerKerridge K8
Maintained byCommercial and pricing teams; integration layer delivers to ecommerce and trade portals
NotesK8 holds list prices, customer-specific discounts, volume breaks and contract terms. Ecommerce publishes these to customers at checkout and in catalogues.
DataCustomer master records and credit limits
Source / ownerKerridge K8
Maintained byCustomer service and credit teams; changes propagate to ecommerce accounts and branch systems
NotesK8 is the source for customer identity, credit terms, payment methods and account status. Ecommerce and trade portals must respect these rules at order intake and checkout.
DataWeb orders and trade-portal orders
Source / ownerKerridge K8
Maintained byOrder ingestion layer captures from ecommerce and trade channels; K8 owns acknowledgement and fulfilment
NotesOrders originate in ecommerce or trade portals but are owned by K8 once received. K8 assigns order numbers, reserves stock, triggers picking and manages despatch.
DataDespatch confirmations and tracking
Source / ownerKerridge K8
Maintained byWarehouse and carrier operations; integration layer publishes back to ecommerce and customer systems
NotesK8 records shipments and integrates with carriers for tracking. Ecommerce and customers receive despatch notifications and tracking links but do not modify shipment data.
DataReturns, credits and refunds
Source / ownerKerridge K8
Maintained byReturns and credit teams; integration layer accepts returns from ecommerce and branches
NotesReturns authorisations, credit notes and stock adjustments are owned by K8. Ecommerce and branches initiate returns but K8 validates and finalises credits.
DataInvoices and financial records
Source / ownerKerridge K8
Maintained byFinance and operations teams; integration layer publishes to ecommerce and accounting systems
NotesK8 generates invoices, credit notes and payment records. Ecommerce and branch systems receive invoices for customer portals and accounting integration.
10 · Experienced integrator

Built this before

iWeb has designed and built Kerridge K8 integrations for wholesale distributors, trade operators and cash-and-carry businesses. We understand how K8's inventory structure, trade-account pricing rules and multi-location operations map to ecommerce storefronts, branch systems and marketplaces.

Designed stock allocation models that prevent oversell across ecommerce channels and branch locations, using K8 as the definitive inventory source.
Built order ingestion pipelines that map ecommerce and trade-portal orders into K8 sales orders, with customer validation, address standardisation and credit checks.
Implemented trade-account pricing and credit-limit delivery to ecommerce and trade portals, so customers see correct pricing at checkout and orders don't fail on credit grounds.
Instrumented K8 integrations with monitoring for stock sync lag, order ingest delays, pricing mismatches and customer-account drift, alerting operations before issues reach customers.
Handled returns, credits and stock adjustments flowing from ecommerce and branches back into K8, so refunds are timely and inventory reconciliation is clean.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify stock depletion consistency across ecommerce, branches and K8 during a simulated transaction cycle; confirm no oversell across channels.
Test customer credit-limit enforcement at checkout: confirm orders above credit are blocked, notification is sent to the customer, and K8 shows the blocked order.
Confirm trade-account customer sees their negotiated pricing and volume discounts at login and in the shopping cart; verify pricing matches K8.
Capture a web order into K8, confirm K8 assigns an order number, stock is reserved and an acknowledgement is sent back to the customer within 5 minutes.
Test K8 outage fallback: stop K8 for 30 minutes, confirm ecommerce continues using cached stock and pricing, then verify reconciliation after K8 recovers.
Initiate a return through ecommerce, confirm it creates a returns authorisation in K8, then post a credit note and verify the customer's account balance and refund are updated.
Confirm pricing or credit-limit changes made in K8 appear on ecommerce storefronts within the scheduled sync window and that alerts fire if the sync is delayed beyond SLA.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Stock oversell across channels

If K8 stock is not allocated by channel, ecommerce and branches can sell the same item twice. This happens when stock updates lag, allocation rules are unclear or K8 downtime breaks the sync.

Pricing mismatch on trade accounts

K8 holds negotiated customer prices, volume breaks and credit limits. If these rules are not published accurately to ecommerce or trade portals, customers see wrong prices at checkout or orders fail on credit grounds, causing disputes.

Orders stuck in ingestion

Ecommerce orders fail to map into K8 if customer records are missing, addresses are malformed, or stock cannot be reserved. Without clear exception handling, orders queue silently and customers never receive acknowledgements.

Returns and credits lost

Returns from ecommerce or branches require reverse logistics, credit-note generation and customer-account adjustments in K8. If these steps are manual or unmonitored, credits leak, stock discrepancies grow and customer refunds are delayed.

K8 downtime breaking checkout

If ecommerce relies on real-time K8 calls for stock or pricing, a K8 outage can stop checkout. Without caching or fallback rules, customers see errors or inventory appears wrong during recovery.

Credit limit enforcement gap

K8 maintains customer credit limits and payment terms. If these are not refreshed at checkout or are overridden without approval, orders exceed credit and create bad debts or payment recovery friction.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Kerridge K8 integrations.

How does stock sync work between K8 and ecommerce when we have multiple branches and channels?

iWeb designs an allocation model that divides K8 stock into ecommerce, branch and reserved inventory. Stock updates flow from K8 at regular intervals (typically hourly or on-demand), reflecting warehouse depletion and branch transfers. The allocation rules are reviewed during planning so that peak trading doesn't cause gridlock or oversell across channels.

What happens if K8 goes down during the day? Will ecommerce checkout still work?

iWeb caches the last known stock and pricing from K8 in the ecommerce platform or middleware. Checkout can continue using cached values, but orders may need manual review if credit limits or special pricing apply. After K8 recovers, the integration reconciles any discrepancies and re-publishes live data.

How do trade-account customers see their negotiated pricing and credit limits at checkout?

K8 holds customer-specific pricing, volume breaks and credit limits. The integration publishes these to ecommerce trade portals when the customer logs in. Checkout applies the customer's rules (discounts, payment terms, credit limit) so they see the prices they negotiated and orders are not rejected on credit grounds.

How do web orders get into K8 and what happens if the customer is missing or the address is wrong?

iWeb captures ecommerce orders and maps them into K8 as sales orders. The integration validates customer records, standardises addresses and checks credit limits before handing the order to K8. If a customer is missing or credit is exceeded, the order is flagged for manual review and the customer is notified of the issue.

Can we capture orders from multiple storefronts and marketplaces into a single K8 instance?

Yes. iWeb builds connectors from each storefront, marketplace and trade portal to feed orders into K8. Each order is tagged with its source channel so that K8 can route it correctly for fulfillment and so that despatch confirmations go back to the right place.

How do returns and credits flow back from ecommerce to K8?

When a customer initiates a return through ecommerce, the integration creates a returns authorisation in K8. Once the item is received and inspected at the warehouse, K8 generates a credit note and adjusts stock. The customer's account balance and refund are updated so the return is complete.

What happens if a pricing change or credit-limit update is made in K8? How quickly does it reach ecommerce?

iWeb schedules regular price and customer-data refreshes from K8 to ecommerce, typically multiple times per day. For urgent changes (e.g. credit suspension), the integration can be triggered on-demand. During peak trading, iWeb monitors the sync lag so that pricing mismatches or credit blocks do not surprise customers.

Who owns the reconciliation between K8 and ecommerce if stock numbers disagree?

K8 is the system of record for stock. iWeb instruments the integration to flag discrepancies (stock received in K8 but not shown as available online, or vice versa). Warehouse and ecommerce operations teams investigate the gap, and iWeb updates the allocation rules if needed.

Can we run multiple ecommerce platforms or brands against the same K8 instance?

Yes. iWeb designs a multi-channel integration so that multiple storefronts pull stock and pricing from K8 and push orders back to K8. Each channel can have separate stock allocation, pricing rules and customer bases. K8 tracks orders by channel source.

How do we handle stock transfers between branches? Does this affect ecommerce availability?

K8 records branch-to-branch stock movements. iWeb's allocation model accounts for branch inventory when calculating ecommerce available-to-sell. If a branch transfer depletes a location, ecommerce available stock reflects that change in the next sync cycle.

What if a customer tries to place an order but their credit limit is exceeded? What do they see?

iWeb builds the integration so that ecommerce checks the customer's K8 credit limit at checkout. If the order would exceed the limit, checkout is blocked and the customer is notified of the reason. The order is not created until the customer pays or the credit limit is increased in K8.

How does the integration handle VAT, trade discounts and promotional pricing?

K8 holds base pricing, customer-specific discounts, volume breaks, promotions and VAT rules. The integration publishes these to ecommerce so that customers see correct net prices, tax and any applicable discounts. VAT is calculated by ecommerce at checkout and reconciled in K8 invoices.

How do we know if an order was successfully captured in K8 or if it's stuck somewhere?

iWeb instruments the integration to log every order from ecommerce, track its ingestion into K8 and confirm that K8 has assigned an order number and reserved stock. If an order fails, the integration alerts operations and the customer is notified so that manual follow-up can happen quickly.

Can the integration handle drop-ship orders or orders fulfilled from specific branch locations?

Yes. iWeb can design the integration to tag orders with a preferred fulfillment location (branch, warehouse or drop-ship supplier). K8 uses these tags to route orders to the correct location and to reserve stock from that location only.

What monitoring and alerting do we have during launch and beyond?

iWeb sets up dashboards and alerts for stock sync latency, order ingest lag, pricing mismatches, failed customer-account syncs and exception queues. During launch, these are reviewed daily. Post-launch, thresholds are adjusted based on trading patterns and alerts are routed to the teams responsible for each flow.

14b · Same category

Other erp · finance integrations.

Adjacent integrations in the same category. Same shape of work, different vendor.

ERP · finance
Next step

Have a Kerridge K8 integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →