Get on a call with us to see how we can help you
Get a QuoteRedefine×MAXIMUM · Custom Web Application · Enterprise Admin Portal
MAXIMUM Weather Instruments runs its business across an ERP, inventory, a headless ecommerce storefront, and marketplace channels. Redefine replaced the patchwork with MAXIMUM Admin, a single Next.js platform where one team manages product, inventory, content, orders and marketplace listings without leaving the screen.
Summary
MAXIMUM is a weather instruments manufacturer and retailer running ERP, inventory, a headless ecommerce storefront and marketplace channels for its business. Redefine built MAXIMUM Admin, a single enterprise platform on Next.js, React and TypeScript that unifies Microsoft Dynamics 365 Business Central inventory sync, storefront configuration and content, and Amazon/Wayfair marketplace field mapping, with role-based access, bulk import/export, and a Jest/RTL plus Playwright test suite covering the full ERP-to-storefront-to-marketplace flow. The result: one team manages product, inventory, content, orders and marketplace listings from a single hub instead of switching between four systems.
Note: the platform scope (4 systems unified, Business Central ERP, 2 marketplace channels, full tech stack) comes from the build. Performance percentages, dollar figures and testimonials on this page are illustrative samples pending verification.
The challenge
MAXIMUM had already partnered with Redefine on a headless storefront build on Shopify, but the storefront was only one piece of the business. Behind it sat Microsoft Dynamics 365 Business Central for ERP, inventory managed outside a single admin view, marketplace listings on Amazon and Wayfair, and the content and promotions tooling needed to keep it all current.
None of those systems talked to each other natively. Product data lived in a master feed, then an active feed, then per-store listings, then marketplace exports, each a manual hop with its own chance to drift out of sync. Updating a price or a stock count meant touching four places, not one.
That fragmentation is what made this a platform problem, not a feature request: the fix had to be one accountable system spanning ERP, inventory, storefront and marketplace, not another point tool bolted onto the pile.
The approach
Redefine ran admin experience and platform engineering as one workstream, designing the interface and integrations against the same data model from day one.
Merchandising, warehouse and support teams previously worked in different tools. Redefine designed the admin UX around their actual workflows, not the underlying systems.
Underneath the UI, the platform owns the data contract between Business Central, the headless storefront and the marketplace channels, so the interface is only ever showing one true state.
The work
System architecture (documented scope; flows inferred)
What we engineered
Migration & rollout
Redefine rolled out MAXIMUM Admin module by module against the live Business Central instance, product feeds and inventory sync first, then storefront configuration and the content builder, then marketplace field mapping, then orders, returns, customers and promotions. Each module shipped behind role-based permissions so teams adopted their slice without a single big-bang cutover, while Jest/RTL unit tests and a Playwright E2E suite validated every ERP-to-storefront-to-marketplace flow before release.
ERP deep-dive
Five Business Central–facing modules, each scoped behind role-based access so the warehouse, merchandising and finance teams only see what's theirs.
| Entity | Source of record | Sync direction | Destination |
|---|---|---|---|
| Stock levels | Business Central | BC → Admin | Storefront, Amazon, Wayfair |
| Product & pricing | Business Central | BC → Admin | Master & active feeds |
| Orders & returns | MAXIMUM Admin | Admin → BC | Business Central |
| Customers & companies | MAXIMUM Admin | Admin ↔ BC | Business Central, storefront |
The platform reconciles inventory and pricing changes against Business Central on a scheduled cycle with retry handling, so a dropped sync doesn't silently leave a store overselling. (Cadence and retry behavior are inferred, confirm against the implementation before publishing.)
Marketplaces
Marketplace fan-out (documented channels; flow inferred)
Mapped fields
Marketplace orders route back through MAXIMUM Admin so fulfillment, whether shipped from MAXIMUM's own warehouse or via a marketplace program, is visible in the same orders screen as direct and storefront orders.
Engineering & quality
A feature isn't done when the UI works. It's done when the ERP-to-storefront-to-marketplace flow it depends on is covered by an automated test. Jest and React Testing Library cover components and logic; Playwright drives full end-to-end flows across feeds, stores and marketplaces; Sentry watches production. Azure DevOps runs the suite on every change.
The results
The brief documents the platform scope (4 systems unified, 2 marketplace channels live, full test automation). The performance figures below are reasoned estimates for the team to confirm against real usage data.
The build documents the systems-unified count, marketplace channels, tech stack, and test suite composition. Stock-accuracy, time-to-publish and order-handling figures are illustrative samples sized to a business of MAXIMUM's scale. Replace them with verified analytics before this page goes live.
“Sample testimonial: replace with a real, approved quote. We used to log into four different systems to get one product live everywhere; now it's one screen.”
“Sample testimonial: replace with a real, approved quote. Redefine already knew our storefront from the Shopify build; bringing them in for the admin layer meant zero ramp-up time.”
Start here
We build the admin layer that connects your ERP, inventory, storefront and marketplaces into one accountable system: fixed price, one team, full code ownership.
No commitment. A scoping call costs nothing and tells you exactly what unifying your systems would look like.