Domain mismatch
Machine-based purchasing, customer portal stores and approval chains were not ordinary retail-commerce requirements.
← All case studies
B2B commerce modernization
From Magento constraints to a purpose-built Laravel platform.
DigiLynx re-engineered WolfMach’s commerce and Tool Management System as a custom Laravel application—preserving business-critical workflows while connecting customer pricing, inventory, accounts and orders with NetSuite.
Legacy foundationMagento
Storefront + custom TMS extensions
Rigid workflowsScript-heavy integrationCostly changes
Re-engineered
Purpose-built platformLaravel
Commerce + TMS + business workflows
Custom domain modelModern applicationOperational control
System of recordNetSuite
Customers · pricing · inventory · orders
6 milestonesStructured redevelopment and verification
One portal per customerCustomer-specific B2B store experience
Real-time pricingNetSuite levels, discounts and formulas
Connected operationsAccounts, inventory, addresses and orders
The challenge
This was never a standard online store.
WolfMach’s platform combined conventional eCommerce with a specialized Tool Management System (TMS). Every B2B customer operated inside its own portal store, organized products around the machines it used, created subaccounts, controlled order approvals and received pricing determined by NetSuite.
Over time, implementing these domain-specific workflows inside Magento created friction. Changes depended on inherited scripts and platform conventions that did not naturally match the business. DigiLynx therefore moved beyond a theme change or version upgrade and rebuilt the application around WolfMach’s actual operating model.
Complex pricing
Customer groups, NetSuite price levels, custom prices, discounts and measurement formulas all influenced the final price.
Integration dependency
Customers, addresses, inventory and orders moved between the website and NetSuite with different directional rules.
Operational drag
Product organization, machine associations and everyday ordering required too many manual steps.
The solution
A commerce application designed around the business.
Built on a current Laravel release, the custom architecture brings storefront, customer portals, TMS workflows, administration and NetSuite integration into one maintainable application.
Customer experienceCatalog · Product details · Favorites · Cart · Checkout
B2B applicationAccounts · Subaccounts · Machines · Approvals · Reporting
Commerce operationsOrders · Invoices · Shipments · Credit memos · Transactions
NetSuite integrationCustomers · Prices · Discounts · Inventory · Addresses · Orders
The domain model follows WolfMach
Stores, machines, product associations and approval rules are application concepts—not workarounds inside a generic storefront.
Business logic lives in clear services
Pricing, synchronization, notifications and ordering workflows can evolve without depending on scattered Magento customization.
NetSuite remains the operational authority
The web application delivers the experience while NetSuite governs customer pricing, inventory and downstream order processing.
Core B2B experience
The Tool Management System, rebuilt for faster ordering.
Each customer receives a dedicated portal store with the people, machines, products and controls relevant to that account.
Customer portal
Each B2B customer is assigned one portal store managed by its authorized users.
Machine setup
Managers create machines or equipment groups and associate the appropriate products.
Easy Order
Customers browse by machine, add required products and see the same product order configured by the manager.
Approval workflow
Subaccounts can prepare orders that require approval from the main account before submission.
Products are organized beneath each machine, and the saved sequence carries into the Easy Order view.
Multiple products can be connected to a machine in one operation instead of being added individually.
Relevant categories such as sawing and turning replace inherited attributes that did not help users find products.
Non-TMS customers can keep frequently used products until they choose to remove them—even after purchase.
Account history makes previous orders visible and allows customers to place recurring requirements again.
Sales reporting can be filtered by machine, product and customer store to support operational analysis.
NetSuite integration
Pricing and inventory reflect the customer—not a generic catalog.
The integration distinguishes what NetSuite owns, what Laravel owns and which information must move in both directions.
NetSuite → Laravel
Operational source data
- Customer records and NetSuite identifiers
- Price levels and customer groups
- Customer-specific product pricing
- Discount information
- Inventory availability
Laravel pricing engineBase or customer price+Measurement formula+Applicable discount= Customer price
Laravel → NetSuite
Customer and order updates
- Confirmed eCommerce orders
- Customer address changes
- Relevant customer details
- Subaccount contact changes or alerts
- Order data for downstream processing
Customer-specific pricing
When a customer has a NetSuite price record, the application applies the relevant level, group or custom price.
Formula pricing
Configurable products can calculate price from measurements—for example, price per metre multiplied by the selected length.
Fallback pricing
If no customer-specific entry exists in NetSuite, the application uses the standard price maintained in the commerce platform.
Cart repricing after login
Items added before authentication are checked again after login and updated to the identified customer’s correct price.
Complete platform scope
Commerce, accounts and operations in one application.
The redevelopment covered the customer-facing experience and the administrative functions required to operate it.
Discovery and catalog
Category menus, breadcrumbs, attribute filtering, product grids, product details, related products and related content.
B2B account management
Account dashboard, subaccounts, approval queues, reminder schedules, orders, invoices and reporting.
Catalog control
SKU, name and price sorting; machine and category filters; formulas; upsells and cross-sells.
Commerce administration
Orders, invoices, shipments, credit memos, transactions and customer reporting.
Stock and account alerts
Scheduled stock-level emails by product or machine, subaccount creation alerts and account-change notifications.
Business checkout methods
Paymark and purchase-order methods support the purchasing requirements of B2B customers.
Migration approach
Rebuild the platform without losing the business rules.
The work was divided into six milestones so the team could reconstruct the experience, validate commerce behavior, add TMS capabilities, integrate NetSuite and complete system-wide testing in controlled stages.
- 01Experience foundation
Frontend, catalog, authentication, account area and initial administration.
- 02Commerce operations
Orders, invoices, shipments, catalog management, customers and reports.
- 03Notifications and reporting
Subaccounts, stock reminders, inventory labels, approvals and machine associations.
- 04Core TMS
Customer stores, machines, product assignment, Easy Order and approval workflows.
- 05NetSuite integration
Customers, pricing, formulas, discounts, inventory, addresses and orders.
- 06Testing and stabilization
Payments, purchase orders, debugging and complete workflow verification.
The achieved outcome
A modern B2B commerce foundation that fits how WolfMach sells.
The application models stores, machines, approvals and repeat ordering directly.
NetSuite pricing, discounts and formulas are applied for the identified account.
Bulk association, drag-and-drop ordering and relevant filters reduce operational friction.
Business-critical behavior was reconstructed in stages and verified before completion.