CentriPOS has two separate label workflows. Product labels are generated from a saved product’s Labeling & Shipping area and may use configured product templates, category matching, product/variant codes, warranty data, branding, custom fields, and optional scan-time price/callout overrides. Print sale labels uses a fixed sold-item tag design from an existing receipt and excludes returned lines. Neither workflow stores the browser/system printer, media size, margins, or scale. Print one controlled copy and scan it before producing a batch.

Before you beginSearch first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.

Step by step

  1. For a catalog price label, open the exact saved product and its Labeling & Shipping label panel. Confirm parent product, enabled variants, SKU/code assignments, price, brand, warranty, custom fields, category, and tenant branding before choosing a template. Unsaved products cannot print.
  2. Template selection loads only active templates whose source is Product. For a new product/category scope, CentriPOS chooses the first template whose settings categoryIds contains the current category, otherwise the default, otherwise the first alphabetically after default ordering. The Built-in price label appears only when there are no active Product templates.
  3. Changing product or category can recalculate the automatic template choice. A template’s stored width, height, background, design, and horizontal/vertical offsets are used; invalid/nonpositive dimensions fall back to built-in dimensions and offsets are clamped from -1 to +1 inch. Verify the category/template relationship and physical stock size.
  4. Choose Product label for parent-level data, All SKUs for every enabled variant, or one specific enabled variant. The panel defaults to All SKUs but automatically changes to Product label when there are no enabled variants. Disabled variants are never All SKUs targets.
  5. Enter Label pages/copies. The field strips nondigits as typed and blank becomes 1 on blur. At print time parseInt is clamped to at least one. All SKUs multiplies this quantity by the number of enabled variants; confirm the full generated count before accepting the system print dialog.
  6. Understand encoded code priority. Parent label uses its active parent primary-for-label code, then primary-for-scanning, product barcode, another active parent code, then product SKU. A variant uses its active variant primary-for-label code, then primary-for-scanning, first active variant code, variant barcode, target SKU, then the parent fallback. Inspect both human-readable SKU and scannable code.
  7. Leave One-off sale price, Compare at, and Print callout blank for ordinary catalog labels. A valid nonnegative sale override changes printed price; when Compare at is blank it defaults to regular price. Compare at alone and callout text are also treated as overrides. These do not update the product’s stored retail price.
  8. Any sale price, compare-at, or callout causes CentriPOS to add an override-barcode element to the chosen template and create one unique label_scan_overrides database row per physical copy before opening print. Scanning that generated code can reproduce the saved override payload. This is not merely visual print text. Obtain pricing authorization and never use an override label after its intended promotion/context ends.
  9. If creating any override row fails, printing stops. If override rows save but the browser blocks/fails the print window, those unused scan overrides remain stored; do not repeatedly press Print without checking generated override evidence. Ordinary labels with no override do not create those rows.
  10. Product label data can include product/brand, variant attributes, SKU/barcode/code, regular/sale/compare-at price, callout, supplier code, tenant name/logo, product custom fields, and Warranty versus AS IS. Variant attribute inference may fill Comfort and Feel from slash-separated variant names when explicit attributes do not already provide them; inspect the rendered text.
  11. Choose Print once. CentriPOS opens a separate print window from the generated custom-label HTML. If it reports Could not open the print window, allow pop-ups. In the browser/system dialog choose the exact physical printer, label media, orientation, margins, and 100%/intended scale; these are outside CentriPOS and are not remembered reliably across devices/jobs.
  12. Print one product-label test. Confirm template dimensions/offsets, clipping, brand/product/variant, SKU/supplier code, price/compare-at/callout, warranty/AS IS, logo, copy count, and contrast. Scan the code in an authorized test cart and confirm it resolves the exact product/variant and—only for an override code—the intended temporary scan payload. Void/clear the test cart afterward.
  13. For physical sold-item tags, open the exact receipt and choose Print sale labels. This dialog uses the fixed SALE_SOLD_LABEL_TEMPLATE, not the product template selected above or the category/default product-template rules.
  14. Only receipt line_items whose is_return flag is false appear. A returned line is excluded entirely. Every eligible line starts unchecked, while its label quantity initializes to at least one using the sale-line quantity. Select only lines that need tags and review the displayed product/variant, SKU, and line amount.
  15. Change each selected label quantity as needed. The number input shows min 1, and both the counter and print path clamp invalid, zero, or negative values to at least one. The selected label count sums physical copies, not selected receipt lines.
  16. Remarks / notes are print-job notes passed to the sold-label output. They do not update the receipt, line item, customer, fulfillment, or product record. Avoid confidential information and put operational history in the correct receipt/fulfillment notes workflow.
  17. Choose Print labels once. Each selected line produces the requested copies with To: customer name, receipt number, Item: product/variant, Amount Due from the sale’s current balance_due, Date from sale fulfillment_date or today when absent, SKU, and barcode falling back from line barcode to SKU. It does not print the individual line price as Amount Due.
  18. Print one sold-tag test. Confirm the intended customer and receipt, current overall balance due, item/variant, date, SKU/barcode, remarks, physical size, and count. A later payment or fulfillment change does not automatically alter tags already printed; reprint only after destroying/controlling superseded tags.
  19. For either workflow, document product/variant or receipt/line IDs, template ID/name/dimensions, label target, copy count, encoded code, override row/time/creator, printer/media/scale, and error when troubleshooting. Do not compensate for alignment by editing product data or creating duplicate override labels.
  20. No screenshot is published for this guide. The approved Harbor & Hearth capture set has no exact open product-label panel, print window, or Print sale labels dialog. A Products or Receipts list would not demonstrate these controls, so no unrelated screenshot is substituted.

