Adobe Commerce
B2B, engineered
for aerospace manufacturing.

What it doesA custom Magento payment method integrated directly with the BridgeComm gateway, using PCI-compliant tokenization at checkout. Pre-authorizes the full order at checkout; final capture fires from the ERP after the order ships.

Why from scratchWe replaced the third-party gateway extension with a custom direct-API integration, giving DMC a full admin UI and a payment lifecycle tied to fulfillment rather than cart submission.

What it doesA second payment processor wired into Magento for accounts that route through Cenpos rather than BridgeComm. Sits alongside the BridgeComm module in checkout.

Why from scratchNo existing Cenpos extension covered the B2B requirements: Net-terms gating, customer-group payment restrictions, ERP capture flow. Built to the same pattern so both behave consistently for the order desk.

What it doesBidirectional integration with Infor Syteline via its IDO REST API, customers, addresses, payment terms, products, inventory, lead times, orders, shipments. Writes order due_date back per line item; triggers final card capture post-shipment.

Why from scratchThe original spec called for Celigo iPaaS. DMC's flows (Document Profiles, A-account normalization, line-item due-date writeback, ERP-driven capture) are too tightly coupled to Syteline to live behind a generic abstraction.

What it doesExtends the Syteline integration with API calls that check, create, and update Customer Document Profiles (Order Verification + Invoice routing) every time a Magento account is created or updated.

Why from scratchDMC's accounting and order-verification workflows depend on these profiles existing in Syteline before an order can ship. Manual creation was error-prone; the module makes it automatic and idempotent.

What it doesA back-fill utility plus a runtime hook that normalizes Syteline A-prefixed account numbers across the whole customer base, converting short forms like A252 to the canonical A000252 everywhere.

Why from scratchYears of inconsistent data entry meant customer-to-ERP matching failed silently and orders couldn't route. The check API guarantees every Magento customer reconciles to the canonical Syteline ID.

What it doesA custom admin module exposing an editable Estimated Ship Date at the order level, calculated from the longest-lead-time line, surfaced on the confirmation email, My Orders grid, order view, admin grid, and detail. Edits write back to Syteline as the line-item due_date.

Why from scratchNative Magento has no concept of a customer-promised ship date driven by ERP lead times and editable by the order desk. The Order Manager became the single source of truth for the date DMC commits to.

What it doesThe rules engine behind every Est. Ship Date on the site: PDP, cart, checkout, quotes, emails, admin. Weekend skips, certification days, Safe-T-Cable +3, same-day +1, admin holiday calendar, DMC-prefix 'Please Consult Factory' (LaceLok exception), cart-level cascade, 1-hour PDP cache, hardcoded-override field.

Why from scratchAerospace tooling lead times don't fit a generic 'X business days' formula. Every rule came from how DMC's order desk and certification process actually work, and one change has to ripple across PDP, cart, checkout, quote, and admin without breaking ERP sync.

What it doesPre-selects the first simple SKU on configurable PDPs, swapping in its Name, Price, Tier Pricing, Military Part Number, Lead Time, descriptions, attachments, and reviews. Strips the * suffix from configurable SKUs in listings.

Why from scratchDefault Magento forces buyers to pick an option before seeing anything specific. Wrong UX for a catalog of military part numbers. Had to swap product data without breaking schema.org Product, the Google Merchant feed, or reviews. Nothing off-the-shelf did all three.

What it doesA checkout-embedded credit application. Qualified B2B buyers (US ship-to, logged in, above a configurable order threshold, no existing Net terms) get a popup collecting their D&B number, AP contact, and requested terms, notifying the team and confirming a 2-business-day review SLA.

Why from scratchMost B2B sites push credit apps to a standalone page buyers leave checkout to fill out, and never return. Embedding it (with admin-configurable minimums and qualification rules) keeps the order alive while DMC reviews. Extended Amasty Custom Forms with the checkout + business-rule layer.

What it doesEvery Request-a-Quote, Contact Form, and B2B quote email auto-CCs the right National Account Executive by the buyer's shipping state (e.g. Florida, Northeast & Canada, and the AL/AR/LA/MS/NC/SC/TN territory each route to a different NAE).

Why from scratchDMC's territory map doesn't fit a single recipient or a CRM round-robin. The module makes state-to-executive routing a config layer sales ops can edit without redeploying.

What it doesA small but pervasive utility every date-aware module (Lead Time, Order Manager, Quote dates) consults, reading an admin-configurable holiday list and rolling dates forward across weekends and US public holidays.

Why from scratchNative Magento ships no holiday-aware date utility, and three modules needed the same logic. Centralizing it means one holiday-calendar change updates every Est. Ship Date across the site.