A spreadsheet is a quick way to start an inventory. It allows you to collect a list of products, owners and basic gaps. The problem arises when one row is meant to represent a product, many variants, several suppliers, documents, revisions and decisions. The choice of tool should follow from the scale and risk of the process, not from a belief that every spreadsheet is bad.
When a spreadsheet is enough to start
For a small, stable catalogue, a spreadsheet can act as an intake register. The condition is a clear owner, access control, copies, unambiguous identifiers and the principle that a cell with a link does not replace an assessment of the document. It is worth limiting it to inventory and a migration plan.
A spreadsheet also works well as an import or export format. A user can prepare data in batches, and the system will verify columns, types and duplicates. After import, however, the source of current work should be one agreed record.
Where the difficulties begin
Many-to-many relationships are awkward in a flat table. One report may cover several variants, and one product may rely on many pieces of evidence. An instruction has language versions, packaging has levels and components, and a supplier responds to many requests. Copying values between rows hides dependencies.
It is also difficult to separate permissions. A person completing data may accidentally change an approved decision. The file's change history does not always show the business significance of a change or which version was the basis of a generated document.
Source of data and source of decision
A controlled system stores not only a value but also its provenance. A manufacturer's address may come from a document, a supplier confirmation or a verified record. The decision to use a value has an author, date and scope. This makes it possible to distinguish raw data from approved data.
This is particularly important for GPSR and PPWR, because a complete set of fields does not automatically mean compliance with requirements. The system should show a gap and lead to filling it, but it must not turn an empty cell into a positive conclusion.
Versions and frozen snapshots
A document should indicate the data applicable at the time of approval. If the supplier or packaging weight changes later, the earlier document must not be silently recalculated. A snapshot preserves the values, evidence and rules used in a given revision.
A spreadsheet can be copied before a change, but files called “final”, “final2” and “last” quickly appear. The system enforces a revision number, change description and status. This makes it clear which version is a draft, which is approved and which has been superseded.
Collaboration with suppliers
Sending a template by email is simple, but responses must later be assigned manually. A supplier portal can restrict the view to a single request, require an identifier and record the file transfer. A substantive assessment by the company is still needed.
The system can also monitor deadlines and reminders. It should not expose the data of other contractors or the whole of the organisation's surface to a supplier. Isolation and audit are part of the process, not an add-on to a form.
Permissions and responsibility
Roles make it possible to separate the organisation owner, its space administrator, an editor, a reviewer and a read-only user. A client administrator should not automatically obtain administration of the entire portal. The organisation boundary must be enforced in the backend.
Approval should require an appropriate role, and every operation should record the actor and request identifier. The interface may hide a button, but the actual block must also work in the API.
Operating cost and hard limits
When choosing a system, it is necessary to compare not only the subscription but also the time spent searching for documents, correcting duplicates and reconstructing decisions. A small package may be a good entry point if it clearly shows limits on active SKUs, users and features.
Limits should be predictable and block an operation before a limit is exceeded, without automatic surcharges. The administrator must be able to see usage. The platform's owner account may be technically exempt from limits, but client accounts should be subject to the purchased package.
Criteria for moving away from a spreadsheet
- the number of variants and markets is growing,
- the same data is copied to many places,
- several people approve documents,
- it is difficult to indicate the applicable revision,
- suppliers send many inconsistent files,
- reports do not lead to tasks,
- roles and organisation isolation are needed,
- the company is preparing for an audit or scaling the catalogue.
A sensible transition model
It is best to start with a representative batch of SKUs, agree the structure, perform an import and check the output document. Categories can then be migrated one after another. The spreadsheet remains a useful exchange format, but it ceases to be a place where uncontrolled decisions are made in parallel.
GPSR / PPWR is built as a controlled source of data, evidence and revisions. Its role is to facilitate operational work, not to issue an automatic certificate of compliance.