- CPQ engine
Multi-tier discount schedules
Volume, contract, and promotional discounts compound in a declared order rather than whichever order the rep applied them. The order is part of the price book, so two reps quoting the same cart get the same number.
DistributionManufacturing
- CPQ engine
Customer-specific price books
A price book is versioned and effective-dated. Requoting an old order reprices against the book that was live then, which is what makes a disputed invoice resolvable.
DistributionManufacturingShading
- Control & governance
Margin floor enforced at the line
The floor is checked on the line, on the document total, and again at approval. A quote cannot be sent below it without an approval that is recorded against a named person.
DistributionManufacturingShadingAutomation
- CPQ engine
Parametric product configuration
Finished dimensions in, cut list out. The deduction logic is catalogue data rather than tribal knowledge, so the estimator who has been here three weeks produces the same cut sheet as the one who has been here eleven years.
ShadingManufacturingAutomation
- CPQ engine
Configured BOM generation
The bill of materials is emitted by the same configuration that produced the price, with part numbers resolved against the ERP catalogue. Engineering reviews it rather than rebuilding it.
ManufacturingAutomation
- CPQ engine
Multi-currency quote exports
The conversion rate and its retrieval timestamp are stamped onto the document. A quote issued in USD in March is defensible in June because the rate it used is on the page.
ManufacturingDistribution
- Field operations
Skill-tag and certification matching
Technicians are matched to work by capability, and any certification expiring before the scheduled install date removes them from consideration automatically rather than at an inspection.
Field servicesAutomationShading
- Field operations
Route optimisation with real constraints
Optimised against customer time windows, van inventory, technician skills, traffic profile, and the overtime ceiling — not just against distance, which is the version that produces an impossible day.
Field servicesDistribution
- Field operations
Offline-first technician app
The device is the primary store. Job completion, parts consumed, photos, and signatures are captured with the radio off and reconciled on reconnect with per-field merge.
Field servicesAutomationShading
- Field operations
Van inventory and parts consumption
What is on the van is a tracked location, not an assumption. Parts consumed at completion decrement it and flow straight into the draft invoice.
Field servicesDistribution
- Integration
Bidirectional ERP synchronisation
Customers, parts, and invoices reconcile in both directions with a declared system of record per entity, so nobody has to guess which side wins on a conflict.
DistributionManufacturingField services
- Integration
KNX and DALI commissioning exports
Group addresses are generated from the design record at sign-off, so the as-built and the installed system start life identical instead of drifting from day one.
AutomationShading
- Integration
Motorised hardware provisioning
Motor addressing and scene bindings are emitted from the same configuration that priced the shade, so the commissioning technician is not retyping addresses from a quote PDF.
ShadingAutomation
- Control & governance
Threshold-based approval workflow
Discount depth, contract value, and non-standard terms each carry their own approver. The rule is configuration, so changing who signs off on a 30% discount is a settings change rather than a release.
DistributionManufacturingField services
- Control & governance
Append-only audit lineage
Every quote revision and dispatch assignment is an immutable entry. You can reconstruct exactly what a customer was shown on a given day, which is the only version of this that survives a dispute.
DistributionField servicesManufacturingShadingAutomation
- Control & governance
Granular RBAC scopes
A field technician sees the job, not the margin. A CFO sees the margin, not the customer's door code. Scopes are granted per role and enforced at the API rather than hidden in the UI.
DistributionField servicesManufacturingAutomation