Nemat Enterprises -
B2B Commerce Engine.
Four manufacturers. Thirteen business scenarios. A pricing engine that the previous platform got wrong silently - and 150+ monthly B2B orders that couldn't afford the errors.
Nemat Enterprises distributes fragrances at B2B scale - across four manufacturing companies, multiple product categories, and hundreds of wholesale buyers.
Their catalogue spans Attars, Roll Ons, Non-Alcoholic Sprays, Agarbatti, and bulk compounds - each with different pricing logic, different discount structures, and different minimum order requirements depending on the buyer's volume.
Products are sourced from four distinct manufacturing entities. When an order is placed, the system needs to determine - automatically - which manufacturer issues the sales order, and whether it goes direct or gets consolidated through Aromas Sales.
The previous system had hardcoded Agarbatti at a flat 18% discount regardless of order value. Discount slabs were shared across all categories. Sales order routing logic was silently producing wrong outputs across multiple order scenarios. None of this was visible until orders were placed and discrepancies appeared.
Three distinct systems. All producing wrong outputs.
Hardcoded discounts ignoring order value
Agarbatti was hardcoded at 18% regardless of order size. All categories shared a single discount slab. A buyer ordering ₹5,00,000 of Attar got the same discount as someone ordering ₹50,000 - because the system had no way to separate category-level logic.
Wrong manufacturer routing on live orders
The SO routing engine was producing incorrect outputs across multiple order scenarios - sending orders to Aromas Sales when they should have gone direct to the manufacturer, and vice versa. The logic evaluated all categories together instead of independently per category per manufacturer.
Product-level minimums blocking B2B buying behaviour
Minimum quantity requirements were enforced per product. A wholesale buyer who wanted to mix 20 pieces of Product A and 60 pieces of Product B from the same series could not - even though the combined 80 pieces met the series minimum. The system forced them to hit the minimum on each product individually.
Three separate engines. Each rebuilt from the correct business logic up.
Discount slabs are created independently and assigned to specific categories. A slab assigned to Attar only applies to Attar products. Agarbatti has its own slab with its own tier logic - no more hardcoding.
One slab can be assigned to multiple categories simultaneously. When it is, those categories are evaluated together in a single cart card. When categories have separate slabs, they get separate cards with separate discount calculations.
The cart now shows buyers exactly how their order value maps to their discount tier - transparently, per category group.
Each category is evaluated independently per manufacturer. Agarbatti is never combined with non-Agarbatti totals - even from the same manufacturer.
If a manufacturer's non-Agarbatti total reaches ₹50,000, they issue their own sales order directly. Below that threshold, those products consolidate under Aromas Sales. Agarbatti follows the same independent threshold check.
13 distinct business scenarios were mapped, tested, and verified - covering every combination of manufacturer totals, category splits, and threshold crossings.
Minimum quantity requirements now operate at the series level, not the product level. A buyer can mix any combination of products from a series - as long as the combined quantity meets the series minimum.
A sticky bottom bar accumulates selected products as they browse. The Add to Cart button activates only once the series quantity threshold is met. Until then, it shows exactly how many more pieces are needed.
The PDF generation for sales orders was also refactored - decoupled from order placement entirely, with idempotent SO number generation that creates each number exactly once regardless of how many times the document is printed.
The kind of work that only shows up in the business logic.
The discount slab engine was designed with a safety net built in - when an admin deletes a pricing tier, the system automatically removes any orphaned extra charges from all affected products. No manual cleanup required.
The SO routing system processes Agarbatti and non-Agarbatti as completely independent evaluation chains - even when they come from the same manufacturer. The threshold check runs separately for each, producing the correct SO split in every combination.
This is the class of problem most agencies either refuse to quote or misunderstand at the architecture stage. We mapped 13 scenarios before writing a line of production code.
Pricing that's correct. Orders that route right. Every time.
The platform now handles the full complexity of Nemat's B2B operation without manual intervention. Discount slabs are managed dynamically by admins. Sales orders route to the correct manufacturer automatically. Buyers can place mixed-product orders the way wholesale purchasing actually works.
The pricing errors that were silently occurring on live orders are gone. The SO routing that was sending consolidation orders to the wrong entity is fixed across all 13 tested scenarios.
Complex business logic is where we start.
If your platform has pricing logic, routing rules, or order workflows that your current team said were "too complex" - that's exactly the kind of problem we take on.