Screen and contract reference

Control or areaWhat it means
Product label workflowSaved Product → Labeling & Shipping custom-label generation.
Active Product templatesOnly active label_templates with template_source product.
Automatic template priorityCategory match, then default, then first; built-in only when none exist.
Template dimensions/offsetsStored size/design/background with safe fallbacks and ±1-inch offset clamp.
Product labelParent-level data and parent code priority.
All SKUsEvery enabled variant times copy quantity.
Specific SKUOne enabled variant target.
Label pagesDigits-only input parsed/clamped to at least one physical copy per target.
Code priorityPrimary-for-label, primary-for-scanning, active/barcode/SKU fallbacks scoped to parent or variant.
One-off sale priceNonnegative scan/print override, not product retail-price edit.
Compare atExplicit comparison price or regular-price fallback when sale override exists.
Print calloutOverride text that also triggers an override scan code.
label_scan_overridesOne unique persisted override row per physical override-label copy.
Override partial stateRows can remain when print-window opening later fails.
Warranty / AS ISDerived from product warranty label/path/URL for supported product templates.
Browser print windowExternal printer/media/margin/scale selection; pop-ups required.
Print sale labelsReceipt-specific fixed sold-item template, separate from Product templates.
Returned-line exclusionSale lines with is_return true do not appear.
Unchecked defaultsEvery eligible receipt line starts unselected.
Receipt-line quantity defaultInitial copies equal at least one sale quantity.
Selected label countSum of requested copies for checked lines.
Sold-label Amount DueCurrent whole-sale balance_due, not individual line price.
Sold-label dateSale fulfillment_date or current local date fallback.
Sold-label barcodeLine barcode then SKU fallback.
Remarks / notesPrint-job-only notes; no receipt/product mutation.
No public screenshotNo exact approved label-panel/dialog/print capture; no substitute.

Expected result

The exact product/variant or receipt/line targets, active template and category/default selection, dimensions/offsets, human identity, encoded code priority, price/compare-at/callout or sold-tag data, warranty state, copy count, and physical printer/media/scale are verified on a controlled test; any persisted scan-override row remains authorized and maps only to its intended temporary payload.

Troubleshooting

  • Confirm whether you are editing a product, variant, shared master record, or location-specific value.
  • Search for an existing product, SKU, UPC, attribute, or tag before creating a duplicate.
  • Preview labels, pricing, and availability in the intended location before broad publication.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.