Bi-directional
PrestaShop
Bi-directional sync of parts catalogue, stock levels, orders, and customer data via PrestaShop XML/REST API.
Read the specSolutions · Strategic · Dismantler Group Director
Sustain360 for Dismantler Group Director
The Dismantler Group Director operates two-to-ten yards under one brand. The buying question is whether one platform can roll up the whole group without forcing every yard onto an identical workflow. Sustain360 answers with tenant-level configuration and yard-level workflow overrides — one rollup view, many local realities.
Where this role sits:Two-to-ten-yard dismantler groups operating under one brand
A day in the life
How a dismantler group director works with Sustain360
Monday is the group rollup: throughput by yard, exception queues by yard, ledger by yard, all on one screen. The Leeds yard's teardown is six states; the Manchester yard's is five — both run against the same platform. Pricing rules sit at the group level with yard-level overrides; PrestaShop credentials are per yard, not per tenant.
USP · Manual vs Sustain360
What this changes for a Dismantler Group Director
A side-by-side view of the legacy / manual way of working against the Sustain360 way — with concrete, illustrative numbers from typical customer-development scenarios.
- MetricCross-yard KPI rollup speedManual / legacyWeekly spreadsheet pullWith Sustain360Live dashboard, drill-downDeltaAlways-on
- MetricWorkflow flexibility per yardManual / legacyOne template, friction at every yardWith Sustain360Tenant-level config + yard overridesDeltaConfigurable
- MetricTime to onboard a new yardManual / legacy3–6 monthsWith Sustain3604–6 weeksDelta≈ −75%
- MetricGroup-wide exception visibilityManual / legacyEach yard reports upWith Sustain360Single queue, group-levelDeltaUnified
- MetricStandardised reporting cadenceManual / legacyMonthly, often lateWith Sustain360Daily, on-demandDeltaReal-time
| Metric | Manual / legacy | With Sustain360 | Delta |
|---|---|---|---|
| Cross-yard KPI rollup speed | Weekly spreadsheet pull | Live dashboard, drill-down | Always-on |
| Workflow flexibility per yard | One template, friction at every yard | Tenant-level config + yard overrides | Configurable |
| Time to onboard a new yard | 3–6 months | 4–6 weeks | ≈ −75% |
| Group-wide exception visibility | Each yard reports up | Single queue, group-level | Unified |
| Standardised reporting cadence | Monthly, often late | Daily, on-demand | Real-time |
Illustrative — based on customer-development scenarios in the dismantling, salvage, and parts-resale industry. Real outcomes vary by yard size, workflow maturity, and integration scope. Reference contacts available on request.
Pain → Outcome
Pain today, outcome with Sustain360
Five to seven concrete pains this role lives with today, paired with the specific Sustain360 outcome that removes each one.
| Pain today | With Sustain360 |
|---|---|
| One platform forces every yard onto the same workflow. | Tenant-level config with yard-level workflow overrides. |
| Rollup reporting is a manual merge of spreadsheets. | Group dashboard reads across every yard's live state. |
| Pricing rules diverge yard by yard. | Group rules with yard overrides — audit-trail captures both. |
| Onboarding the next yard takes a quarter. | Yard rollouts run as configuration, not as a re-platforming. |
| Compliance reporting reassembles across yards. | Group-level compliance export across every yard in scope. |
Placeholder · Customer voice
“Each yard kept its workflow. I got the rollup. Nobody got told to change how they work.”
Workflow stages
Workflow stages most relevant to this role
The stages this role touches most often. Each stage is a page in its own right with capabilities, integrations, and FAQs.
Integrations
Integrations most relevant to this role
Connectors that matter to this role in practice. Browse every integration in the integrations directory.
Outbound
NopCommerce
Parts and stock push to NopCommerce storefronts.
Read the specOutbound
CSV / Excel export
Every grid in the product exports to CSV.
Read the specBi-directional
REST API
Public, versioned, documented (Swagger / OpenAPI).
Read the specFAQ