Adobe Commerce B2B, engineered for aerospace manufacturing.

What it doesCustom Magento payment method wired directly to BridgeComm with PCI-compliant tokenization. Pre-authorizes at checkout; final capture fires from the ERP after shipment.

Why from scratchThe third-party extension had no admin UI and tied capture to cart submission. The custom integration gives DMC a full payment lifecycle tied to fulfillment.

What it doesSecond payment processor for accounts that route through Cenpos. Sits alongside BridgeComm in checkout with the same admin and capture behavior.

Why from scratchNo existing Cenpos extension supports Net-terms gating, customer-group restrictions, or ERP capture flow. Built to the same pattern so both processors behave identically.

What it doesBidirectional sync with Infor Syteline via its IDO REST API: customers, addresses, payment terms, products, inventory, lead times, orders, and shipments. Writes due_date back per line item and triggers 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 for a generic middleware layer.

What it doesExtends the Syteline integration to check, create, and update Customer Document Profiles (Order Verification + Invoice routing) whenever a Magento account is created or updated.

Why from scratchDMC's accounting workflows require these profiles in Syteline before an order can ship. Manual creation was error-prone. The module makes it automatic and idempotent.

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

Why from scratchYears of inconsistent data entry caused silent matching failures and unroutable orders. The check API guarantees every Magento customer maps to its canonical Syteline ID.

What it doesCustom admin module with an editable Estimated Ship Date per order, calculated from the longest-lead-time line. Surfaces on confirmation emails, My Orders, order detail, and admin grids. Edits write back to Syteline as line-item due_date.

Why from scratchNative Magento has no concept of a customer-promised ship date driven by ERP lead times. The Order Manager is 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, holiday calendar, DMC-prefix 'Please Consult Factory' (LaceLok exception), cart-level cascade, PDP cache, and hardcoded-override field.

Why from scratchAerospace tooling lead times don't fit a generic 'X business days' formula. Every rule mirrors how DMC's order desk and certification process actually work, and a single change ripples across every touchpoint without breaking ERP sync.

What it doesPre-selects the first simple SKU on configurable PDPs, swapping in its 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. The module swaps product data without breaking schema.org, the Google Merchant feed, or reviews.

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

Why from scratchMost B2B sites push credit apps to a standalone page buyers never return from. Embedding the form in checkout keeps the order alive while DMC reviews. Built on Amasty Custom Forms with a checkout + business-rule layer.

What it doesEvery quote request, contact form, and B2B quote email auto-CCs the right National Account Executive by the buyer's shipping state (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. State-to-executive routing is a config layer sales ops can edit without a deploy.

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.