Jewelry Design Change Request: How Brands Control Revisions

Classify the issue before deciding what to do. A clarification resolves an uncertain instruction; a correction addresses a mismatch with the agreed reference; a design change proposes a different requirement; a substitution proposes another material or component. More than one category can apply, so describe the facts rather than using a label to decide responsibility. A supplier proposing another clasp because a component is unavailable still needs the affected product and approval scope identified.

Do not treat a proposed improvement as proof that the original sample was defective, or a reported defect as permission for an unrelated redesign. Record the observed difference, the current requirement and the requested outcome separately. The existing sample approval guide explains the physical review; this guide controls what happens when that review or a buyer decision creates a new request. Avoid deciding costs, refunds or other contractual rights from the category alone; those matters need the applicable agreement and, where necessary, qualified advice.

Give the request its own identifier and connect it to the style, drawing or CAD revision, physical sample, specification, component list and order where one exists. Include the request date and source of the current baseline. If the design is still exploratory, say which proposed reference is being discussed and what has not been approved. A project name, an unversioned image and the phrase latest file are not enough to identify the starting point.

NASA's configuration-management guidance describes controlled references, evaluation of proposed changes and verification of approved implementation. Those are general record-control principles adapted here, not aerospace procedures imposed on a jewelry buyer. ISO 10007:2017 is also published as configuration-management guidance; its public scope does not certify this worksheet or Zalson's operations. Keep the request linked to identifiable records while choosing a practical level of control for the actual project.

For each changed feature, show the current requirement, proposed outcome, reason and affected view or reference. Mark whether a dimension is a buyer requirement or a supplier proposal needing confirmation. If a measurement is not yet known, ask for a dimensioned proposal instead of inserting an invented number. Explain the intended result without prescribing an unreviewed manufacturing solution. A visual reference can communicate direction, but it cannot establish a material identity or hidden construction.

Consolidate feedback from design, buying and marketing into one numbered request. Resolve conflicting instructions before the supplier develops two incompatible responses. BJM's CAD/sample review and 925 Pro's revision discussion both emphasize specific feedback and controlled references; their project policies and numerical examples are not adopted here. Keep unchanged requirements visible as well, so a request to alter a bail does not accidentally release a different stone, finish or overall product size.

A request before CAD development differs from one after a sample has been approved, but the stage label alone does not explain the exposure. Ask what is unstarted, ordered, received, tooled, in process, completed or packed for the affected styles and quantities. Record the status as of a stated date. A sample may be awaiting buyer approval while some separately authorized material purchasing has already occurred; neither record should be assumed from the other.

Royi Sal's public FAQ explains that post-approval or production-stage changes may affect feasibility, development work, cost and time. Treat this as a manufacturer perspective, not a Zalson revision allowance or fee rule. Request a project-specific response for each affected work group. Keep existing work identified while the decision is pending, and agree whether any limited hold or continued work applies; do not imply that an email automatically stops every operation or changes the parties' contract.

Ask the supplier to identify direct and dependent effects. A different stone size may affect its seat and profile; a closure change may alter the finished length, handling and box fit; a finish change may require another appearance reference and evidence review. These are questions to evaluate, not assumed outcomes. Use the chain and clasp specification guide, gemstone guide and plating guide for the detailed inputs rather than restating their complete requirements inside the request.

Request separate answers for feasibility, tooling or development work, material allocation, unit or quantity effects, new sample or verification needs and the proposed schedule. Ask which assumptions remain open and when the assessment is valid. Include artwork, care information, packing and any claim supported by the changed component. Do not assume every revision increases price or that a small visual change is inexpensive. Obtain a revised quotation or written scope confirmation where needed before approving commercial consequences.

Keep the request, supplier assessment and buyer decision as distinguishable parts of one record. The requester states the desired change; the evaluator identifies consequences; the authorized decision owner accepts, rejects or requests more information. The blank fields below are not a completed approval or a contractual amendment. Duplicate rows for multiple features and attach marked references so the record remains usable without reconstructing a long conversation.

