Stock and prices in one place
A stock change in the warehouse or at the supplier updates the offer in the store and on marketplaces without manual work.
IT services · Canpol Bis
System integrations and APIs
When orders, stock levels and invoices live in different systems, someone has to join them by hand. Integrations make data flow on its own and give you a single source of truth.
In short
System integration connects company applications (store, ERP, CRM, accounting, couriers) through APIs and webhooks so that data flows automatically. Canpol Bis designs data mapping, error handling and monitoring for such connections.
How an integration works – diagram
Systems do not talk to each other directly. An integration layer sits between them: it receives data, validates it, maps it and passes it on.
Data sources
- WooCommerce store
- Warehouse / wholesaler
- ERP and accounting
Integration layer
API · webhooks · job queue
- validation
- field mapping
- retries
- logs and alerts
Data recipients
- Couriers and carriers
- Marketplaces
- CRM and newsletter
The path of one operation
- 1Evente.g. a new order or stock change
- 2Verificationrequest signature and data validation
- 3Mappingfields, units, VAT rates
- 4Queueretries and API limits
- 5Save and logstatus and alert on error
Example scenarios
Order → shipment
Once an order is paid, a shipment, label and tracking number are created and sent back to the customer.
Sales documents
Invoices and credit notes go to the accounting system, and their status returns to the order.
Product data
Descriptions, images and attributes from a supplier file are mapped to the product page and updated on a schedule.
Secure exchange
Key or OAuth 2.0 authentication, webhook signature verification and restricted permissions.
What the service includes
Store and warehouse
Synchronising stock and prices between the store and the warehouse system or wholesaler.
ERP and accounting
Passing orders and sales documents to the accounting system or ERP.
Couriers and carriers
Creating shipments, labels and tracking numbers directly from the order.
Marketplaces and comparison sites
Exporting offers and importing orders from sales platforms.
CRM and marketing
Passing leads and customers to the CRM and newsletter tools.
Monitoring and logs
Integration error reports and notifications when something stops working.
Technical approach
Interfaces
Integrations via REST, SOAP and GraphQL, as well as CSV/XML/JSON file exchange, with OAuth 2.0, API keys or tokens for authentication.
Mapping and validation
Documented field mapping between systems, input validation and normalisation (units, VAT rates, country codes).
Reliability
Idempotent operations, job queues, retries with exponential backoff and respect for rate limits.
Webhooks and events
Near real-time event handling with request-signature verification, backed by periodic synchronisation.
Monitoring
Operation logs, discrepancy reports, failure alerts and a view of synchronisation status.
Documentation
Data-flow diagram, field descriptions and contingency procedures handed over to your team.
Technologies and standards
- REST · SOAP · GraphQL
- OAuth 2.0 / API keys
- Webhooks
- CSV · XML · JSON
- n8n / custom plugins
- Job queues
- Monitoring and logs
Who is it for?
This service is for companies that use several tools and lose time moving data by hand, or make mistakes when retyping orders and stock levels.
How we work
- 1
Discovery and analysis
We learn about your business, goals and current tools, then agree on scope and priorities.
- 2
Proposal and quote
We present a plan, timeline and quote before any work begins.
- 3
Implementation and testing
We deliver in stages, show progress and test the solution on real devices.
- 4
Launch and support
We deploy to production, train your team and stay available after go-live.
FAQ
Frequently asked questions
Can every system be integrated?
Most modern systems have an API. Where there is none, a file export or another intermediary can often be used. We check the options during analysis.
How often is data synchronised?
According to need: near real time via webhooks, or periodically, for example every few minutes or once a day.
What happens when an integration breaks?
We deploy monitoring and notifications, and failed operations are retried or flagged for manual handling.
Do integrations require changes in my systems?
Usually not. We use the interfaces and documentation the vendors provide.
How do you make sure data is not duplicated?
Operations are designed to be idempotent: each record has an external key, and resending updates the existing entry instead of creating another.
What about external API rate limits?
We respect vendor limits: requests are queued, grouped into batches and retried with a delay so the permitted rate is not exceeded.
Let’s talk about your project
Tell us what you need. We will come back with a proposal and a quote.
Content last updated: 15 October 2026