Jonathan Bird Web Design & Development
  1. Integrations
  2. Options ERP Integration
OE ERP & Accounting

Options ERP Integration for B2B eCommerce

A production Options ERP connection synchronising around ten million rows nightly with documented 100% success, supported by batching, idempotency, and reconciliation.

Impact Office Supplies runs on Options ERP, and their B2B and B2C platforms run on an integration we built and still maintain. Every night it synchronises around ten million rows: products, customer-specific contract pricing, stock, and account hierarchies. It has run at 100% success because it was designed around what happens when things go wrong, not around what happens when they go right. If you are running Options and your website does not really know what your ERP knows, this is exactly the problem we solve.

Discuss Options ERP integration
Works with Shopify Adobe Commerce WordPress Laravel & custom builds

Proven in production

Very few developers have shipped Options ERP once, let alone three times. We built and still maintain the Options integrations behind FurnX, Impact Office Supplies, and Blue Ink Office Supplies, including a nightly sync of around ten million rows at 100% success.

Capabilities

What we build with Options ERP

The Options ERP integration work our senior team most often takes on.

Nightly Catalogue & Pricing Sync

Products, categories, stock, and customer-specific contract pricing pulled from Options into the storefront every night. At Impact that is roughly ten million rows, which is not a number you reach by looping over records one at a time.

Contract Pricing & Account Hierarchies

B2B customers do not see a price, they see their price. Contract pricing, quantity breaks, and parent and child account structures come from Options so that each logged-in trade customer sees exactly what has been negotiated for them.

Order Flow

Orders placed on the website land in Options ready to be picked, packed, and invoiced, without anybody rekeying them. The whole point of the integration is that the warehouse never has to care that the order came from a website.

Reconciliation & 100% Success

A sync of that size does not hit 100% by being lucky. It hits it because every batch is checked, every failure is retried, and reconciliation confirms the ERP and the storefront agree before anybody wakes up.

Long-term Ownership

We built this integration and still maintain it. That is the model we offer generally: our senior team retains the failure-mode and data-flow context, so later changes do not start from scratch.

How it works

An Options ERP integration built to last

The same approach behind every integration we deliver, from the first conversation to the years of maintenance that follow.

01

Scope & map

We define the data, events, responsibilities, source of truth, and failure cases across Options ERP and the systems around it.

02

Build for failure

We design around real failure modes with appropriate retries, idempotent writes, validation, and reconciliation so a temporary outage does not become silent data loss.

03

Test & reconcile

We test representative data in a safe environment, verify each data path, and reconcile the expected outcomes before go-live.

04

Monitor & maintain

Monitoring and alerting start at launch. Our senior team keeps the project context and remains responsible for changes, incidents, and long-term operation.

Straight advice

The simplest reliable integration usually wins.

The right design depends on volume, timing, ownership and what must happen when either system is unavailable.

Not every sync needs to be real-time

Scheduled or event-driven updates can be safer, cheaper and easier to recover.

Choose a source of truth

Each field and business rule needs one accountable owner across the connected systems.

Design the failure path

Retries, logs, alerts and reconciliation are part of the integration—not optional support work.

The Difference

Ten million rows a night is a design decision, not a lucky break.

Nobody accidentally builds an ERP sync that runs at 100% success at this volume. It happens because idempotency, batching, retries, and reconciliation were part of the architecture on day one rather than patches applied after the first bad month.

A common shortcut

Integration as plumbing.

  • Sync loops over records one at a time, works fine on a test catalogue, and then takes eleven hours once it meets the real one.

  • A failed batch is a failed night. Somebody notices in the morning, or more likely a customer does.

  • Contract pricing is approximated, so some trade customers occasionally see the wrong price. Everybody agrees it is "mostly fine".

Our senior-team model

Integration as the specialism.

  • Batched and designed for volume from the start. Ten million rows nightly, finished before the business day begins.

  • Failures are retried and reconciled automatically, and alerted if they cannot be resolved. 100% success is the operating standard, not the aspiration.

  • Contract pricing and account hierarchies come straight from the ERP. A trade customer sees their negotiated price, every time.

“ Digital Bird has had a huge influence on our business providing many solutions besides just a fantastic reliable website. Jonathan is great to work with and has a solution to every challenge. Jonathan also has the ability to “dumb it down” and provide timely advice and assistance if something goes astray. With Jonathan we have in excess of 99% uptime on all three websites. ”

Jeff Ross · Director, Impact Office Supplies
Impact Office Supplies Logo
FAQ

Common Options ERP Integration Questions

Common questions our team is asked about integrating Options ERP.
Yes, and we have built exactly that. Impact Office Supplies runs both B2B and B2C platforms against Options, with products, stock, contract pricing, and account structures flowing out of the ERP and orders flowing back into it. The integration synchronises roughly ten million rows nightly and has run at 100% success.
By not treating it as ten million individual operations. The work is batched, parallelised where it is safe to be, and diffed so that unchanged rows are not needlessly rewritten. Just as importantly, it is idempotent, which means a batch that fails can simply be retried rather than putting the whole run into an uncertain state that a human has to untangle.
Yes, and this is usually the single most valuable part of the integration. B2B buyers expect to log in and see the pricing they negotiated, including quantity breaks and any parent or child account arrangements. That pricing lives in the ERP, so the storefront has to reflect it faithfully rather than approximate it. Getting this wrong is both a commercial problem and a trust problem.
Almost certainly. The skill here is integration engineering rather than any one vendor's API: designing the failure modes, the retries, the idempotency, and the reconciliation. We have shipped against NetSuite, MYOB, Xero, and Options, and the same approach applies to SAP, Cin7, Dynamics, Pronto, and Odoo. See the ERP integration page, or just tell us what you run.

Discuss your Options ERP integration

Led by more than 15 years of commercial experience, our senior team helps Australian organisations ship websites that are fast, secure, accessible and built for the long term.

Planning a project?

Get a quote
Get a quote