Record which affected quantities, components and work states the decision covers, including any planned split between versions. Give unresolved questions an owner and next review rather than marking the entire change approved with a vague note. The PO guide explains the order references and the lead-time guide handles dependency planning. Link their relevant versions to the request, then preserve the proposed versus acknowledged cost and date fields separately so an internal target is not mistaken for supplier confirmation.

Agree who can request, assess, authorize, publish and receive the change. One buyer contact may consolidate feedback without having authority to approve extra expenditure or release production. Record the relevant approval route rather than assuming that the person commenting on a render can decide every consequence. Useful working states include requested, under assessment, awaiting decision, rejected, approved for a defined scope, released and verified. Choose labels the parties understand and define what each permits.

An acknowledgment that a request was received is not approval of its technical or commercial content. A revised render is a proposal unless the named authority accepts its identified scope. Silence should not be treated as a release instruction in this workflow. Where only a trial or limited quantity is authorized, state that boundary, the remaining restrictions and the next decision needed. Preserve rejected and withdrawn requests so an obsolete alternative cannot later reappear as an undocumented instruction.

For a substitute chain, stone or finding, request its identity, differences, reason for proposal and effect on the product and evidence. Ask whether a new physical sample, fit review or test is needed before acceptance. Do not allow a supplier reference alone to stand for a technical equivalence decision. If an earlier material has already been purchased or assembled, keep its quantity and proposed treatment separate from the proposed new version.

Possible dispositions may include continued use within an agreed scope, rework, separate retention or another mutually confirmed action; none is prescribed automatically here. A mixed-version first order requires explicit buyer acceptance, identification, packing and receiving instructions if it is to proceed. Do not blend versions silently to meet a quantity. Cost allocation, cancellation, ownership of tooling or files and disposal obligations must be resolved through the applicable agreement, not inferred from this editorial checklist.

Issue an identified new file set with a change summary and the authorized effective scope. Include drawings, component and stone schedules, finish references, sample notes, packaging and inspection instructions where affected. Preserve prior versions as history and mark them as superseded for the relevant work; do not delete evidence of what was approved earlier. Ask recipients to acknowledge the released revision and explain how outdated workshop or packing copies are prevented from controlling the next step.

Document release and physical implementation are different events. Obtain the agreed revised sample or other verification, compare it with the approved change and close dependent checks before the next authorized gate. DinHuey's sample guide distinguishes a retained reference from bulk acceptance; the same boundary matters after a change. Keep open verification visible in the quality plan, and review shipment records if quantities or packing change. The supplier sending a new filename does not by itself prove that every affected unit follows it.

Stuller's September 18, 2026 customization update describes routes from ideas, existing styles and customer files, with project visibility tools. The buyer-side inference is narrow: different starting points need a clearly identified current reference and decision stage. A status dashboard or email update does not replace the scope of a change approval. This is industry context, not a claim that Zalson operates Stuller's systems or offers the same service policies.

For the first order, close the transition from exploration to released configuration before assuming that future units can repeat it. The catalog references below remain unchanged examples for discussing product scope, not documented revision case studies. Once the initial baseline is established, the reorder checklist takes over the repeat-order review. Keep this request focused on the difference being proposed now, its affected work and the authorization needed, instead of attaching every earlier development conversation to each new message.

When discussing a Zalson project, send the current reference, the marked proposed change, known affected quantities, work stage and desired outcome. State what you need the team to assess and which matters remain unconfirmed. Existing designs can be useful starting references, but no catalog page establishes the feasibility, fee or timing of a new variation. Use the RFQ checklist when a revised scope needs a comparable quotation rather than asking the supplier to price an undefined redesign.

Before closing the request, check that the decision, released documents, recipient acknowledgment and verification all cover the same scope. Record any remaining action instead of calling the whole project approved. No fixed revision allowance, automatic fee or guaranteed turnaround is created by this workflow. Its value is a traceable decision chain: a buyer can see what was requested, what was assessed, what was authorized and what has actually been checked.