Candle Wholesale Website Line Sheets: SKU Variants And Version Control
For candle makers who need the website, downloadable line sheet, and wholesale inquiry route to reflect the same approved product details.
Keep one owner-approved register for every sellable candle variant, then use it to check the live wholesale page, downloadable PDF, and inquiry route before each release. Record the approved scent name, vessel, size, SKU, owner-supplied price and case-pack details, availability wording, and version date. Hold publication until unclear or missing facts are confirmed. An inquiry is not a confirmed order.
- Compare the existing wholesale page and linked PDF before editing either one.
- Keep one owner-approved record for every sellable candle scent, vessel, size, and SKU.
- Hold a release if buyer-facing facts are missing, unclear, or inconsistent.
- Test the page, download, and wholesale contact route together before approval.
Open your current wholesale page and its linked line sheet as a stockist would. Pick one sellable candle and compare its scent name, vessel, size, SKU, and owner-approved pack details across both formats. Then follow the wholesale contact link and confirm that it reaches the intended destination. This check can reveal a stale PDF, a changed vessel description, or a route that sends buyers somewhere unexpected. Before changing anything, identify the register and person authorized to confirm the product facts. That record should control the next update.
What Should You Check On The Existing Wholesale Page?
Start with the page stockists already reach from your site navigation, footer, or product menu. Open its linked PDF and choose one current sellable variant. Compare the public scent name, vessel, size, SKU, price or case-pack details supplied by the owner, and availability wording. Write down the exact mismatch instead of correcting either version from memory.
Then follow the wholesale inquiry link. Check its label and destination, and confirm with the person responsible for wholesale that it reaches the intended contact. A buyer may ask about a product or availability there. That message remains an inquiry, not an approved account, confirmed order, or payment.
If nobody can identify which product record is current, pause the public edit. Ask the person authorized to approve the line to resolve the facts first. A website update cannot decide whether a vessel change creates a new sellable variant or whether an old scent is still available.
What Belongs In A Candle Wholesale SKU Register?
Use one entry for each owner-confirmed sellable variant. A candle in two sizes may need a separate entry for each size; a different vessel needs its own entry if the owner sells it as a distinct item. Record the approved SKU for each variant rather than deriving one from an internal production code.
Keep the register usable as the source for both the web page and PDF. Include a source or approval reference and the date or version of that approval. Leave commercial fields blank when the owner has not confirmed them. Do not copy a price or pack count from an older file simply because it looks plausible.
| Sellable variant | Public scent, vessel, and size | Owner-confirmed SKU | Owner-supplied price and case pack | Availability, approved source, and date/version |
|---|---|---|---|---|
| Current scent, first size | Enter the approved public name, vessel, and size | Enter the confirmed SKU for this variant | Leave blank until supplied and approved | Record approved availability wording, source, and date/version |
| Same scent, another size | Repeat the approved name and vessel; identify this size | Enter the SKU confirmed for this sellable variant | Leave blank until supplied and approved | Record the owner-approved status, source, and date/version |
| Same size, different vessel | Enter the public name, distinct vessel, and size | Confirm whether the owner assigns a separate SKU | Leave blank until supplied and approved | Hold unclear sellable status; record approval and date/version |
| Retired or uncertain variant | Use only the owner-confirmed public name and details | Record the confirmed retired SKU or removal decision | Do not carry forward terms without approval | Remove or use explicitly approved status; record source and date/version |
- Inspect
Compare one current sellable candle across the existing page, linked PDF, and inquiry route.
- Approve
Confirm the SKU register, buyer-facing terms, version rule, and intended wholesale destination.
- Update
Scope the owned-site page and file changes, confirming upload and route dependencies separately.
- Release
Test both formats and the inquiry path, then record owner approval and the release date.
How Do You Decide Whether A Release Is Ready?
The register defines the approved facts. A separate release record checks whether those facts made it onto the live page and the linked PDF, and whether the inquiry route still works. It is an audit, not another product catalog.
For every required field, compare the approved value with what a buyer can see in each format. A missing value is not a pass. If a price, case-pack detail, availability status, or SKU is unclear, mark the release for clarification rather than treating the blank or disagreement as approved. The release is ready only when all required buyer-facing facts have an approved value, the page and file match those values, and the intended contact route is confirmed.
| Release check | Approved register | Live page and PDF | Discrepancy owner | Release decision |
|---|---|---|---|---|
| SKU, scent, vessel, and size | Required facts confirmed for every sellable variant | Compare every buyer-facing entry in both formats | Assign unclear or mismatched variants to the approving owner | Ready only when all published variants match; otherwise hold |
| Price and case-pack details | Owner-supplied terms confirmed, or intentionally left unpublished | Check that neither version shows stale or estimated terms | Ask the authorized owner to resolve missing or conflicting terms | Ready only with approved values or an approved decision not to publish |
| Availability and retired items | Current status and wording approved | Check the page and PDF for conflicting or outdated status | Assign uncertain status to the person who controls the line | Hold until unclear status is resolved in both formats |
| Version date and file link | Release date or version rule recorded | Check visible dates and confirm the page links to the intended file | Assign a correction if the date or file is wrong | Ready when the same approved release is identified |
| Wholesale inquiry route | Intended contact and permitted test method confirmed | Check the page and PDF instructions and test the agreed route | Confirm with the intended recipient that the test reached them | Ready only when the destination is correct and receipt is confirmed |
Should You Edit The Line Sheet Yourself Or Get Managed Help?
If the approved register is already disciplined and the change is a simple copy edit you can safely make, an owner edit may be enough. Keep a dated release record and repeat the page, PDF, and contact checks yourself. Managed website help is a better fit when both formats need implementation, file updates need a scoped process, or you want ongoing help maintaining the release.
Storebox can scope an owned-site wholesale page edit, downloadable-file update, and inquiry-path checks. Before work begins, share the live page and current PDF, the approved SKU register, the release-date rule, the intended wholesale destination, and the person who will approve buyer-facing details. Confirm permission to update published files. Hosting, uploads, redirects, form behavior, and third-party integrations need separate scope confirmation.
Keep the page useful as HTML as well as linking to a PDF. Google’s SEO Starter Guide recommends useful, clearly organized content for people. It does not validate your product facts or promise search visibility. For a scoped conversation, use Discuss your website with Storebox. Only the proposal is free; website work and file handling are scoped separately. You can review small-business website management if recurring edits are part of the need.
What Does A Practical Update And Approval Test Look Like?
Illustrative example: The live wholesale page and linked PDF give different vessel descriptions for one current SKU. The owner checks the approved register and confirms which description is correct. The update is then scoped for both formats, the download and inquiry route are tested, and the owner approves a newly dated release. This is a hypothetical workflow, not a client result or a claim about buyer response.
Before release, compare every buyer-facing field on the live page and linked PDF against the same owner-approved register. Verify the version date and file link. Open the download on mobile and desktop. Test the wholesale contact route using a permitted method agreed in advance, then ask the intended recipient to confirm receipt. The owner approves the page, file, and route together.
A release can pass these checks even if no buyer has inquired yet. Do not treat a download, contact-button click, or test message as a qualified wholesale inquiry. Keep the test record with the register and the owner’s approval so the next product change has a clear starting point.
How Can You Tell Whether The Current Line Sheet Reached A Buyer?
Keep release testing separate from downstream results. A qualified action is a verified wholesale inquiry that names the current line-sheet version or current SKU/variant set and reaches the correct wholesale contact route. A click or download alone does not qualify.
Confirm the inquiry from records you are permitted to use, and keep the outcome stages distinct: proposal request, qualified owner inquiry, agreed project, and confirmed revenue are not interchangeable. For the candle business, likewise distinguish a wholesale message from account acceptance, an order, and payment. If you compare inquiries over time, use an available prior baseline or begin when the approved version is released. Note assortment, seasonal, and other concurrent changes; the comparison alone cannot show that the line sheet caused an order.
Google’s guidance for AI features in Search says foundational SEO practices still apply and does not require a special AI optimization. Make the variant facts, release date, and contact destination clear for readers. That is useful preparation, not evidence that an AI system cited the page or that a retailer acted on it.
If you need help implementing the approved update, send Storebox your actual website URL and business goal, along with the current wholesale page and PDF URLs, register, release rule, intended inquiry destination, and approver. You can use the verified WhatsApp route to request a proposal. The proposal is free; any page, file, or integration work is scoped separately.
Frequently Asked Questions
What if wholesale prices or case-pack details are not approved?
Leave those fields blank in the working register and do not publish estimates. Ask the authorized owner to confirm the terms for each sellable variant, including whether those details should appear publicly. Add approved values or an approved decision to omit them before the page and PDF are released.
How should a retired candle variant appear in the current release?
Remove it from the current buyer-facing release or use status wording the owner has explicitly approved. Check the live page and PDF together so one format does not imply that the retired scent or size is currently available. Keep the confirmed status in the register for the next update.
Can search engines find a wholesale line-sheet PDF?
Do not assume a PDF is invisible to search engines because of its file type. Keep important variant and contact information clear on the owned page as well as in the approved download, and link the page to the current file. Search discovery is not guaranteed.
How much does a managed line-sheet website update cost?
A fixed price for this specific page and file work is not provided here. The scope may depend on the website, file handling, and any requested form or integration work. Storebox’s plans and current pricing provide current terms; request a proposal to confirm the work and its price. Only the proposal is free.
What should I send when asking for a proposal?
Share your actual website URL and business goal, the current wholesale page and PDF URLs, the approved SKU register and release-date rule, and the intended wholesale inquiry destination. Identify who can approve product details and confirm your permission to change published files. Ask separately whether uploads, hosting, redirects, or form behavior can be included in scope.