Where should sample management sit: ERP, PLM, or both?

Samples are one of fashion’s most important components, used to approve products, review fits, confirm colourways, support presales, and give direction to production. Yet the management of them tends to sit in an awkward place – sometimes in ERP, sometimes in PLM.

It’s imperative brands manage them correctly because a sample’s usage extends beyond initiating product development. A showroom sample might later shape a customer order, while an approved fit sample could become a reference point for production, and a supplier revision might affect purchasing decisions elsewhere in the business.

So, given they’re essential to both purchasing and the product lifecycle, where should sample management fit… inside ERPs? PLMs? Or both?

Why PLM is important for sample management

Samples are an inherent part of the product development process, which makes a PLM tool a natural place to manage much of the process itself.

Approvals, fittings, supplier communication, deadlines, collection milestones, and development tasks are all contingent on samples being attached to them. If those activities are spread across spreadsheets, emails, and disconnected tools, it’s all too easy for delays to compound until your teams lose countless hours chasing updates.

PLM brings structure to that work by enabling teams to manage development timelines, assign ownership, track progress, and keep sampling connected to the wider collection plan. Within K3 Pebblestone, our PLM tool supports milestones, samples, fittings, approvals, task ownership, and alerts all designed to keep your teams on track throughout the lifecycle.

However, sample management doesn’t “end” after an approval.

Businesses still need to know where samples are, which variants they belong to, whether they have been transferred, what their costs were, and how they relate to purchasing, sales, and production activities. Once those samples start moving through the business, PLM tools alone often struggle to provide that necessary information.

Why ERP is important for sample management

ERPs are equally important for managing samples because they represent physical assets that carry real cost and commercial implications.

A sample may move between offices, suppliers, showrooms, sales teams and customers. It may also be tied to item records, variants, purchase orders, sales orders and production activities, while carrying development, manufacturing and freight costs that businesses often struggle to account for properly.

When sample management is properly built into an ERP process, ownership becomes clearer to track, movement can be monitored, costs are known and logged, and teams ultimately have a stronger link between what was reviewed and produced.

However, without native PLM functionality, an ERP by itself cannot manage the full process either. All the activities described above – milestone management, approvals, collection planning – are better suited to being handled in an out and out PLM tool.

Fashion brands need both ERP and PLM to manage samples

The ideal scenario is to handle the full sample management process across both an ERP and PLM. When both are connected, samples can move through approvals, fittings, and supplier reviews while remaining connected to item records, variants, purchasing, and production.

The end goal of this is not to create additional governance, merely to reduce the number of times where teams have to reconstruct decisions or hunt down information after the fact because it lives in a million different places.

K3 Pebblestone, built inside D365 Business Central, offers sample management alongside a dedicated PLM module to deliver a total system designed to support the full process.

Our PLM capabilities support collection milestones, approvals, fittings, samples, task ownership and alerts, while our sample management tools ensure samples are connected to item records, variants, and other workflows to keep movement, ownership, and cost in check.

If you’d like to find out how K3 Pebblestone can support you, feel free to get in contact today.

FAQ

What is sample management in fashion?

Sample management in fashion is the process of tracking, approving, controlling, and managing samples throughout product development, sales, and production. This includes sample location, ownership, variant history, approval status, movement, associated costs, and connection to the final product.

Should sample management sit in PLM or ERP?

Sample management should usually work across both PLM and ERP. PLM is useful for managing development activity, approvals, fittings, milestones, and supplier tasks. ERP is useful for managing ownership, movement, cost, item records, operational processes, and the connection between samples and production activity.

Why is PLM useful for sample approvals?

PLM gives teams a structured way to manage approvals, development milestones, supplier activity, fittings, tasks, and deadlines. This helps sample approval workflows stay connected to the wider product development plan rather than sitting in spreadsheets, emails, or disconnected conversations.

Why does ERP matter for sample tracking?

ERP matters because samples often move beyond product development. They may be transferred, used by sales teams, linked to purchase orders, associated with production workflows, sold later, or disposed of after use. ERP helps bring ownership, movement, cost, and accountability into the same operational structure as the rest of the business.

What happens when samples are not linked to item records?

When samples are not linked to item records and variants, teams can lose the connection between what was reviewed and what eventually gets produced. This can lead to version confusion, incorrect approvals, repeated work, unclear ownership, and questions around cost or movement that are difficult to answer later.

How does K3 Pebblestone support sample management?

K3 Pebblestone supports sample management by connecting product development activity with Microsoft Dynamics 365 Business Central. Its PLM capabilities help teams manage milestones, approvals, fittings, samples, tasks, suppliers, and alerts, while the wider ERP structure helps connect samples to operational processes such as item records, purchasing, transfers, sales activity, and production workflows.

How can fashion brands improve sample management?

Fashion brands can improve sample management by connecting samples to product records and variants, assigning ownership, tracking movement, recording approval activity, understanding sample costs, and keeping development workflows connected to purchasing, sales, and production processes.