Public Receipt and Public Fulfillment Slip are different unauthenticated bearer-link applications. Anyone with a working token can view the returned content; forwarding, browser history, clipboard sync, QR scans, email/SMS, screenshots, PDFs, and support tools can spread it. Use only `https://pos.getcentri.com` customer links. Never send Supabase, Edge Function, storage, or other service URLs. The receipt route sets a strict noindex/nofollow meta policy; the current fulfillment-slip component does not set that policy itself, so do not rely on search-engine exclusion as access control. No safe exact Harbor & Hearth customer-document screenshot is approved.

Before you beginUse only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.

Step by step

  1. In CentriPOS, open the exact sale or fulfillment record and choose its customer-link action. Read the share-dialog title: Receipt Link is the financial receipt; Fulfillment Slip is the merchandise handoff/acknowledgement document. Do not choose by visual similarity or reuse a URL from another sale.
  2. Confirm the sale/receipt number and the dialog’s Receipt Total, Cart Total, Refund, or Fulfillment slip badge. Preview with Open link in new tab before sending. Opening the share dialog can copy the link to the clipboard automatically, so use a private trusted browser/clipboard environment.
  3. Use only the branded link generated for this exact document. New financial receipt links use a tenant-specific receipt path; older /r/<token> links may redirect to a verified canonical receipt path. Fulfillment slips use their own generated fulfillment path. Do not edit the path, move tokens between document types, or construct a URL from an invoice or customer ID. Signed invoice/account-statement links are a separate workflow covered in Open an invoice or account statement.
  4. Treat the token as the authorization. The public page does not ask the customer to sign in to a Centri Account. Send it only to the intended recipient through Text Link, Email Link, controlled QR, or another approved channel. Verify consent and recipient separately.
  5. On the customer document, confirm store identity, document number, date, location details and whether it says Receipt or Invoice. The receipt application can also render an invoice copy and show outstanding, paid, or failed-payment information when returned for that document. An invoice preview is not payment proof.
  6. Review Fulfillment on the receipt when the sale is pickup, local delivery, or shipping. It can show fulfillment type/status, delivery address, and delivery phone. Carry out and none do not show this customer-fulfillment block. These details are sensitive delivery data.
  7. Review merchandise rows. Zero-quantity lines are hidden. Lines recognized as delivery/shipping/fulfillment charges or SKU `FULFILLMENT-FEE` are removed from the item table and summarized separately as a fulfillment fee. Item rows can show product, variant, SKU, quantity, line total, and template-controlled line discount detail.
  8. Reconcile the receipt totals: merchandise subtotal excludes detected fulfillment-fee lines; fulfillment fee, Discounts, Tax, separate Cash rounding adjustment/discount, Total, Paid, each payment, and Amount/Balance due appear when applicable. Template labels can rename subtotal, tax, total, and amount due.
  9. Understand payment disclosure. Every payment row can show method and amount. CentriPay Cloud can also show processor transaction/reference/receipt ID, authorization code, card brand, and last four digits parsed from stored fields or nested terminal response. Confirm this disclosure matches receipt/privacy policy before sharing.
  10. Review Store policies when present. The page selects returned policy_html or template policies_html, sanitizes it with DOMPurify, and renders supported rich text/images/links. Confirm the current legal text and external link destinations; sanitized display does not make incorrect policy wording valid.
  11. Choose the displayed Download receipt PDF or Download invoice PDF action. It keeps the generated document’s receipt scope and bearer token in the branded PDF route. Inspect the downloaded document independently; a saved or forwarded file can outlive access to the browser link.
  12. Read the exact unavailable message. This link has expired / Fresh link required appears only when the service identifies the link as expired. Other unavailable, forbidden, missing, rate-limited, invalid, or service-error cases can show Receipt unavailable / Please try again. The customer page does not prove the underlying cause; authorized staff should inspect the source record.
  13. For an unavailable receipt, ask authorized staff to inspect the exact sale and generate/resend a supported fresh link. Do not alter token characters, send an internal endpoint, disable protection, or repeatedly request a rate-limited link. Verify the new recipient and preview again.
  14. If an invoice copy says Your balance is still due after a failed payment, verify the displayed invoice, attempted method and balance. Use its offered secure payment or contact-the-store path only after the prior processor attempt is resolved. A displayed retry action is not a reason to submit duplicate payments.
  15. On a Public Fulfillment Slip, verify store logo/name, sale number, Customer name and optional phone, fulfillment method/date, location name/address/phone/email, optional Served by identity, and every item’s product name, variant, SKU, note, and quantity. Payment method, price, tax, total, paid, and balance are intentionally absent from this UI.
  16. Choose Download PDF to open `/fulfillment-slip-pdf/<same token>`. Inspect that it remains payment-free and contains only the intended customer, location, fulfillment, item, note, and acknowledgement information. Treat item notes and staff/customer contact details as sensitive.
  17. If the fulfillment GET fails or returns no data, the page says “This fulfillment slip is unavailable.” Unlike the receipt’s branded expired context, this screen does not distinguish expired, revoked, unauthorized, missing, rate-limited, or service failure. Staff must inspect the source record/service rather than guessing.
  18. When acknowledgement is required and the slip is not already signed, the intended customer chooses Sign. The contained signature pad states that the customer acknowledges pickup or receipt of fulfilled merchandise. The capture posts the data-URL signature plus capture mode (default onscreen) and optional device information using the same bearer token.
  19. Before capture, confirm the actual customer/authorized recipient, merchandise, quantities, condition, handoff method/date, and business signature policy. A signature is sensitive evidence and is not identity proof by itself. Do not ask an uninvolved employee to sign merely to clear the workflow.
  20. After capture, wait for Signature saved. The page closes the pad, refetches the slip, changes to Signed, and displays the stored signature image. The public screen does not show signer name, signed timestamp, IP, explicit consent checkbox, or an undo/replace control. Verify richer audit metadata in the authorized CentriPOS fulfillment record if required.
  21. If signature save fails, keep the customer on the slip, preserve the real-world handoff evidence, and contact authorized staff. Do not capture repeatedly until duplicates/overwrites are understood. A bearer-token holder can reach the signature workflow, so revoke/replace the link under approved procedures after suspected exposure.
  22. Return to CentriPOS and verify the exact sale/fulfillment record, public-link state, signature image/source/timestamp or other supported audit evidence, send/log result, receipt/PDF, and fulfillment status. The public page itself does not complete delivery, settle payment, move inventory, or prove a communication log saved.
  23. Keep the general support knowledge base indexable while keeping customer transaction documents private. The Public Receipt explicitly sets `noindex,nofollow,noarchive,nosnippet,noimageindex`; because the current Fulfillment Slip component lacks an equivalent meta update, escalate that as an indexing/privacy gap rather than representing the bearer token as SEO protection.
  24. No screenshot is published. The approved Amelia Grant Harbor & Hearth capture set contains no safe exact public receipt or fulfillment-slip document; publishing a live demo transaction token, customer/delivery details, signature, payment identifiers, or a substituted screen would violate the evidence/privacy standard.

