TL;DR · Direct answer
The buying decision in brief
Freeze an order by approving one dated baseline that identifies the model, base unit, configuration, accessories, market assumptions and relevant file versions. Keep changes outside that baseline until they have an impact review and written approval. This is a buyer-control framework; it does not establish product certification, availability, engineering feasibility or supplier commitments.
01 / Buying guide
Create a dated configuration baseline, not a loose collection of files
A frozen configuration begins with a dated record that identifies the model or proposed baseline under review. Link it to the current quotation, configuration list and supporting images or documents actually supplied. Do not use a category name, undated presentation or similar-looking image as a substitute for a specific baseline.
Name the buyer-side owner, intended destination market, quantity and project stage. These fields establish context; they do not imply supplier acceptance or that a product is permitted in a market. Keep anything not yet confirmed visibly marked as open.
- Baseline ID, revision and approval date
- Exact model identifier and source of reference
- Buyer, decision owner, quantity and target market
- Linked quote, configuration list and open-item register

02 / Buying guide
Keep model, configuration, standard items and files distinct
The model is the starting identity. The configuration is the particular combination proposed for that model. Standard items are stated as part of the base offer; optional items are separately selected or quoted additions. A document version is a specific supplied file or artwork revision. A market version describes buyer destination assumptions, not a conclusion that an approval or registration exists.
Create a row for every item that could change the decision: base unit, handpiece, accessory, consumable, voltage, plug, interface, label, manual, packing and requested documentation. Mark it included, optional, excluded, pending or not supplied. This makes a “full configuration” statement testable before the order.
- Model identity: code, label reference and version where supplied
- Configuration: base unit plus each selected component
- Supply status: standard, optional, excluded or pending
- Files: title, date/revision, holder and stated scope
- Market context: buyer destination and questions requiring qualified review
03 / Buying guide
Use a pre-order confirmation matrix
A confirmation matrix turns an email trail into an ordered decision list. Put the baseline identifier in every row, then list the item, buyer expectation, supplier statement, evidence reference, decision status and person who can approve a change. A blank cell is useful information: it identifies a question that should not be resolved by assumption.
Review the matrix with people responsible for commercial scope, receiving, technical fit and any destination-market review. Each organization chooses its own approval route. This page does not identify Aurum Epoch’s internal process or state that every option, document or market version is available.

04 / Buying guide
Treat every difference as a change request
A difference may appear in a quote, image, label, manual, packaging proof or sample discussion. Log it first: what changed, compared with which baseline, who noticed it and what evidence is attached. Then ask the supplier and the relevant buyer owner to assess its effect before replacing the baseline.
A practical change request can include the proposed item, reason, affected file references, stated commercial or timeline effect, unresolved market questions and written decision. Do not assume a visual change is only cosmetic or a file change has no scope consequence. Applicability depends on product, intended use, market and legal roles.
- Describe the difference against a dated baseline
- Request the supplier’s stated impact rather than guessing it
- Keep technical, commercial and market questions separate
- Approve, reject or leave pending in writing
- Issue a new baseline only after approved change incorporation
05 / Buying guide
Release an order record only after open items are controlled
Before authorizing an order, check that the baseline, matrix and decision trail refer to the same model and configuration. List any remaining open item beside the decision rather than implying it has been closed. The commercial contract, quotation and purchase order remain controlling documents for the parties; this guide helps prepare a more precise review package.
Retain the final configuration record for receiving and future support questions. At receiving, use it to check what was ordered against what arrived and route discrepancies through the agreed commercial process. It is not a test report, certificate, shipping promise or performance guarantee.
06 / Buying guide
Keep the minimum records that make a later question answerable
A useful record set is small enough to maintain: baseline version, approved matrix, relevant file versions, change requests, written approvals and final order reference. Give each record a date and owner. Store it in the buyer’s controlled procurement location instead of relying on personal inboxes or an unlabelled chat image.
If a later reorder starts from an old configuration, ask whether the original baseline is still suitable rather than copying it forward automatically. The same matrix can request a current response, identify changed assumptions and decide what needs a new approval.
Comparison visual
What belongs in the baseline—and what needs its own decision
Model
The named product identity used for the request
Proof that every pictured or similar unit is the same configuration
Configuration
The selected base unit, components and options
A vague “full set” without a line-item list
Document version
A specific supplied file or artwork revision
Proof of universal market approval or product certification
Market context
Buyer destination and review questions
A conclusion that requirements have been met
Decision flow
Configuration-freeze and change-control flow
- 01
Baseline
Create one dated model-and-configuration reference.
- 02
Map
List each included, optional, excluded and pending item.
- 03
Review
Match files, market assumptions and buyer responsibilities.
- 04
Control changes
Assess every difference before it replaces a prior decision.
- 05
Release
Keep the approved record with the order and receiving file.
Practical table
Configuration-freeze record before order approval
Each checklist row shows every comparison field.
| Record field | What to capture | Decision check |
|---|---|---|
| Baseline identity | Revision, date, model and buyer project | One current reference |
| Configuration | Base unit, accessories, handpieces and options | Each line has a supply status |
| Files | Quote, label/manual/artwork references and revisions | Scope and open questions visible |
| Market context | Destination, language, voltage and buyer review needs | No unverified approval claim |
| Change request | Difference, impact request, owner and written decision | No silent substitution |
| Release package | Approved matrix, open items and order reference | Buyer approval route complete |
Buyer FAQ
Frequently asked questions
When is a configuration frozen?
When the buyer has approved one dated baseline and any remaining questions are explicitly recorded rather than hidden in unrelated messages.
Is the product model the same thing as the configuration?
No. One model may be discussed with different components, accessories, language, voltage or documentation assumptions. Record the selected combination separately.
Do manual and label versions belong in the freeze record?
Where they are in the buyer’s review scope, record the supplied version and its stated scope. Do not infer market approval from their presence.
What should happen if a supplier proposes a change after approval?
Log it against the baseline, request the stated impact, route it to the appropriate owner and create a new revision only after written approval.
Source notes
References and further reading
External references provide general regulatory or industry context; they do not establish approval of a listed product. Accessed 27 September 2026.
Turn the checklist into a model-specific quotation
Send the exact model, destination market, quantity and configuration you need. Ask for the applicable documents and service scope in the response.
Request a quotation →
