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

Options ERP Integration for B2B eCommerce

Ten million rows synced nightly at 100% success. This is the integration I point at when someone asks what good looks like.

Impact Office Supplies runs on Options ERP, and their B2B and B2C platforms run on an integration I 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 I solve.

Talk to me about Options ERP
Works with Shopify Adobe Commerce WordPress Laravel & custom builds

Proven in production

Very few developers have shipped Options ERP once, let alone three times. I 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 I build with Options ERP

The Options ERP integration work I most often take on. If yours sounds like one of these, we should talk.

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

I built this integration and I still maintain it. That is the arrangement I offer generally: the person who designed the failure modes is the person you call when something changes, years later.

How it works

A Options ERP integration built to last

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

01

Scope & map

We map exactly what needs to move between Options ERP and your store: orders, stock, pricing, customers, and where the awkward edge cases hide.

02

Build for redundancy

I build the integration around the failure modes: retries with backoff, idempotent writes, and reconciliation, so it holds up when the API has a bad day.

03

Test & reconcile

Tested against real data in a safe environment, with reconciliation reporting that proves Options ERP and your store actually agree before go-live.

04

Monitor & maintain

Monitoring and alerting from launch, so failures surface immediately, and the same developer who built it is the one who keeps it running.

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 typical agency

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".

Working with me

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.

FAQ

Common Options ERP Integration Questions

The questions I get asked most often about integrating Options ERP.

Can Options ERP integrate with an eCommerce website?

Yes, and I 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.

How do you sync ten million rows without it taking all night?

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.

Can Options drive customer-specific contract pricing on a B2B store?

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.

We run a different ERP. Can you still help?

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. I 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 me what you run.

Talk to me about your Options ERP integration

For over 15 years I've helped Australian enterprise, government, and not-for-profit organisations ship websites that are fast, secure, and accessible. Get in touch to discuss your project today.