Screen and contract reference

Control or areaWhat it means
Receipt LinkUnauthenticated bearer page with financial sale, item, fulfillment, payment, total, balance, policy, and PDF details.
Fulfillment SlipUnauthenticated bearer page focused on customer, fulfillment, items, notes, acknowledgement, and PDF without payment totals.
pos.getcentri.comOnly approved customer-visible link host.
Receipt prefix`/r/` or supported tenant-scoped receipt path returned by link generation.
Fulfillment prefix`/f/` for public fulfillment slips.
TokenLowercase hexadecimal 20–64 character bearer secret; possession can grant document access.
No Centri Account sign-inPublic document authorization is the token, not customer authentication.
Receipt robots policynoindex, nofollow, noarchive, nosnippet, and noimageindex set by Public Receipt.
Fulfillment robots gapCurrent Public Fulfillment Slip component does not set an equivalent robots meta policy.
Logo paletteReceipt attempts to derive primary/secondary colors from the store logo, with fallback colors.
Fulfillment blockType/status and optional delivery address/phone for non-carry-out customer fulfillment.
Visible merchandiseNonzero-quantity lines excluding detected fulfillment-charge items.
Fulfillment feeDetected charge lines summarized outside merchandise subtotal.
Line discount detailShown only when the selected receipt template enables it.
Payment detailMethod/amount; CentriPay Cloud can also expose transaction ID, authorization code, brand, and last four.
Store policiesSanitized returned/template rich HTML.
Receipt Download PDF`/receipt-pdf/<token>` using the same bearer authorization.
Expired receipt experience410 contextual or generic 404/403/429/failure presentation; wording does not prove cause.
Fulfillment customer detailsName/phone plus location and optional served-by identity.
Item notesPublic on fulfillment slip and potentially sensitive.
Fulfillment Download PDF`/fulfillment-slip-pdf/<token>` with payment-free intent.
SignOpens contained acknowledgement signature pad when no signature exists.
Signature payloadData URL, capture mode, and optional device information posted with the bearer token.
SignedStored signature image exists; public page does not show signer identity/time or undo.
Unavailable slipGeneric GET failure/no-data state with no cause distinction.
No public screenshotNo exact privacy-safe Harbor & Hearth public document capture exists.

Expected result

The intended recipient receives only the branded pos.getcentri.com bearer URL for the exact sale and document type; receipt financial/payment disclosures or payment-free fulfillment details reconcile to source records and matched PDFs, unavailable states are not overdiagnosed, signature evidence is verified in CentriPOS, no internal service URL is shared, and customer-document indexing/privacy gaps are explicitly controlled rather than relying on token obscurity.

Troubleshooting

  • Use only branded pos.getcentri.com links supplied by CentriPOS.
  • Confirm the merchant, customer-safe reference, and intended recipient before continuing.
  • Ask the merchant for a new link if the page says it is unavailable or expired.

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.