WordPress / WooCommerce Developer — Fix Broken B2B Staging Migration & Finalise Elementor Rebuild

We have a complex B2B WooCommerce store mid-way through a front-end redesign. A recent developer's changes broke the staging environment, and we need an experienced WooCommerce developer to diagnose, clean up and correctly finish the work for go-live. This is urgent — we're aiming to have it back on track within 1–2 days. WHAT WENT WRONG - The staging site is a copy of live, deployed via a GitLab repo with CI/CD (rsync-based; dev and main branches, main protected). - The previous developer worked directly in WP admin instead of committing through Git, and upgraded WooCommerce (and WooCommerce Subscriptions). - That upgrade appears to have broken order-to-customer associations — most likely because HPOS was enabled — and disabled an email-suppression plugin, so test emails reached real customers. - Nothing was tracked in Git, so there is no clean history to review or roll back. CORE STACK - WordPress + WooCommerce (B2B), Woodmart theme + custom child theme (heavy custom PHP in the child theme's functions.php) - Elementor (the redesign layer) - WooCommerce Subscriptions - A custom ERP-integration plugin tying WooCommerce to a back-office ERP (pricing, stock, accounts, orders, invoices) — largely dependent on WooCommerce's legacy order storage, hence the HPOS sensitivity - Custom DB tables, custom user fields (account code, credit status/terms, freight entitlement, assigned locations) and custom product meta - GitLab + CI/CD (rsync deploy; dev to staging, main to live) CUSTOM B2B COMPONENTS TO PRESERVE - Account-based pricing pulled from a custom table, keyed to each logged-in customer's account code; pricing hidden entirely from guests - Conditional payment gateways by customer credit status/terms and shipping method (e.g. some orders cannot use credit card until a freight quote is generated); on-account rules with credit limits; card / bank transfer / on-account options - Multi-warehouse stock with primary/secondary locations per customer; "traffic-light" stock display (in/low/out thresholds, not exact quantities); regional aggregation ("nearby" availability) when assigned warehouses are short - A dynamic surcharge line item auto-added to qualifying carts as a percentage of eligible items, created as a real product so it syncs to the ERP - Custom shipping logic driven by product flags (special delivery handling), recorded against order line items; free-freight entitlement per customer (on-account only); a "collect" option that auto-fills the delivery address from the assigned branch - Parent/child account structure with account switching (head-office users managing sub-accounts) - Custom My Account area pulling live order history and invoices from the ERP via API; plus quick order pad, "recently purchased," and account-management screens - Grouped-product display logic on category pages - Branch order-notification emails on order placement - Downloadable product documents (spec/safety sheets) rendered from custom product meta IMPORTANT ARCHITECTURE NOTES - The Elementor design lives in the database, and the CI/CD pipeline only rsyncs files, not the DB — so the design and the data migration are handled separately at go-live, not via a Git deploy. - Several ERP-driven features (invoices, past orders, some pricing/stock) only return data on the live domain (the API is domain-bound), so they cannot be fully verified on staging. SCOPE OF WORK - Diagnose staging — HPOS status, WooCommerce version, and whether order/customer data is recoverable or needs a re-clone. - Restore the commerce layer — correct WooCommerce version, HPOS off, order data intact. - Re-apply the Elementor design correctly, committed through Git on dev, without disturbing the custom plugin or child-theme functionality. - Test the custom B2B functionality above (noting the live-domain-only caveat). - Prepare a clean, traceable handover for the final data migration and go-live. MUST-HAVE SKILLS - Strong WooCommerce, including HPOS / order storage, version management and B2B setups - Disciplined Git + GitLab CI/CD workflow (feature branches, merge requests) - Elementor + Woodmart/child-theme development - Confident debugging custom plugins, WooCommerce hooks and ERP integrations - Careful and communicative under a tight deadline TIMEFRAME: Urgent — start today or tomorrow, complete within 1–2 days. TO APPLY, PLEASE TELL US: - Your experience fixing broken WooCommerce order data / HPOS issues - How you would approach diagnosing this - Your availability over the next 48 hours