A procurement director at a garment manufacturer in the Vale do Ave region receives, on average, 47 emails a day from suppliers. Of these, 23 are about the status of orders, deadlines, non-conformities or change requests. None of them leaves an auditable trail. When the end customer asks about the traceability of a batch, the director opens the email folder, searches through three years of conversations, finds two screenshots of WhatsApp messages from a manager who left 18 months ago, and then takes a photo for the AT. This is not inefficiency. It is operational risk disguised as normality.
B2B collaboration between suppliers and industrial customers in Portugal still works, in most cases, through channels that leave no trail: email without workflow, WhatsApp, a phone call jotted down in a physical diary or, in the best case, an ordering portal that does not communicate with the rest of the system. The result is that companies with sophisticated ERPs continue to entrust quality and traceability to tools that were not designed for it. This is not a choice. It is inertia disguised as pragmatism.
The overall trade margin in wholesale trade was 4.6% in 2024, according to INE. Every percentage point of logistical inefficiency or of rework due to non-conformity eats directly into profitability. A company with €50M in purchasing volume that loses 2% of its managers' time on manual traceability activities is wasting between 200 and 400 thousand euros per year — and doesn't even know it.
Email Is Not a Management System
Email is a point-to-point communication tool. It was not designed to leave a trail of decisions, to create approval workflows, to prevent two different suppliers from making contradictory changes to the same order, or to generate an auditable history of changes. Even so, it is to email that Portuguese industrial companies entrust most of their critical interactions with suppliers.
This has direct and measurable costs. A quality manager who spends 6 hours a week consolidating order information scattered across email, WhatsApp and paper notes. A production director who, 48 hours before starting a batch, still has no confirmation that the supplier has met the specification. An audit that results in a non-conformity because the approval of the change "was in someone's email" — and that someone left the company three months ago.
Traceability is not a document. It is a flow of information that everyone in the chain can follow in real time, without interpretation.
When a customer questions the quality of a batch, the company has 48 hours to respond. If that response depends on opening 200 emails and contacting three people who may be on holiday, the deadline runs out before the answer is ready. If the customer is international — Inditex, Decathlon, Tom Tailor — the cost of a late or incomplete response is a loss of trust and, frequently, a loss of volume.
Traceability Without Infrastructure Is Fiction
There is a common belief that traceability is a matter of documentation: keeping a file with the date, the signature of whoever approved it, the order number. The reality is different. Traceability is the ability of a person, at any given moment, to know exactly the status of an order, who modified it, when, why, and with what authority. This requires that the information lives in a single place, accessible to all those involved, with control over who can do what, with a history of changes, and with alerts when something departs from what was planned.
An ordering portal that allows the supplier to view the order, but does not allow them to confirm that they received the specification or question an impossible deadline, is read-only traceability — the supplier sees, but does not participate. A system that records when the supplier confirmed receipt, when production began, when quality control was completed, and that automatically generates a traceability document for the customer, is closed-loop traceability. The difference between the two is the difference between knowing that something happened and being able to prove how and when it happened.
Quality Is Not an Attached Photo
A garment manufacturer receives 80 orders a week from different customers. Each of them has different specifications: exact colour (Pantone + tolerance), fabric (density, elasticity), trimmings (buttons, zips, labels), packaging (number of pieces per box, type of box, label). The fabric supplier sends a sample and an email saying "Colour approved". The manufacturer opens the file, sees the sample, and then what? Keeps the email? Prints the sample? Places it in a sample box with 300 others, with no date, no name of who approved it, no recorded tolerance?
When the batch arrives and the colour is not exactly the same, the customer complains. The manufacturer says "But we had approved it". The customer says "That is an email with a photo. It is not a binding specification". And they are right. Quality requires that each sample, each approval, each deviation, each decision to accept or reject a batch, is recorded in a structured and auditable way — not as an email, but as data in the system.
This means the supplier does not send a sample by email. They send it through an ordering portal, where the manufacturer can record: "Sample received on 2024-11-15, colour Pantone 17-1564 TCX, tolerance ΔE < 1.5, density 240 g/m², elasticity 12%, APPROVED by João Silva on 2024-11-16, valid for orders from 2024-11-20 to 2025-02-28". This is traceability. This is quality.
Integration Is the Critical Point
An ordering portal that does not talk to the ERP is a silo. The supplier confirms the order in the portal, but the procurement manager has to re-enter it into the MULTI ERP because the systems do not communicate. The customer generates a specification change in the portal, but no one knows whether the supplier received it or whether production has already started with the old data.
Integration is not a luxury. It is what turns an ordering portal into a real collaboration system. When the ERP receives a confirmation of receipt from the supplier through an integrated portal, it can automatically: update the status of the order, trigger quality control, generate the estimated arrival at the warehouse, alert production planning if there is a deadline deviation. This is not luxury automation. It is a reduction of reaction time from days to hours.
A few years ago, we believed that a well-designed ordering portal was enough. That suppliers would use it, that data would flow, that email would disappear naturally. Reality showed that without deep integration with the ERP, the portal is consulted when there is a problem — and by then it is too late. Email remains the de facto channel because it is quicker to send a message than to log into a system that does not have the answers you need.
Quality Control Without Paperwork
A textile factory receives 12 dye suppliers and 8 trimmings suppliers. Each of them sends samples, certificates, analysis reports. Some arrive by email, some by post, some by WhatsApp. A quality manager spends 4 hours a week organising this: filing it into folders, updating a spreadsheet, printing it out to archive, searching for old documents when someone questions a batch from 18 months ago.
If the customer questions the compliance of a batch with a sustainability specification — for example, the EU Strategy for Sustainable and Circular Textiles — the response requires locating the supplier's analysis report proving that the dye contains no heavy metals. This is in an email from 2023, in a PDF that someone printed out, in a network folder named "Suppliers_Various_v3_FINAL_REAL". Three people know where it is, and one of them is on parental leave.
A document management system integrated with the supplier portal allows each document to be uploaded only once, automatically classified, versioned, and accessible to anyone with permission within 5 seconds. No paperwork. No duplication. No risk of using an outdated document. No asking someone who no longer works at the company.
When Something Fails, Who Answers?
B2B collaboration without traceability creates a grey zone of responsibility. A batch arrives with a non-conformity. The supplier says "But the specification you sent was wrong". The company says "No, the specification was correct, but you did not read it properly". The customer complains. No one can prove who is right because the specification was sent by email, modified by WhatsApp, and the confirmation of receipt is an "ok" in a chat.
A system without traceability does not protect quality. It protects the argument.
When responsibility is clear — because each action was recorded, with who did it, when, and with what data — the resolution is fast. It is not an argument. It is a fact. The supplier sees exactly what they approved. The company sees exactly when the supplier confirmed. The customer sees exactly the complete flow of approval and execution. This reduces the time to resolve non-conformities from weeks to days, because there is no room for contradictory interpretations.
The Real Cost of Disorganisation
According to INE, the overall trade margin in wholesale trade in Portugal was 4.6% in 2024. This means that every percentage point of logistical inefficiency or of rework due to non-conformity eats directly into profitability. A company with €50M in purchasing volume that loses 2% of managers' and operators' time on activities related to manual traceability is wasting between 200 and 400 thousand euros per year. This does not include the cost of non-conformities that take time to be detected, of deadlines missed due to a lack of clear communication, or of failed audits.
Most companies that implement an ordering portal integrated with the ERP manage to recover the investment within 14-18 months, purely through the reduction of administrative rework and of the time taken to resolve incidents. The rest is margin.
Frequently asked questions
Why is email problematic for managing orders with suppliers?
Email was not designed to create approval workflows, prevent contradictory changes or generate auditable histories. Companies entrust critical information to a point-to-point tool that leaves no trail of decisions, making traceability difficult when customers question the quality of a batch.
What is the difference between read-only traceability and closed-loop traceability?
Read-only traceability allows the supplier to view the order, but not to participate actively. Closed-loop traceability records when the supplier received the specification, started production, completed quality control and automatically generates documentation. The difference is between knowing that something happened and being able to prove how and when.
What does real-time traceability mean?
Traceability is the ability of anyone to know, at any moment, the exact status of an order, who modified it, when, why and with what authority. It requires that information lives in a single place, accessible to all, with permission control, a history of changes and automatic alerts.
How should the approval of a quality sample be recorded?
Approval should not be an email with an attached photo. It should be recorded in a structured way in the system with: date of receipt, exact specifications (Pantone, tolerance, density), name of who approved it, date of approval and validity period. This turns the approval into an auditable data point, not an informal communication.
What is the financial impact of managing traceability manually?
A company with 50 million euros in purchasing volume that loses 2% of its managers' time on manual traceability activities wastes between 200 and 400 thousand euros per year. Every percentage point of logistical inefficiency or rework due to non-conformity directly reduces profitability.
Why is it critical to respond quickly to customer quality queries?
When a customer questions the quality of a batch, the company has 48 hours to respond. If that response depends on opening hundreds of emails and contacting people who may be absent, the deadline runs out. With international customers, a late or incomplete response results in a loss of trust and volume.
What is a system silo and what is its impact?
An ordering portal that does not communicate with the ERP is a silo. The supplier confirms in the portal, but the manager re-enters it manually into the ERP. Specification changes in the portal may not reach the supplier before production starts. Integration is essential to turn a portal into an effective management tool.