Selected work

A small set of engagements where the architecture had to hold.

Client names are withheld under NDA. The systems are real. Each case below is condensed to the architectural problem, the approach, and the outcome.

Sector
Regulated e-commerce
Engagement
Architecture + delivery
Stack
WooCommerce, NetSuite, PHP, REST
Duration
Ongoing

WooCommerce ↔ NetSuite real-time integration

The problem

A specialty pharmacy needed its WooCommerce storefront to behave as a sales channel for a NetSuite ERP system that owned inventory, pricing, and order fulfilment. The previous setup had drift, duplicate customer records, and stock numbers that lagged hours behind reality.

The architecture

We designed a one-directional sync model — NetSuite as the master, WooCommerce as the channel — using flat Inventory Items keyed by SKU rather than NetSuite's Matrix products. Field mapping was reduced to what the storefront actually needs (description, attributes, price, stock). Customer and order sync run through queued jobs with idempotent handlers and retry semantics.

~1s Stock update latency
0 Duplicate customers since cutover
5 Sync surfaces unified
Sector
High-volume retail
Engagement
Performance & DB architecture
Stack
WooCommerce, MySQL, object caching
Duration
3 months

Scalable database architecture for high-volume WooCommerce

The problem

The site's admin dashboard was effectively unusable during business hours. Order list queries timed out, product save operations took 20+ seconds, and the database server was permanently CPU-bound. Standard caching plugins had been layered on without addressing the underlying query patterns.

The architecture

We audited the live query plans, restructured the most expensive joins, added targeted indexes on lookup paths the team didn't realize were being hit, and moved hot metadata to a dedicated table layout. Object caching was reconfigured to actually cache the right keys, and a background worker was introduced for the operations that didn't need to be synchronous.

12× Faster admin queries
60% Lower DB CPU at peak
0 Downtime during migration
Sector
Regulated payments
Engagement
Payment architecture & gateway
Stack
CyberSource, SuiteScript, 3DS2
Duration
2 months

High-compliance payment architecture with CyberSource & 3DS2

The problem

Two order channels — prescription and over-the-counter — needed to share a payment infrastructure but had completely different risk and AVS requirements. The existing setup applied the same checks to both, causing legitimate prescription orders to be flagged as “bad CC” even after CyberSource had successfully settled them.

The architecture

We separated the two flows in the gateway adapter layer, conditionally adjusting AVS behaviour based on the commerce indicator. 3DS2 authentication was wired in for the consumer-facing flow, and tokenized capture/void/refund operations were standardized so reconciliation could trust the order state. The fix was applied without touching the OTC checkout path.

100% RX orders cleared correctly
0 Regression on OTC flow
3DS2 Compliance verified
Your project

Looking for the same kind of work on your system?

Most engagements start with a single email describing the problem. We'll read it, respond, and tell you honestly whether we're the right fit.

Get in touch →