{"id":931255,"date":"2026-10-19T08:03:33","date_gmt":"2026-10-19T08:03:33","guid":{"rendered":"https:\/\/ecobridgestove.com\/?p=931255"},"modified":"2026-10-22T01:33:41","modified_gmt":"2026-10-22T01:33:41","slug":"gas-stove-repeat-order-check","status":"publish","type":"post","link":"https:\/\/ecobridgestove.com\/es\/gas-stove-repeat-order-check\/","title":{"rendered":"Repetici\u00f3n de pedidos de cocinas de gas: comprobaci\u00f3n de revisi\u00f3n antes de una nueva orden de compra"},"content":{"rendered":"

Before repeating a gas stove order, compare the proposed supply with the last approved purchase package and the records of what was actually delivered. The same supplier model number is useful for finding the file, but it does not establish that the next order has the same configuration, packaging, documents or commercial scope.<\/p>\n

Approve the new PO when every material field is confirmed unchanged, approved as a specific revision, or assigned a clearly controlled condition. If the supplier cannot identify the applicable version, keep that field open and resolve its effect before releasing the affected purchase requirement.<\/p>\n

This guide helps importers, distributors and private-label purchasing teams create that comparison. A real ECOBRIDGE Model 6001 document discrepancy shows why copying the last order description can leave the packing basis uncertain. The buyer tools include a revision comparison form, a supplier declaration, a carton reconciliation example and a repeat-order approval record.<\/p>\n

Quick Answers for Repeat-Order Buyers<\/h2>\n\n\n\n\n\n\n\n\n\n
Buyer question<\/th>\nPractical answer<\/th>\n<\/tr>\n<\/thead>\n
Does the same model code prove that nothing changed?<\/td>\nNo. Match the complete variant and its controlled product, packing and document references.<\/td>\n<\/tr>\n
Which old records should be used?<\/td>\nSeparate the last approved specification from the records of the supplied lot, including any approved exceptions.<\/td>\n<\/tr>\n
Does a different catalog entry prove a later production change?<\/td>\nNo. Cross-document differences need explanation; they do not establish chronology or the configuration previously shipped.<\/td>\n<\/tr>\n
Must every repeat order receive a new sample?<\/td>\nChoose the review from the affected requirement and available evidence. Do not assume that either a new sample or the old sample resolves every change.<\/td>\n<\/tr>\n
What should accompany the new PO?<\/td>\nThe current reference register, resolved comparison form, approved amendments and a supplier acknowledgement tied to the new order.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

1. Reconstruct the Last Order Before Asking for the Same Again<\/h2>\n

Separate approval from delivery history<\/h3>\n

Retrieve the last PO and its approved amendments, specification, sample record, artwork, packing specification and supplier acknowledgement. Then retrieve the shipment’s inspection report, packing list, release record and relevant arrival findings. These groups answer different questions: what was ordered and what the records say was supplied.<\/p>\n

A concession for one shipment may have allowed an exception without changing the normal product requirement. Carrying it into the new order automatically can turn an isolated decision into a recurring specification. Record its scope and ask whether it expires with the old lot or has been deliberately incorporated into the new baseline.<\/p>\n

Name the baseline<\/h3>\n

Give the old purchase package an identifier and date. Record the PO, complete supplier model, buyer SKU, destination and approved revisions. Where historical documents are incomplete, mark the gap. Do not replace missing evidence with a current catalog screenshot and call the reconstruction complete.<\/p>\n

If the received goods did not match the approved package, retain both records and the disposition. Purchasing, quality and logistics should review the same history before requesting another shipment. This prevents a reorder conversation from starting with several incompatible meanings of \u201clast version.\u201d<\/p>\n

2. The ECOBRIDGE 6001 Example: One Model, Two Quantity Entries<\/h2>\n

Two first-party sources contain a Model 6001 entry: the ECOBRIDGE April 2026 gas stove catalog and the supplier’s English working sheet. The catalog uses the field PCS\/CTN<\/strong> and records 10<\/strong>. The working sheet’s 6001 block uses Number of boxes<\/strong> and records 18PCS<\/strong>.<\/p>\n\n\n\n\n\n\n\n\n
Question<\/th>\nCatalog record<\/th>\nWorking-sheet record<\/th>\nRepeat-order action<\/th>\n<\/tr>\n<\/thead>\n
Which model is identified?<\/td>\n6001<\/td>\n6001 in the English model block<\/td>\nAsk for the complete current variant and the old PO’s configuration reference.<\/td>\n<\/tr>\n
What does the quantity field say?<\/td>\nPCS\/CTN: 10<\/td>\nNumber of boxes: 18PCS<\/td>\nRetain the original labels and ask what each quantity counts.<\/td>\n<\/tr>\n
Which source governs this order?<\/td>\nCatalog reference only<\/td>\nWorking reference only<\/td>\nObtain a signed packing specification tied to the new PO.<\/td>\n<\/tr>\n
Does this establish a change since the last shipment?<\/td>\nNo historical PO linkage supplied by this comparison<\/td>\nNo approved change chronology supplied by this comparison<\/td>\nCompare both sources with the actual previous-order records before describing a change.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Preserve the difference in meaning<\/h3>\n

Do not silently rename \u201cNumber of boxes\u201d as \u201cunits per master carton.\u201d Ask the supplier to confirm its intended meaning, packing level, unit and applicable configuration. If it represents units per carton, ask which packing specification supports that interpretation and which orders it covers.<\/p>\n

The distinctive finding is not that ECOBRIDGE changed a pack from 10 to 18. The available evidence establishes two differently labeled quantity entries associated with the same model code. It does not establish the sequence, approval status or applicability of those entries to a buyer’s previous shipment.<\/p>\n

Ask a question that can close the discrepancy<\/h3>\n

Send both extracts with the previous PO reference and ask: \u201cFor the configuration previously supplied under this PO, what was the approved units-per-carton basis? What basis is proposed for the new PO? Please identify the packing drawings, revisions and effective lots, and explain the two source entries.\u201d<\/p>\n

That request produces an order-specific answer. Selecting whichever figure gives a preferred carton count leaves the underlying question unresolved. Neither entry establishes an MOQ, loading commitment, current offer or approval for a destination market.<\/p>\n

3. Complete a Revision Comparison Form<\/h2>\n

Use one row for each purchasing requirement. Include the old approved reference, proposed new reference, supplier response and buyer decision. A statement that all products are \u201cstandard\u201d does not replace that comparison.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Requirement<\/th>\nLast-order reference<\/th>\nNew-order evidence to request<\/th>\nDecision to record<\/th>\n<\/tr>\n<\/thead>\n
Product identity and construction<\/td>\nComplete model, variant, buyer SKU and approved configuration<\/td>\nCurrent configuration sheet and an explicit unchanged\/changed statement<\/td>\nConfirmed continuity, approved revision or unresolved identity<\/td>\n<\/tr>\n
Components and technical documents<\/td>\nApplicable parts\/configuration references and technical evidence<\/td>\nDeclared substitutions, affected documents and proposed review<\/td>\nNamed technical review and closure where required<\/td>\n<\/tr>\n
Branding, manual and labels<\/td>\nApproved files, language, revision and destination inputs<\/td>\nPrint-file comparison and identification of any remaining old stock<\/td>\nFiles authorized for this PO and treatment of old versions<\/td>\n<\/tr>\n
Packing and quantities<\/td>\nCarton revision, unit definition, contents and packing list basis<\/td>\nCurrent signed packing specification, quantities and markings<\/td>\nAgreed basis and reconciliation to sellable units<\/td>\n<\/tr>\n
Offer and order scope<\/td>\nPrevious inclusions, exclusions and accepted order terms<\/td>\nCurrent dated quotation and acknowledgement for the new quantity<\/td>\nAccepted scope and separately recorded open conditions<\/td>\n<\/tr>\n
Exceptions and corrective actions<\/td>\nPrior concessions, findings and closure records<\/td>\nApplicability statement and evidence for unresolved items<\/td>\nClosed, retained for review or expressly carried forward<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Require a response for unchanged fields<\/h3>\n

Blank cells are ambiguous. They can mean unchanged, not reviewed or awaiting a response. Use explicit statuses such as \u201cconfirmed unchanged against reference,\u201d \u201cproposed change\u201d and \u201cnot yet confirmed.\u201d A supplier’s confirmation should identify the reference it reviewed and the person making the declaration.<\/p>\n

Keep comparison status separate from approval status. A proposed difference can be fully described but still awaiting a technical or purchasing decision. Conversely, a row described as unchanged can remain unresolved if the referenced file is unavailable.<\/p>\n

4. Reconfirm the Offer for the New Order<\/h2>\n

Check what the repeated description includes<\/h3>\n

Request a current quotation for the exact model, variant, quantity, destination inputs and packing version. Compare inclusions and exclusions with the last accepted offer. Pay particular attention to manuals, labels, loose items, branding, spare parts and services that were previously quoted separately.<\/p>\n

Do not carry the previous unit price, delivery date, payment arrangement or quotation validity forward by assumption. Ask the supplier to state the current offer and any dependencies. This article provides a purchasing comparison process; it does not state ECOBRIDGE’s current commercial terms or predict a repeat-order discount.<\/p>\n

Separate order quantity from packing quantity<\/h3>\n

State the desired number of sellable units and define what is supplied with each unit. Then confirm carton contents and any applicable order minimum separately. If the supplier proposes a new quantity condition, identify whether it concerns the finished product, a printed item, a component or a packing multiple.<\/p>\n

Use the gas stove MOQ guide<\/a> for that separate minimum-order discussion. The repeat-order comparison should record the supplier’s current answer without treating a carton figure as a production minimum.<\/p>\n

5. Reconcile Cartons Without Rewriting the Unit Order<\/h2>\n

The 6001 discrepancy is especially relevant when a buyer repeats a carton count rather than a unit quantity. If the meaning of the packing field changes or remains unclear, a copied carton total may no longer represent the intended number of sellable stoves.<\/p>\n

Use a clear calculation basis<\/h3>\n

Record total units, confirmed units per full carton, number of full cartons and units in any approved partial carton. Reconcile them with this identity: total units = full cartons \u00d7 units per full carton + units in partial cartons. A partial carton requires an agreed packing and marking arrangement; arithmetic alone does not authorize one.<\/p>\n

For illustration only, if 900 units were ordered and the supplier confirmed a 10-unit carton basis, the arithmetic would be 90 full cartons. If an 18-unit basis were instead confirmed, 900 units would equal 50 full cartons. These are hypothetical planning calculations, not an ECOBRIDGE quotation, MOQ, packing approval or evidence that the working sheet’s 18PCS has that meaning.<\/p>\n

Update dependent records together<\/h3>\n

Once the basis is agreed, reconcile the PO quantity, packing list, carton marks and loading request. Ask for the applicable carton dimensions and weight basis rather than applying figures from another packing version. Keep estimated loading figures separate from the order’s final packing and loading records.<\/p>\n

The unit quantity should change only through the buyer’s order process. A supplier’s packing proposal is a reason to discuss quantities and handling, not permission to silently increase or decrease the purchase.<\/p>\n

6. Route Declared Changes to the Right Review<\/h2>\n\n\n\n\n\n\n\n\n\n
Supplier response<\/th>\nEvidence needed<\/th>\nBuyer route<\/th>\n<\/tr>\n<\/thead>\n
Confirmed unchanged<\/td>\nExact references reviewed and their applicability to the new PO<\/td>\nRecord the declaration and resolve any inconsistent source.<\/td>\n<\/tr>\n
Document or artwork revision<\/td>\nOld\/new files, difference list, applicable SKU and stock treatment<\/td>\nObtain the appropriate document and print approval.<\/td>\n<\/tr>\n
Physical or technical substitution<\/td>\nExact proposed difference and affected specification\/evidence<\/td>\nRequest qualified review, sample or other verification according to the impact.<\/td>\n<\/tr>\n
Packing revision<\/td>\nCurrent arrangement, quantities, dimensions and supporting approval<\/td>\nReconcile logistics and determine the needed pack review.<\/td>\n<\/tr>\n
Cannot confirm<\/td>\nNamed missing record, owner and proposed closure date<\/td>\nKeep the affected field open and define its release consequence.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not infer technical equivalence from a sales description<\/h3>\n

A supplier may retain a familiar sales code while proposing a different component, finish or supplied accessory. Ask for the exact difference and the references affected. Technical and market-specific evidence should be reviewed by the appropriate qualified parties for the actual configuration.<\/p>\n

Use the component change approval guide<\/a> when the comparison identifies a proposed substitution. This repeat-order process finds and records differences; the change review determines what evidence is needed to approve them.<\/p>\n

Scope the old sample correctly<\/h3>\n

Identify which features the old sample approved and whether it represents the newly proposed configuration. A physical sample can support a visible comparison while leaving manual language, packing quantity or technical-document applicability unresolved. Choose any new sample or review requirement from the actual gap.<\/p>\n

7. Control Artwork Stock and the First Lot of the New Order<\/h2>\n

Ask which labels, manuals, retail boxes and master cartons remain from the last run. Record their identifiers and quantities where relevant to the order. Old printed stock can match one revision and conflict with another, even when the appliance model code is unchanged.<\/p>\n

State what may be used<\/h3>\n

Authorize specific approved files or stock references for the new PO. If several market or language versions are involved, map each one to its buyer SKU and destination. Do not use a generic \u201csame artwork\u201d instruction when the comparison identifies a changed address, barcode, model reference or manual revision.<\/p>\n

Where an old version is excluded, ask the supplier to describe the agreed segregation and identification arrangement. Retain that response with the purchase package. Do not claim stock was segregated or destroyed without records establishing what happened.<\/p>\n

Identify the effective lot<\/h3>\n

For an approved revision, record the first order or production lot to which it applies. Ask how units, cartons and documents will be linked to that lot. This makes later inspection, arrival review and service questions traceable to a defined version rather than to a product name covering several orders.<\/p>\n

8. Send a Supplier Declaration With Specific References<\/h2>\n

Use the following brief after assembling the old purchase package. Replace the bracketed fields and attach the comparison form. It is a request for confirmation, not a declaration that any particular ECOBRIDGE order has changed.<\/p>\n

\n

Subject: Repeat-order comparison \u2014 previous PO [reference], proposed PO [reference]<\/strong><\/p>\n

Please compare the proposed supply of [complete model\/variant and buyer SKU] with baseline package [identifier\/date] for the previous order. Confirm each row as unchanged, proposed change or not yet confirmed, citing the exact reference reviewed.<\/p>\n

Identify changes to construction, components, supplied items, finish, labels, manual, artwork, packing, quantity basis and offer scope. For each proposed change, provide the reason, affected references, effective lot and evidence needed for approval. Do not incorporate a prior one-lot concession without identifying it.<\/p>\n

For Model 6001, please reconcile the catalog entry PCS\/CTN: 10 with the working-sheet field Number of boxes: 18PCS. Confirm what the working-sheet quantity counts, which specification applied to the old PO and which packing specification is proposed now. This discrepancy alone does not establish a change history.<\/p>\n

Please return the current signed configuration and packing specifications, quotation revision, approved print-file list, remaining old-stock statement and supplier acknowledgement. Keep unresolved items visible with their owner and proposed closure date.<\/p>\n

The buyer will record approved revisions and open conditions in the new purchase package before releasing the affected requirements. Please acknowledge the comparison scope and references by [date].<\/p>\n<\/blockquote>\n

9. Keep a Repeat-Order Approval Record<\/h2>\n

The final record should identify the old PO, new PO, baseline package, comparison-form revision, supplier declaration and buyer approvers. List the final configuration, packing and print references rather than storing only a short approval email.<\/p>\n

For each approved difference, retain its decision, supporting evidence and effective lot. For any permitted open condition, identify the affected activity, responsible person, required closure evidence and release authority. An open point should remain visible until its stated condition is satisfied.<\/p>\n

Use the quotation comparison worksheet<\/a> when the new offer changes scope. That comparison supports the commercial decision; it does not replace technical review or resolve the packing record by itself.<\/p>\n

Common Repeat-Order Mistakes<\/h2>\n