If you sell on Bol.com — the largest marketplace in the Netherlands and Belgium — and run ERPNext for the rest of your business, the gap between the two is where margin quietly leaks. Sellers copy Bol orders into Sales Orders by hand, re-key stock levels into two systems that drift apart within a day, forget to update prices when a competitor undercuts the buy-block, and reconcile Bol's commission and settlement statements against ERPNext bank entries in a spreadsheet at month-end. ERPNext core has no concept of the Bol Retailer API, no Bol offer object, and no settlement matching — so the "integration" ends up being a person. That person is a bottleneck and a source of oversell.

ECOSIRE builds a proper Frappe app (installed with bench get-app / bench install-app) that turns ERPNext into the system of record for your Bol.com operation. It authenticates to the Bol Retailer API v10 with your client-credentials (OAuth2, token cached and auto-refreshed), and models Bol concepts as first-class DocTypes: Bol Settings (single) for credentials and sync toggles, Bol Offer mapped to your ERPNext Item, Bol Order staged before it becomes a Sales Order, and Bol Settlement for reconciliation. Scheduler events (registered in hooks.py under scheduler_events) poll for new orders and settlements and run inventory/price pushes on the intervals you choose; queued background jobs (frappe.enqueue) keep the request-heavy calls off the web workers and respect Bol's rate limits with backoff.

Order flow is two-directional and idempotent. Inbound: new Bol orders are pulled, de-duplicated on the Bol order id, and created as ERPNext Sales Orders with the right customer, item mapping, VAT treatment and Bol commission captured as a line or ledger entry. hooks.py doc events (for example on_submit of Delivery Note) push shipment and Transport/carrier tracking back to Bol so the order is confirmed and the customer is notified through Bol. Outbound: a doc_events hook on Stock Ledger / Bin changes — or a scheduled reconcile job — publishes available quantity and price back to your Bol Offers, so ERPNext stock is the single source of truth and oversell stops. Every external call and payload is logged to a Bol Sync Log DocType for auditability, and failures raise ERPNext Notifications rather than failing silently. Whitelisted methods (@frappe.whitelist()) expose manual "sync now" actions, and client scripts add the buttons to the relevant forms. Access is governed by a dedicated role and Role Profile so warehouse, finance and admin users each see only what they should.

Because this is build-to-order, nothing ships until we agree on scope. It starts with a short scoping call to map your Bol account structure (single vs. FBB/LVB fulfilment, NL/BE VAT, carrier mix), your ERPNext item and warehouse layout, and your commission/settlement posting rules. We build against a staging copy of your site, run UAT with your real Bol test/sandbox and a sample of live SKUs, and only then cut over to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source of your version of the app, a git repository handover, install and configuration docs, a user guide plus a live training session, and a post-go-live support window — all built and supported by ECOSIRE on Frappe/ERPNext v15 and v16.