A publisher's store, stewarded for the long run.

What it doesA structured QA pass across the live store's core integrations: tax, shipping, payment processing, and ERP synchronization, each reviewed end to end with sample orders, error logging, and a findings report with severity and recommendations.

Why from scratchThe store had accumulated operational gaps across its integrations. A disciplined audit established a reliable baseline before any new feature work.

What it doesValidation and tuning of the Avalara AvaTax integration: tax-code mapping, jurisdiction assignment, address validation, and the taxability of shipping and discounts, verified against sample transactions.

Why from scratchTax has to be right in every jurisdiction the publisher ships to. Auditing the configuration removed the risk of mis-charged or non-compliant tax.

What it doesA full review of the ShipperHQ configuration: carrier settings, zone and rate logic, free-shipping thresholds, and domestic and expedited scenarios, validated through complete checkout flows.

Why from scratchShipping rates that misfire at checkout cost orders. Scenario testing confirmed customers see accurate methods and rates every time.

What it doesValidation of the Greytrix GUMU connector that synchronizes customer and order data between Magento and Sage Intacct, covering successful transfers, error handling, and sync timing.

Why from scratchThe ERP is the system of record. Confirming the connector behaves under failure as well as success keeps the store and the books in agreement.

What it doesAn extension of the Magento Payfabric payment module to record full transaction detail and surface it through the Order API, so payments authorized at checkout carry through to capture and reconciliation in Sage Intacct.

Why from scratchThe default integration did not expose transaction detail to downstream systems. Extending it lets the ERP capture and reconcile payments instead of staff doing it manually.

What it doesA registration flow that distinguishes company accounts from regular customers, capturing school division and school or church name, with an automatic admin notification when a company account is created.

Why from scratchThe publisher's customers are largely churches and schools. Capturing organization detail at signup routes those accounts correctly from the first order.

What it doesA CSR-managed customer-type attribute, editable from the admin and hidden from shoppers, exposed through the Customer API so downstream systems share a consistent classification.

Why from scratchService reps need to categorize accounts in ways customers never see. A dedicated attribute keeps that classification consistent across the store and the ERP.

What it doesCustom order attributes for hold flag, hold reason, and hold assignment, plus a rush-order flag, surfaced on the admin order view and create pages and passed through the Order API.

Why from scratchHolds and rush requests were tracked off-system. Bringing them into the order record gives CSRs and the ERP one shared, filterable source of truth.

What it doesA per-line-item status (such as released, active, or do not reorder) that customer-service reps can set directly in the order view while creating or editing an order.

Why from scratchOrder decisions often happen line by line. Item-level status lets reps manage individual products without splitting or re-keying the order.

What it doesConfiguration of Avalara's exemption-certificate management so eligible customers can upload valid tax-exemption certificates against their account.

Why from scratchChurches and nonprofits frequently buy tax-exempt. Capturing certificates in the platform makes exemption a clean, auditable self-service step.

What it doesExtensions to the Magento Order and Customer REST APIs to carry the custom fields added across the engagement, so the ERP and connected systems receive the additional account and order data they rely on.

Why from scratchNew fields are only useful if downstream systems can read them. Extending the APIs keeps the ERP and integrations in step with the storefront.

What it doesOngoing maintenance of the live store, including platform and PHP version upgrades that move it onto current, vendor-supported releases as part of a continuing support partnership.

Why from scratchCommerce platforms drift out of support over time. Continuous upkeep keeps the store on modern, maintained software rather than letting it age.