{
  "product": "CentriSoft",
  "audience": "customer",
  "canonicalHost": "https://platform.getcentri.com",
  "articleCount": 218,
  "referenceCount": 0,
  "references": [],
  "articles": [
    {
      "slug": "quick-biller",
      "url": "https://platform.getcentri.com/centripos/quick-biller",
      "title": "Build an itemized payment in Money",
      "summary": "Use Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Money",
      "introduction": "Money → Take payment uses a quick billing workspace built on the register. It can add ordinary products or one-time description lines to an itemized receipt. A service estimate is a separate mode and must not be mistaken for a collected payment.",
      "beforeYouBegin": "Confirm the business and location and use an authorized selling role. Check whether your operating mode requires an open payment session. Do not continue another person’s active selling tab or treat an unconfirmed electronic result as permission to collect again.",
      "steps": [
        "Open Money → Take payment. If prompted, choose the intended location. Wait for the operating mode and workspace to load; use the original active selling tab when this device already has a Sell screen for the same register.",
        "Choose Amount & description for a one-time line, or Products for existing catalog items. Switching entry views changes how you add lines; it does not make a second receipt or collect money.",
        "For Amount & description, enter Description, Unit amount and a positive whole-number Quantity, then choose Add line. The line remains on this receipt; it does not create a reusable inventory product. Repeat for an itemized charge rather than putting several unrelated services into an unexplained total.",
        "For Products, search and choose the correct services or materials, then review quantities, prices, applicable tax and fulfillment. Use normal product and cart controls rather than entering a one-time line to bypass a configured catalog price or restriction.",
        "Attach the intended customer and review the complete itemized receipt, location, tax, discounts and any required accounting fields before taking payment. Supported tax and payment choices follow the selected location and payment station.",
        "If Payment session is shown or the workflow requires a manually opened service session, open the correct session before collecting. Cash, check and manually recorded tenders require an open register session. A closed-register electronic workflow is limited to its supported verified payment path.",
        "Open the payment screen and use only an enabled, authorized tender. Review any split amounts and remaining balance, then follow the secure card, bank, saved-method or reference prompts that are actually available. Preparing the receipt or opening the payment screen is not payment proof.",
        "Complete the sale once and confirm the saved receipt and payment evidence. Keep an approved but unfinished receipt under its original recovery path; do not add another charge because a save or network response was interrupted.",
        "If you entered from Service → Jobs in estimate mode, read Build this estimate or New job estimate. Choose services/materials and the customer, then save the estimate for review. An estimate is not a completed sale or collected payment; use Back to return to its service context.",
        "Use the Money navigation for Invoices, Payments or Receipts when reviewing the resulting record. Confirm the actual reference and status rather than assuming that switching sections completed or sent anything."
      ],
      "controls": [
        {
          "name": "Products",
          "description": "Adds supported existing catalog items to the current receipt."
        },
        {
          "name": "Amount & description",
          "description": "Adds one-time itemized lines to this receipt."
        },
        {
          "name": "Description / Unit amount / Quantity / Add line",
          "description": "Required line identity, price, positive whole-number quantity and explicit add action."
        },
        {
          "name": "Payment session",
          "description": "Opens the supported manual session where the operating mode requires one."
        },
        {
          "name": "Build this estimate / New job estimate",
          "description": "Service-estimate context; not evidence of payment."
        },
        {
          "name": "Money sections",
          "description": "Take payment, Virtual Terminal, Invoices, Payments and Receipts are separate views of the workflow."
        }
      ],
      "expectedResult": "The intended customer’s receipt contains the reviewed catalog or one-time lines, and any completed payment is recorded once through an allowed session and tender. An estimate remains distinguishable from payment and completed-sale evidence.",
      "troubleshooting": [
        "If Add line is unavailable, check that Description is nonblank, Unit amount is positive and Quantity is a positive whole number within the shown limits.",
        "If cash or a manually recorded tender is refused, open the correct register session rather than disguising it as an electronic payment.",
        "If Sell screen already open appears, return to the original tab. Use take-over only when the original workspace is no longer in use and you understand which pending work it owns.",
        "If the receipt or payment needs review, preserve its original context and safe reference. Do not clear the cart, switch business or start another payment to work around an uncertain outcome."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "virtual-terminal",
      "url": "https://platform.getcentri.com/centripos/virtual-terminal",
      "title": "Take a one-time payment in Virtual Terminal",
      "summary": "Review 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.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Virtual Terminal",
      "introduction": "Virtual Terminal is a focused one-time payment screen. It is separate from a physical card terminal and from the itemized Quick Biller. Card, bank and card-authorization choices appear only for the assigned checkout that supports them.",
      "beforeYouBegin": "Use an authorized selling role and the intended business, location and register/payment station. Confirm the payment is approved by the customer and that the register, tax configuration, currency and gateway are ready. Never use real card details or submit a real charge as a documentation test.",
      "steps": [
        "Open Payments → Virtual Terminal or Money → Virtual Terminal. Both use the same focused screen. If prompted, choose the intended location and register; return to the original station when recovering a saved receipt.",
        "Wait for the selected register, payment permissions, assigned checkout and tax rate to be verified. This screen requires an internet connection and a supported US-dollar checkout. A blocked or unavailable assigned checkout must be resolved for that station, not redirected to another merchant.",
        "Open the register or payment session when the screen requires it. Some specifically supported always-on service stations can work without a manually opened session; do not assume that behavior applies to every account or bank/card combination.",
        "Enter Sale amount as the amount before sales tax, up to the supported limit shown by validation. Review Apply sales tax and its assigned rate. Only authorized tax managers can change the tax choice; a tax-exempt contact or a customer-address calculation can change the displayed requirement.",
        "Add an optional Description and attach the correct Contact when needed. If tax requires a customer address, use a contact with a complete state and ZIP code. Keep card/account credentials out of descriptions, customer notes and support messages.",
        "If Payment action is available, choose Charge now or Authorize card deliberately. Authorization places a hold for later capture or cancellation from the receipt; it is not the same as a completed charge. Do not infer authorization or bank availability from the page title.",
        "Review Subtotal, Sales tax and Sale total or Total to charge. Continue to card entry, Continue to payment or Continue to authorization opens the assigned secure entry. For supported card-fee workflows, review the final payment amount and fee with the customer before submission.",
        "Enter payment details only in the supported secure checkout fields and follow its review and authentication prompts. Use the permitted card or bank method for that assigned checkout. Do not type payment credentials into the ordinary amount/description form.",
        "After submission, keep the original receipt and payment attempt together. If the screen asks for receipt review, status recovery or a return to the original register, inspect that result before another payment. An interruption is not a confirmed decline.",
        "When payment is approved, allow the receipt to save. If Payment approved. Save the receipt to finish appears, use Save receipt to complete the original record; do not charge again. Verify the completed receipt and its payment reference before starting another payment.",
        "After a card authorization, follow the original receipt to capture or cancel it when authorized. Do not create a new sale merely because an authorization is not a completed-payment receipt.",
        "Use Edit payment details only when the saved draft is still eligible and no payment evidence blocks editing. If the screen cannot establish that the prior attempt is clear, preserve the receipt for review. Finish the receipt dialog before entering a fresh amount."
      ],
      "controls": [
        {
          "name": "Sale amount",
          "description": "One-time amount before applicable sales tax."
        },
        {
          "name": "Apply sales tax",
          "description": "Uses the assigned, verified tax context; editing is permission-controlled."
        },
        {
          "name": "Description / Contact",
          "description": "Optional receipt context; neither is a place for payment credentials."
        },
        {
          "name": "Payment action",
          "description": "Charge now or supported card authorization, when available."
        },
        {
          "name": "Continue to payment/card entry/authorization",
          "description": "Opens the assigned secure checkout; it does not by itself confirm payment."
        },
        {
          "name": "Edit payment details",
          "description": "Available only when the original draft has no blocking payment evidence."
        },
        {
          "name": "Save receipt",
          "description": "Completes the original approved payment record if automatic saving needs recovery."
        }
      ],
      "expectedResult": "One authorized payment or card authorization remains tied to the intended station and original receipt, with verified tax and provider result. Approved money is not submitted twice because receipt saving or confirmation was interrupted.",
      "troubleshooting": [
        "If Access restricted appears, ask an administrator to review the selling role. Do not borrow another user’s credentials.",
        "If register, tax, currency or checkout verification fails, stop at that message and review the selected station and approved configuration. Do not switch merchants or turn off a tax rule to force payment.",
        "If an outcome is uncertain, retain the original receipt and safe payment reference, and follow its status/review path. Retry only after a confirmed decline or an explicitly permitted recovery.",
        "If an approved payment has not finished saving, preserve it and complete the original receipt. A blank or locked amount form is not permission to create another payable sale."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "booking-payments-accrual",
      "url": "https://platform.getcentri.com/centripos/booking-payments-accrual",
      "title": "Review booking payments, refunds and earned care",
      "summary": "Keep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Booking accounting",
      "introduction": "Booking payments cover completed services first; money paid ahead remains with the stay until used or refunded. Confirmed provider results, service completion and accounting balances must be read separately.",
      "beforeYouBegin": "Confirm the business, property, booking reference, currency and demo/live mode. Use an approved finance role for financial review, and an owner or manager for refunds. Do not submit a payment, refund, cancellation or accounting action merely to learn how the screen works.",
      "steps": [
        "Open the saved stay and compare its Booking total, recorded payments, package coverage and remaining balance. Read each payment’s status and reference; a saved reservation or payment prompt is not evidence of money received.",
        "In Payments & refunds, distinguish the amount received from unused payment available for refund. Do not count the same payment again as new money when applying it to a completed service or reading the accounting details.",
        "Use Nightly care & services to mark actual care completed only after the service date has arrived and the care has been provided. This updates earned-care reporting; it does not charge the customer or create a second payment.",
        "In Activity & accounting details, read Recorded net cash, Advance liability and Earned unpaid A/R separately. When authorized, Apply advance to earned charges uses recorded unused money against earned charges; it is not a new tender.",
        "If a stay must be cancelled, choose Cancel booking and review the saved cancellation assessment, recorded payments, cancellation fee and refundable amount. Confirm the reviewed terms before Confirm cancellation. Cancelling a stay does not itself prove a refund.",
        "After cancellation, an authorized owner or manager can use Review refund where the saved configuration and original provider support it. Review the amount and original payment method, then submit once only with the required approval. A refund does not reverse services that were already completed.",
        "If the refund is awaiting confirmation, use Refresh recorded status for the original result. The screen blocks another refund while one is unresolved. Do not switch payment references or create a replacement refund to bypass that state.",
        "Open Accrual report for the same property and mode. Choose Period start, Period end and Balances as of. The period end cannot precede its start, and the as-of date must be on or after the period end.",
        "Choose Run accrual report and compare Earned revenue · period, Cash receipts · period and Cash refunds · period with Unused advance payments · as of and Earned charges still unpaid · as of. Period activity and ending balances answer different questions.",
        "Open the earned-revenue drilldown and the original booking when a total needs explanation. Match service dates, completed-care entries, cancellation fees and recorded cash/refunds without counting a shared figure more than once.",
        "Use Journal evidence to inspect effective date, entry, amount and recorded time. Keep the original evidence when escalating a mismatch; do not edit a stay’s history or mark care completed merely to make a report balance.",
        "Treat the accrual report as booking-care evidence, not a complete profit-and-loss statement. Expenses, taxes and broader accounting reconciliation must be reviewed separately before making financial conclusions."
      ],
      "controls": [
        {
          "name": "Payments & refunds",
          "description": "Recorded payment and refund evidence for the selected stay."
        },
        {
          "name": "Review refund",
          "description": "Permitted review of unused payment to the original method after cancellation."
        },
        {
          "name": "Refresh recorded status",
          "description": "Checks an existing unresolved result instead of sending another refund."
        },
        {
          "name": "Mark completed",
          "description": "Records actual service delivery and earned care, separately from money received."
        },
        {
          "name": "Activity & accounting details",
          "description": "Recorded cash, advances and earned receivables."
        },
        {
          "name": "Accrual report",
          "description": "Period activity alongside separately dated ending balances."
        },
        {
          "name": "Journal evidence",
          "description": "Effective and recorded dates for saved booking accounting entries."
        }
      ],
      "expectedResult": "The booking’s payment, earned-care, advance, receivable, cancellation and refund records explain the report without duplicate financial actions. An unresolved provider result remains under review rather than being represented as confirmed money.",
      "troubleshooting": [
        "If a refund control is missing, check cancellation status, saved configuration, provider support and your role. Do not post a substitute negative payment.",
        "If provider confirmation is pending or the response was interrupted, preserve the original booking/payment reference and refresh its recorded status before any further financial action.",
        "If report totals differ, confirm property, currency, demo/live mode, date period, as-of date and service completion evidence. Changing only the report dates is not a reconciliation.",
        "If the stay has a payment or fee but lacks the saved terms needed for cancellation, stop and ask the accounting owner to review the original evidence rather than forcing the lifecycle change."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "booking-settings-publishing",
      "url": "https://platform.getcentri.com/centripos/booking-settings-publishing",
      "title": "Configure booking properties and customer pages",
      "summary": "Set accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Booking setup",
      "introduction": "Property settings, Rooms & kennels, Setup and Publishing control different parts of the booking experience. New reservations use saved configuration; existing visits retain the terms captured when they were created.",
      "beforeYouBegin": "Use an authorized owner or manager account for the intended business, location and property. Record current settings and confirm demo versus live mode before changing availability, rates, intake, terms or publication. Configuration work can affect real customer reservations.",
      "steps": [
        "Open Events → Bookings, choose the data mode and property, and read its timezone and currency. If no property exists, an authorized owner or manager can choose Set up property. Confirm name, location, public slug, timezone, demo status and enabled state before saving.",
        "Open Rooms & kennels to review accommodations. Add accommodation or Edit accommodation only with approved operational details: Name, Type, Capacity, Base rate and Additional guest rate. A room, suite, kennel/run or daycare capacity pool must represent the intended bookable resource.",
        "Choose Available, Maintenance or Inactive deliberately. These controls change saved accommodation availability immediately; closing a different editor does not undo an availability selection.",
        "Open Setup and Services. Review each package’s name and stable code, Overnight boarding or Daycare day service unit, customer-bookable switch, eligible accommodations, rates and description. Blank package rates can use the accommodation rate; confirm the actual result before sharing a price.",
        "For add-ons, review the amount per service unit, whether to charge for each pet, and whether the option is included automatically. Review regular-price and savings labels separately from the payable price; a displayed savings label must accurately describe the approved package.",
        "In Booking page, review the logo image address, welcome heading/message, policy version and full policy text. Customer-facing content and image addresses must be approved for this business.",
        "In Questions & files, choose vaccination-date and emergency-contact requirements, required document types, whether staff review is required before check-in, and whether expiry must cover the entire visit. Add required intake questions with clear answer types and stable question codes.",
        "In Availability, review arrival, departure and daycare days/time windows, lead time and stay limits, and unavailable date ranges. All booking times follow the property timezone. Check the complete requested stay, not only the arrival day.",
        "In Payment & terms, choose the amount due at booking: Full booking amount, Percentage deposit or Fixed deposit. Review free-cancellation notice and any late cancellation fee method and amount. These terms describe the booking’s policy; payment availability still requires its own enabled provider.",
        "Choose Save booking setup once, wait for Booking setup saved, and reopen the sections to verify the saved values. If another edit changed the configuration, refresh and review the current version rather than overwriting terms blindly.",
        "Open Publishing and check Customer booking page and its Enabled or Not published state. Use Copy booking link for the generated branded page. Preview this property’s embed before asking customers to use an embedded version.",
        "If embedding is approved, configure the exact Approved website origins in Setup, then use Copy embed snippet on the approved site. Copying a snippet does not install it. WordPress packaging and client-site installation are not performed by this screen.",
        "Run an approved demo booking through the chosen package, dates, available accommodation, intake and review steps. Keep demo evidence separate from live readiness and confirm the account’s payment setup independently before accepting real customer payments."
      ],
      "controls": [
        {
          "name": "Property settings",
          "description": "Property identity, location, timezone, data mode and enabled state."
        },
        {
          "name": "Rooms & kennels",
          "description": "Accommodation capacity, approved rates and availability state."
        },
        {
          "name": "Services",
          "description": "Packages, allowed accommodations, payable rates and add-ons."
        },
        {
          "name": "Booking page",
          "description": "Welcome content, policy text/version and approved embed origins."
        },
        {
          "name": "Questions & files",
          "description": "Intake answers, document types, expiry and review requirements."
        },
        {
          "name": "Availability",
          "description": "Days, time windows, lead time, length limits and blackout ranges."
        },
        {
          "name": "Payment & terms",
          "description": "Booking amount due and cancellation policy; not proof of provider activation."
        },
        {
          "name": "Publishing",
          "description": "Generated branded link, embed snippet and preview."
        }
      ],
      "expectedResult": "New reservations use the reviewed property, package, availability, intake and terms. The intended branded page is shared or embedded only after approved configuration and a separate payment-readiness check; saved visits retain their own agreed terms.",
      "troubleshooting": [
        "If Setup is missing, check the selected property and your role. Ordinary booking access does not grant settings or refund authority.",
        "If saving reports a conflict or invalid value, refresh the current configuration, correct the specific field and review the complete result. Do not recreate the property to avoid a version conflict.",
        "If an embed is refused, check the exact approved website origin and property before changing publication settings. Do not weaken origin restrictions or paste private owner links into public embed code.",
        "If a package is unavailable, check its customer-bookable switch, service unit, eligible accommodations, dates, pet count and full-stay availability rather than changing a price to force acceptance."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "hospitality-bookings",
      "url": "https://platform.getcentri.com/centripos/hospitality-bookings",
      "title": "Manage saved bookings and pet stays",
      "summary": "Choose the correct booking property and data mode, save an available stay for the right owner and pets, and follow policy, readiness, arrival and departure status.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Bookings",
      "introduction": "Bookings keeps accommodation, owner, pets, agreed terms and care together. Demo bookings and Live bookings are separate data modes. A saved stay, accepted policy, completed service and confirmed payment are different pieces of evidence.",
      "beforeYouBegin": "Sign in to the intended business and location with booking access. Confirm the property, timezone and whether you are using Demo bookings or Live bookings. Use approved demo records when learning; do not create a live stay or share a private owner link as a test.",
      "steps": [
        "Open Events → Bookings. Use Booking data mode to choose Demo bookings or Live bookings, then choose the intended Booking property. Read the workspace notice: demo work is distinct from Production · saved operational records.",
        "Use Stays and the All stays, Arriving today, In care, Going home today, Upcoming or Past stays filters. Search by owner, pet or booking reference. Today-based views follow the property timezone; confirm the dates before assuming an arrival is missing.",
        "Choose New booking only when the selected property is enabled and you are authorized to reserve the stay. The form checks the selected property’s saved booking setup; do not force a reservation through a disabled property or an unavailable package.",
        "Where saved owner profiles are enabled, select the responsible Owner. If the owner belongs to several households, select one Household, then choose Who is staying? Add or update only the pets you are permitted to book. Do not combine pets from different households into one stay.",
        "If this property uses the simpler owner form, enter the Owner name and Owner email, then complete the pet details. Saved-account features are property-dependent; an absent owner-profile control does not authorize creating a duplicate customer.",
        "Choose the Service plan, Arrival date and Departure date or daycare day. Complete any required arrival/departure times and optional package add-ons. Wait for Available for the whole stay to refresh; availability depends on dates, package, pet count and selected options.",
        "Select one of the returned accommodations and review the quoted total. If there are no rooms or kennels available for the full stay, change the requested dates or package deliberately. Do not substitute an arbitrary accommodation or treat an old availability result as current.",
        "Complete the required booking questions, vaccination-valid-through date, emergency contact and care instructions. Where saved pet documents are available, the stay captures the selected evidence; a later profile upload does not silently replace the file captured for this visit.",
        "Choose Save booking once and wait for its saved result. If Owner access link ready appears, copy that private link for the actual booking owner to review the saved stay and accept its policy. The one-session copy control clears the displayed link after copying. Keep it out of public notes and screenshots.",
        "Open the saved stay from the owner name or booking reference. Read the booking status, accommodation, dates, pet amounts, saved policy and funding summary before continuing. Saving the booking is not proof that payment or owner policy acceptance has completed.",
        "For a holding booking, Confirm booking becomes available only when policy acceptance is recorded. For a confirmed booking, review Care for this stay, vaccination dates, emergency contacts and document requirements before Check in. A supplied expiry date is not itself staff verification of the document.",
        "Use Save care intake for permitted care changes, and review Their documents or General stay files without exposing them to other customers. Mark a document reviewed only after inspecting it; the action is not a replacement for the business’s actual care checks.",
        "Use Check in when the saved readiness issues are resolved. Mark Nightly care & services completed only after providing the service, and use Check out when the stay is actually finished. Payment, refund and earned-care reconciliation are reviewed separately.",
        "If arriving from a report link, retain the selected property and data mode. A booking link that is invalid or unavailable for the current business/location must be reopened from the correct report; do not edit identifiers until an unrelated stay opens."
      ],
      "controls": [
        {
          "name": "Booking data mode",
          "description": "Separates demo bookings from saved production work."
        },
        {
          "name": "Booking property",
          "description": "Sets the accommodation, timezone and currency context."
        },
        {
          "name": "Stay schedule",
          "description": "Filters saved stays without changing their records."
        },
        {
          "name": "Owner / Household / Who is staying?",
          "description": "Selects the responsible contact and permitted pets where saved profiles are enabled."
        },
        {
          "name": "Available for the whole stay",
          "description": "Server-returned accommodations for the complete requested stay."
        },
        {
          "name": "Owner access link ready",
          "description": "A private owner access link available for copying during the current session."
        },
        {
          "name": "Confirm booking / Check in / Check out",
          "description": "Separate lifecycle actions with policy and readiness checks."
        },
        {
          "name": "Care for this stay",
          "description": "Saved policy acceptance, care intake and readiness evidence."
        }
      ],
      "expectedResult": "The correct owner and pets have one saved stay at the intended property and dates, with appropriate policy/readiness evidence and an accurate lifecycle status. No payment or completed service is inferred from the reservation alone.",
      "troubleshooting": [
        "If the list is blank, check business, location, data mode, property and filters, then Refresh bookings. An empty result is not proof that the business has no historical stays.",
        "If availability or configuration fails, preserve the entered context and retry the supported screen after checking the error. Do not bypass a failed availability result with manual identifiers.",
        "If an owner or property changes while saving, reopen the current booking context and verify what was saved before repeating the request.",
        "If confirmation or check-in is disabled, inspect owner acceptance, required contacts, vaccination coverage and document review. Ask an authorized manager when the business requirements cannot be met."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "service-requests",
      "url": "https://platform.getcentri.com/centripos/service-requests",
      "title": "Review service requests and connect the right job",
      "summary": "Triage incoming request activity, confirm the customer, and start or link the correct job while keeping request state separate from unread activity.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Service",
      "introduction": "Service → Requests is a service-focused communications inbox. It groups incoming activity into requests and shows workflow status such as Open, Responded, Estimated, Scheduled and Completed. New activity and a completed service request are separate signals; a fresh call can arrive on an older job.",
      "beforeYouBegin": "Confirm the active business, contact identity and approved communication channels. Review messages and recordings only when your role permits access, and keep customer addresses, phone numbers and private request details out of public screenshots.",
      "steps": [
        "Open Service → Requests and allow the configured providers to load. The business’s request-inbox settings determine which channels and providers appear; a channel’s absence does not establish that no request exists.",
        "Choose All, Open, Responded, Estimated, Scheduled or Completed, then use search for a name, phone number or meaningful request text. The displayed search is limited to up to 80 matching threads; clear filters before treating a missing result as a missing customer.",
        "Open the intended request and review its latest activity, time, channel and earlier messages. A New activity badge indicates unread activity and does not reset the request’s workflow stage. Pinned and unread threads can appear before other recent threads.",
        "Confirm the linked customer. Use the offered contact action to open or match the right record before starting work. Check email and phone ownership rather than choosing a similar name.",
        "Use Open job when a request already links to a job. Inspect that original job’s customer, estimate, visits and state before creating anything new.",
        "When the request belongs to an existing open job and Link to open job is offered, choose the exact eligible job for the same customer. The chooser excludes completed/closed work and jobs without the required service or financial context. Wait for Request linked to job and verify both records.",
        "Use Start job for genuinely new work. It opens the service estimate workflow with the available customer and request context. Review the scope, location, customer and pricing there; opening the workflow alone is not an accepted estimate, scheduled visit or payment.",
        "Use Continue in CRM only when offered for the connected provider, or call the shown customer number through an approved process. Review the actual recipient and channel before any outbound contact. A loaded recording is private service evidence, not public content.",
        "Use Mark read/unread and pin controls for inbox organization. If the latest activity is genuinely a separate request on an existing linked job, use Make latest activity a new request only after reviewing its scope and customer; this intentionally creates a new request bucket.",
        "Use Ignore request only when the business has decided no further request handling is needed. It removes the request from this service inbox’s normal results; it does not prove the underlying job was completed or that the customer received a reply.",
        "After linking, starting an estimate or changing request state, reopen the request and verify the correct job link and workflow badge. Record the next owner/action through the business’s service process."
      ],
      "controls": [
        {
          "name": "Request workflow filters",
          "description": "All, Open, Responded, Estimated, Scheduled and Completed."
        },
        {
          "name": "New activity",
          "description": "Unread activity indicator, separate from request workflow status."
        },
        {
          "name": "Link to open job",
          "description": "Links an eligible request to an eligible existing job for the same customer."
        },
        {
          "name": "Start job / Open job",
          "description": "Starts an estimate for new work or opens the already linked job."
        },
        {
          "name": "Continue in CRM",
          "description": "Provider-specific continuation when an authorized CRM link exists."
        },
        {
          "name": "Make latest activity a new request",
          "description": "Separates new request activity from an existing linked request/job."
        },
        {
          "name": "Ignore request",
          "description": "Hides the request from normal service-inbox results; does not complete a job."
        }
      ],
      "expectedResult": "The request is matched to the intended customer, linked to the correct existing or new job when needed, and left in a clear workflow/read state without creating duplicate work.",
      "troubleshooting": [
        "If activity is missing, clear filters, check the selected business, provider/channel settings and request-specific link before creating another request.",
        "If no open jobs are offered, confirm the customer match and that the intended job is still open and has the required service/financial context.",
        "If a provider sync or recording fails, keep the original request and capture safe time/channel/error evidence for support.",
        "If a request was ignored unexpectedly, contact an authorized administrator with a safe request reference; do not create a duplicate to force it back into view."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "service-schedule",
      "url": "https://platform.getcentri.com/centripos/service-schedule",
      "title": "Schedule service calls and arrange a day route",
      "summary": "Choose the intended day and technician, schedule accepted jobs, and order stops while keeping customer appointment windows intact.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Service",
      "introduction": "Service → Schedule uses the same visit records as Today, with a selectable day and a scheduling queue for accepted service calls that still need a time. Scheduling, route ordering and customer-facing appointment commitments are separate decisions.",
      "beforeYouBegin": "Confirm dispatch authority, business/location, workstation timezone, agreed customer window and technician availability. A day route needs accurate addresses; mapping and fleet features must be enabled before they can be used.",
      "steps": [
        "Open Service → Schedule. Choose a day in the date strip, or use Previous, Today and Next. Times and day boundaries follow the workstation’s local time, so verify the selected date and timezone before saving an appointment.",
        "Use Show jobs when available to choose the intended technician, My jobs or All technicians. Non-dispatch users see only their own assignments. Check the scheduled, completed and booked-hour counts for the resulting day and filter.",
        "Review Accepted jobs to schedule when it appears. These are pending service calls without a scheduled start. Choose Open job to check the scope, customer and address before choosing Schedule; do not create a second job merely because a date is missing.",
        "In Schedule service call, enter Start and Expected finish. Changing Start proposes a one-hour finish; review and adjust it to the agreed window. The saved finish must be after a valid start.",
        "Choose Assigned to deliberately and select the exact technician. Verify the saved assignment afterward: the current scheduling flow can fall back to your signed-in profile when no technician is selected, so Assign later must not be treated as proof of an unassigned visit.",
        "Choose Schedule call once, wait for Service call scheduled, then check that the existing job now appears at the intended date/time and technician. If the result is unclear, reopen the job’s schedule before submitting again.",
        "For a displayed route, verify each address and appointment window. Use the earlier/later arrow controls to rearrange stops when offered. Reordering saves driving-order metadata; it does not change the customer’s scheduled start and finish.",
        "Use Best route only for one technician, with a business-location origin address and routeable job addresses. It is disabled for mixed technicians or a selected managed fleet route. The route planner calculates driving order and estimated arrivals while leaving appointment windows unchanged.",
        "If Fleet routes is available, open the route-management workspace for fleet assignments. Use the route pager and map to review the selected route; do not mistake a suggested order or ETA for a new appointment promise.",
        "On a phone, use View day map and Hide day map as needed. Open a job card for full detail. Use the travel/arrival/completion controls only when those events actually happen; reviewing a future schedule must not mark a visit as underway.",
        "After scheduling or reordering, reopen the day and job to verify date, window, technician, stop order and address. Communicate an approved appointment change separately through your normal customer process."
      ],
      "controls": [
        {
          "name": "Date strip / Previous / Today / Next",
          "description": "Selects the local day being planned."
        },
        {
          "name": "Accepted jobs to schedule",
          "description": "Pending accepted service calls without a scheduled start, available to dispatch users."
        },
        {
          "name": "Start / Expected finish",
          "description": "The agreed local appointment window; finish must follow start."
        },
        {
          "name": "Assigned to",
          "description": "Technician choice; verify persistence rather than inferring an unassigned state."
        },
        {
          "name": "Move stop earlier / later",
          "description": "Changes saved route order without changing appointment windows."
        },
        {
          "name": "Best route",
          "description": "Mapping-dependent driving optimization; choose one technician and valid origin/stop addresses."
        },
        {
          "name": "Fleet routes",
          "description": "Separate fleet-management workspace, shown to authorized dispatch users."
        }
      ],
      "expectedResult": "The original accepted job has the agreed visit window and intended technician, and the day route order is verified without changing appointment commitments or collecting payment.",
      "troubleshooting": [
        "If the scheduling queue is empty, confirm the job was accepted, remains pending and has no start time; check the technician filter.",
        "If route planning is unavailable, check one-technician selection, location address, stop addresses and mapping configuration.",
        "If saving fails, review the exact start/finish validation and reopen the original job before retrying.",
        "If a future day looks empty, verify the workstation timezone and selected date before assuming the visit is missing."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "service-today",
      "url": "https://platform.getcentri.com/centripos/service-today",
      "title": "Follow today’s service route",
      "summary": "Review assigned visits, record travel and arrival, track the work, and finish the correct visit or job without confusing completion with payment.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Service",
      "introduction": "Service → Today shows service visits scheduled for the current local day. Dispatch users can browse technicians and fleet routes; other users see their own assigned jobs. A visit, the overall job, and its invoice have separate states.",
      "beforeYouBegin": "Confirm the business, active location, date, customer and assigned technician. Use only the visit actions available to your role and business. Arrange any customer messages or signatures under your normal service policy.",
      "steps": [
        "Open Service → Today and wait for the day to load. Confirm the business and date in the greeting. Review the scheduled, completed and booked-time totals; they describe this day’s displayed visits, not cash received or every open service job.",
        "If Show jobs is available, choose All technicians, My jobs or the intended technician. Owners, super admins and authorized manager/fleet-manager roles can browse routes; other associates are limited to their own assignments. On a phone, open the technician picker, search and choose the exact person.",
        "When fleet routes are available, use the previous/next route controls to inspect the intended route and truck/crew. All routes can show a job’s assigned route; choosing one route limits the stops to that route’s order. A visible route does not grant permission to change someone else’s work.",
        "Review the next stop’s customer, job summary, time window, route ETA and address. Open the job card to inspect the full job before acting. Directions opens the selected address in maps, and the phone action uses the customer number shown on that job.",
        "Use On my way only when travelling to the correct scheduled visit. Start route appears only for a supported current native-app assignment and published route. The action records the visit as on the way and may send the configured customer text; review the result because a saved visit status and a failed text can occur together.",
        "Choose Arrived on the correct on-the-way visit once arrival is real. This records arrival and starts the job’s in-progress state. Use the available job clock to record work time; arrival by itself is not evidence of the duration worked.",
        "When location sharing is offered for an eligible trip, use the supported CentriPOS app and the displayed Share truck location or Stop sharing location control. Browser access alone does not guarantee native tracking. Follow workplace privacy policy and check the displayed sharing state.",
        "At completion, distinguish Finish visit from Finish job when both are offered. Finish visit leaves a multi-visit job open; Finish job completes the service work. On businesses using the combined flow, the button reads Complete. Capture the required customer confirmation/printed name or signature only for work actually completed.",
        "Wait for the completion result and reopen the job. A visit-completed notice can explicitly say that the job remains open. A completed job can make an on-completion invoice payable, but it does not itself collect money or prove a card charge settled.",
        "Use Payment only when the completed record offers it, then review the original invoice/receipt and its real balance. If a visit, completion or payment result is uncertain, inspect the saved original record before repeating an action."
      ],
      "controls": [
        {
          "name": "Show jobs",
          "description": "Authorized technician filter; other users see their own assigned jobs."
        },
        {
          "name": "Next",
          "description": "First displayed visit that is not completed."
        },
        {
          "name": "On my way / Start route",
          "description": "Records travel; configured customer SMS and native tracking have separate availability and results."
        },
        {
          "name": "Arrived",
          "description": "Records arrival and changes the job to in progress."
        },
        {
          "name": "Finish visit",
          "description": "Available on enabled businesses; completes this visit while preserving an open job."
        },
        {
          "name": "Finish job / Complete",
          "description": "Captures completion confirmation and may make an invoice ready for collection."
        },
        {
          "name": "View day map",
          "description": "Phone map toggle; requires addresses and available mapping configuration."
        },
        {
          "name": "Payment",
          "description": "Opens the linked financial record; visit/job completion is not payment proof."
        }
      ],
      "expectedResult": "The intended visit has the correct travel, arrival and completion evidence, the overall job remains open or completes deliberately, and any payment is verified separately on its original financial record.",
      "troubleshooting": [
        "If no jobs appear, check the current local date, selected technician/route and assignment before creating another job.",
        "If the page says the visit changed, refresh its current state before repeating the action.",
        "If the visit is On the way but the customer text failed, review the communication setup and original send evidence before retrying a message.",
        "If tracking or maps are unavailable, use the displayed job/address and approved dispatch process; do not assume the business is enabled for those features."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-portal-settings",
      "url": "https://platform.getcentri.com/centripos/customer-portal-settings",
      "title": "Save and publish Customer portal settings",
      "summary": "Prepare optional account sections and invoice formatting, distinguish a saved draft from the published presentation, and review capability status without changing integrations.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Customer portal edits the customer account presentation. Save draft stores a revision; Publish promotes the saved draft. The on-screen invoice is sample data. Feature-availability cards are read-only and do not activate delivery, accounting, fee posting, payment collection, or a supporting module.",
      "beforeYouBegin": "Use the intended business and an authorized settings role. Agree on the customer-visible sections, wording and privacy policy before publishing. Keep live customer links and financial data out of screenshots.",
      "steps": [
        "Open Admin → Customer portal and wait for settings to load. Confirm the business before changing anything. If loading fails or no draft appears, resolve the error or access issue rather than assuming that default-looking fields are saved settings.",
        "Read Capability status first. Statements, Subscription requests, Finance charges and QuickBooks lifecycle show availability and operational status separately. Status unavailable, Operational activation off or Worker release pending is not an invitation to enable an integration from this screen; refer the exact state to authorized support when needed.",
        "Under Portal sections, leave required Account overview and Balances and invoices available. Choose optional Deliveries, Receipt history, Events, Warranties, Payment methods and Loyalty only when appropriate for this business. Disabled optional sections are removed from portal navigation and the public portal response.",
        "Under Invoice formatting, enter the Heading as plain text, up to 80 characters, and choose an Accent color. Use the available date format deliberately: medium text date, US short date or international short date. Check that the chosen color and wording remain readable.",
        "Add a plain-text Footer message of up to 500 characters. Review Show item SKUs, customer-facing item notes, customer-facing invoice notes, discount breakdown and tax breakdown individually. Enable only information appropriate for the receiving customer.",
        "Review Draft preview after editing. The preview uses a sample customer and transaction, so it helps inspect formatting but cannot prove that a real customer has access, a balance is accurate, a feature is entitled, or a payment can settle. Account identity, balances, invoice number/dates, customer/business identity, totals and amount due remain required.",
        "Choose Save draft and wait for Customer portal draft saved. Reopen or reload and confirm the stored draft and revision. Unsaved browser edits are not the server draft that Publish promotes; save the intended changes before publishing.",
        "When the reviewed saved draft is approved for customers, choose Publish once. Wait for Customer portal settings published and check Published revision/time. A successful draft save alone does not mean the customer presentation is published.",
        "Use an authorized controlled customer account to review the published sections and document appearance. Confirm that hidden optional sections are absent and required financial facts remain visible. Check account permissions and feature entitlements separately; presentation changes do not grant another account access.",
        "If a revision conflict or publish/save error appears, reload the current settings, reconcile other edits and repeat only the intended step. Record the business, approximate time and safe error text for support; never include a private account token or full customer access link."
      ],
      "controls": [
        {
          "name": "Save draft",
          "description": "Stores the current normalized presentation as a server draft revision."
        },
        {
          "name": "Publish",
          "description": "Promotes the saved draft using revision checks; it does not first save unsaved browser edits."
        },
        {
          "name": "Capability status",
          "description": "Read-only module and operational status; does not activate providers or workers."
        },
        {
          "name": "Required sections",
          "description": "Account overview and Balances and invoices cannot be disabled here."
        },
        {
          "name": "Draft preview",
          "description": "Sample invoice for formatting review, not live customer or payment evidence."
        },
        {
          "name": "Published revision",
          "description": "Identifies the stored presentation promoted for customers."
        }
      ],
      "expectedResult": "The saved draft and published revision are understood separately, approved customer-facing sections/formatting are visible, and capability cards have not been mistaken for activation or payment controls.",
      "troubleshooting": [
        "Save the intended draft before choosing Publish; a preview change alone does not update the saved revision.",
        "If a capability reports pending/off/unavailable, retain that boundary and ask authorized support about the underlying module.",
        "Review the actual authorized customer account after publishing; sample preview data does not establish access or payment readiness."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "invoice-settings",
      "url": "https://platform.getcentri.com/centripos/invoice-settings",
      "title": "Configure invoice defaults, appearance, and fees",
      "summary": "Set where new invoices belong, review customer-facing documents, and save each settings area deliberately.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Invoices brings invoice creation defaults, email identity, terms and account fields, document appearance, statement preferences, and finance/late-fee policy into one workspace. These areas have separate save controls. Financial policy and sender availability depend on your permissions and the business configuration.",
      "beforeYouBegin": "Use the intended business and an authorized account owner or administrator. Agree on customer-facing identity, accounting terms and any fee policy with the business owner before saving.",
      "steps": [
        "Open Admin → Invoices. Start with Defaults & fields, Appearance & statements, or Finance & late fees according to the setting you need. Switching tabs does not save every section for you.",
        "In Defaults & fields, review Where new invoices belong. Choose a valid Default location and an available Default register, or leave them to use the current POS selection or only available choice. Changing the location clears the draft register choice. Save invoice defaults, then reopen to confirm both values.",
        "Review Invoice & statement emails. Sender name, From email and Default Reply-To email have their own Save email settings action. Approved sender domains and existing routing can restrict editing or select a different sender. Saving these defaults sends no invoice or statement; review the actual sender, recipients, subject and attachments in each send dialog.",
        "In Terms & account fields, choose the business default invoice terms and the Start payment terms behavior offered for new orders. An invoice’s own terms take priority, followed by the customer’s choices. Issued, delivery and order-created dates are different events; choose the intended rule rather than using a displayed status as a date.",
        "Add or maintain only the account/invoice fields your team needs. Use a clear meaning and supported type, preserve fields required by saved history, and review archive or permanent-removal consequences before changing an established definition. Save changes in this section and verify the persisted terms and fields.",
        "In Appearance & statements, choose the address, phone and email source for customer documents: issuing location, business details or a supported custom value. Review which identity details are shown. If a business-source value is missing, correct General Info or choose another valid source before saving.",
        "Choose the company or a custom invoice logo. Custom uploads accept PNG or JPG, 2 MB or smaller. Review the Header preview, invoice-information fields and their order, and extra details in the customer open-invoice list. Invoice number, status and amounts remain visible even when optional fields are hidden.",
        "Enter approved payment instructions and statement starting preferences. Instructions can appear on customer invoices and PDFs, including the How to pay path when online checkout is unavailable. They do not enable a payment processor. Review statement type/date choices again when preparing an actual statement.",
        "Choose Save changes for appearance, then reopen and inspect a controlled customer invoice/PDF and statement before broad use. The header preview is an illustration, not proof that every customer document or delivery channel is correct. If a concurrent-edit or upload error appears, reload and verify the saved values before retrying.",
        "Open Finance & late fees only with an approved policy. Choose No fees, a finance charge or a late fee; review calculation, cadence, dates, exemptions and whether eligibility is all associated contacts or only selected contacts. Each account uses one fee method at a time. Review/manual posting and automatic posting have different effects.",
        "Use Save fee settings only after checking the audience and amounts. Enabling a nonzero automatic policy opens Enable automatic fee posting?; its separate Save automatic policy confirmation changes the policy that can increase amounts owed. This confirmation does not send notices automatically. Reopen the policy and verify its displayed state before relying on future posting."
      ],
      "controls": [
        {
          "name": "Defaults & fields",
          "description": "Separate invoice origin, email identity, terms and field settings."
        },
        {
          "name": "Save invoice defaults / Save email settings",
          "description": "Independent save actions; email settings save sends nothing."
        },
        {
          "name": "Appearance & statements",
          "description": "Customer document identity, information, instructions and starting statement format."
        },
        {
          "name": "Header preview",
          "description": "Illustrative preview; validate a controlled actual document separately."
        },
        {
          "name": "Finance & late fees",
          "description": "Owner-authorized policy affecting eligible overdue obligations."
        },
        {
          "name": "Save automatic policy",
          "description": "Explicit automatic-posting confirmation; no automatic notice is implied."
        }
      ],
      "expectedResult": "The intended business retains the reviewed defaults and presentation, and any approved fee policy has the exact audience and posting mode expected. Actual documents are checked separately from saved settings.",
      "troubleshooting": [
        "If a setting appears absent, confirm account-owner/admin permissions and wait for loading before assuming it is unsupported.",
        "For a settings-changed conflict, reload and reconcile another administrator’s changes instead of repeatedly overwriting them.",
        "Do not test email, automatic fees or payment collection on a live customer merely to validate that configuration saved."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "quickbooks-invoice-payments-deposits",
      "url": "https://platform.getcentri.com/centripos/quickbooks-invoice-payments-deposits",
      "title": "Reconcile invoice payments and QuickBooks deposits",
      "summary": "Follow one invoice from its recorded customer payment to QuickBooks payment evidence, matched processor settlement and an approved bank deposit without collecting or posting twice.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Invoice accounting",
      "introduction": "A customer payment, a QuickBooks payment, a processor settlement and a bank deposit are related records with separate states. Read each record and its allocation before deciding that accounting is complete. The controls described here appear only where the connected workflow and your permissions allow them.",
      "beforeYouBegin": "Confirm the business, invoice and original payment reference. Use an approved finance role for accounting actions. Keep credentials and raw payment information out of screenshots and support notes. Do not repeat a customer charge because accounting is pending.",
      "steps": [
        "Open the intended Customer Accounts invoice and its linked receipt. Confirm the customer, invoice total, remaining local balance, recorded local payments and the linked QuickBooks document before following accounting links.",
        "If Send to QB is available and the invoice needs an accounting copy, use it only with invoice-send permission and the accounting owner’s approval. Review any customer match carefully. Invoice added to QuickBooks or an invoice-linked result confirms the accounting relationship; this action does not email the customer.",
        "Use Refresh QuickBooks status or Check QuickBooks to update observed invoice and payment evidence. These checks do not send invoices or create a new local tender. If the update connection needs checking or reports waiting/review items, preserve that status and ask support to check the linked update rather than posting substitute money.",
        "Read sent and viewed evidence with its actual date. If QuickBooks reports a prior send but its original date is unavailable, keep that distinction. A new observation time must not be represented as the historical customer-send date.",
        "Inspect Payments recorded in QuickBooks. Open the payment reference and compare payment date, method, total and linked invoices. When one payment covers several invoices, the Payment total is the full payment; use the invoice allocation to avoid counting that total once for every invoice.",
        "If QuickBooks shows the invoice paid while CentriPOS shows an open amount, stop before requesting another payment. Use Check the open balance, then have the accounting owner reconcile the existing payment, its invoice allocation and the local receipt. A display mismatch is not a new customer debt.",
        "Where combined account payments are enabled, verify the one recorded provider payment and its original invoice allocations. A combined QuickBooks payment must apply only the approved principal to the intended invoices. Fees and surcharges belong to the separate settlement treatment and must not inflate the original invoice principal.",
        "If the invoice shows Pending QBO sync for EPX deposit, the payment can already be recorded locally while QuickBooks waits for matched settlement. EPX settlement needs accounting review is a different exception. Preserve the payment and settlement reference; do not charge again, manually mark a new payment, or bypass the settlement gate.",
        "In Matched EPX settlement, follow the branded processor deposit reference. Compare the deposit date, full deposit processing fee, fee allocated to this invoice, surcharge credit and invoice payment. The full fee covers the settlement; the allocated fee is only this invoice’s share.",
        "Only an approved user with the required QuickBooks administration access should use Review & sync deposit. Read the entire settlement, including all connected invoices and payments, rather than approving only the invoice currently open. Verify the active USD destination bank account configured in Admin → Integrations → QuickBooks and the processing-fee expense mapping.",
        "Check the review math: invoice principal payments plus collected surcharge credit minus the full processing fee equals the net bank deposit. Confirm the original invoice register classifications on fee/surcharge offsets. If any original invoice, payment allocation, account, amount or settlement evidence changed, check the original settlement again and review the new result.",
        "Choose Confirm & sync only when the accounting owner approves that exact review. The action creates or recovers one linked QuickBooks bank deposit, preserves the original invoices and verifies the returned accounting record. If QuickBooks created the deposit but local confirmation is pending, reopen this same review to recover it instead of creating a replacement.",
        "Open the linked QuickBooks deposit and compare its payment links, full fee, surcharge credit, date, bank account and net amount. Match it to the bank feed under your accounting process. A linked deposit alone does not establish that bank reconciliation is complete.",
        "For a skipped, failed, pending or review-needed result, save the safe invoice, receipt, payment and processor-deposit references plus the exact error and time. Correct only the verified cause, then use the supported check/recovery path once and reopen both records to confirm the result."
      ],
      "controls": [
        {
          "name": "Send to QB",
          "description": "Adds or links an invoice accounting copy with explicit permission; does not email the customer."
        },
        {
          "name": "Check QuickBooks",
          "description": "Refreshes observed linked accounting information; does not post local tender."
        },
        {
          "name": "Payment total",
          "description": "Full QuickBooks payment amount, which can cover several invoices."
        },
        {
          "name": "Check the open balance",
          "description": "QuickBooks and local open balance disagree; reconcile the original payment before requesting money again."
        },
        {
          "name": "Pending QBO sync for EPX deposit",
          "description": "Recorded payment is waiting for matched processor settlement before QBO payment sync."
        },
        {
          "name": "Full deposit processing fee",
          "description": "Fee for the complete processor settlement, distinct from this invoice’s allocated share."
        },
        {
          "name": "Review & sync deposit",
          "description": "Opens a review of the entire verified settlement before any bank deposit is created."
        },
        {
          "name": "Confirm & sync",
          "description": "Creates or recovers the approved QuickBooks bank deposit after server verification."
        }
      ],
      "expectedResult": "One original customer payment remains traceable through its intended invoice allocations and QuickBooks payment, and one approved settlement deposit accounts for principal, surcharge credit, full fee and net bank amount without changing the original invoices or collecting twice.",
      "troubleshooting": [
        "An update or deposit check can fail while the customer payment remains valid. Check the original payment before repeating any collection.",
        "A payment total spanning multiple invoices must be reconciled by allocation, not multiplied by invoice count.",
        "If the review says the settlement changed, check the original settlement again and re-review all invoices and payments.",
        "If a QuickBooks deposit was created but its local confirmation is pending, recover it from the same review. Do not add a second deposit directly in QuickBooks.",
        "If the action is unavailable or permission is denied, ask the accounting owner to confirm the intended workflow and access. Do not change roles or connections as a workaround."
      ],
      "updated": "2026-11-16",
      "sourceReviewed": "2026-11-16",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "record-invoice-payment",
      "url": "https://platform.getcentri.com/centripos/record-invoice-payment",
      "title": "Record or collect an invoice payment",
      "summary": "Distinguish money already received from a new saved-method collection, review the amount and reference, and keep an uncertain result tied to its original attempt.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Customer Accounts",
      "introduction": "Record Payment has two different actions. Already received records money the business has already received; it does not charge a card, withdraw from a bank, or apply store credit. Saved card / bank attempts a new authorized collection through an eligible saved method. Confirm which action matches the real payment before proceeding.",
      "beforeYouBegin": "Open the exact issued invoice for the correct business and customer. Confirm its linked receipt, current balance, payment history and any original attempt still awaiting confirmation. Have permission to collect or record payments, and confirm that the accounting workflow allows CentriPOS collection.",
      "steps": [
        "In Sales → Invoicing, open the invoice and review the document number, customer, total, balance, issue/due dates and payment activity. A proposal awaiting acceptance is not a payable invoice. Paid and Void invoices do not offer a new normal payment action.",
        "Confirm the invoice is issued, any required customer acceptance is complete, and no collection is already processing or awaiting review. An existing active payment plan or other collection guard can require its own workflow. If the server declines this recorder, investigate that condition instead of recording money through a second path.",
        "Choose Record Payment. If the button says Check payment or the form reports an earlier attempt awaiting confirmation, check that original attempt first. Do not switch actions, create another request, or use a second invoice to work around an uncertain result.",
        "Choose Already received only for money that has actually reached the business through the selected method. Enter a positive amount no greater than this invoice’s current balance, with no more than two decimal places. Review the current balance again if another person or process may have collected money.",
        "Choose the enabled Payment Type that describes the actual incoming money. Store credit, gift cards and terminal/gateway collection methods that are disabled in this recorder cannot be used as substitutes. The available list follows the current location and POS-channel configuration.",
        "Complete the method’s required reference, such as the check number, and choose Received on. Do not enter a future date. Add a safe explanatory note when useful; never put card numbers, bank details, security codes or reusable payment credentials in the note or reference.",
        "Read the register-session message. A payment dated today can be included in the current open register session; a historical collection is recorded outside that session. Cash requires today’s open register. Do not alter the date merely to force a payment into a different closure.",
        "Confirm Payment has already been received, then choose Record received payment once. This is a financial record of the received amount, not a new charge or withdrawal. Wait for the recorded result and verify the invoice’s updated balance and payment row.",
        "If recording cannot be confirmed, keep the original operation and choose Check original payment when offered. The stored operation preserves its amount, type, date and reference while its outcome is resolved. Do not record the same incoming money again or remove recovery information to bypass this state.",
        "For a new collection, choose Saved card / bank instead. Select the exact eligible saved method belonging to this customer. Review the masked method identity and amount. The displayed server review determines whether that method and amount are eligible for this invoice; a saved method’s presence alone is not permission to charge it.",
        "For an eligible saved card, use Charge reviewed saved card only after confirming the customer’s authorization. If no supported method is available or eligibility cannot be checked, stop and use the approved customer payment workflow or ask support to review the safe error. Do not enter a token or private key manually.",
        "For a supported saved bank account, complete the one-time bank authorization review presented for this invoice and amount. A card button is not a substitute for that review. Do not assume choosing the account or seeing a prior mandate authorizes this new bank debit.",
        "After a saved-method submission, use Check original payment attempt if the outcome is pending or uncertain. Keep that attempt attached to the same invoice. Do not charge again, change the method, or add a separate Already received record while the original collection may still complete.",
        "Reopen the invoice and its connected receipt after a confirmed result. Match the amount, method, reference/date, remaining balance and payment status. Where QuickBooks is connected, inspect the accounting copy and any sync note independently; a recorded local payment can still require accounting attention.",
        "Reconcile authorization, captured/recorded payment, processor settlement or bank deposit, register-session totals and the accounting copy as separate evidence. Paid · deposit pending means the invoice has no balance while settlement is still pending. This one-invoice payment does not change future recurring charges."
      ],
      "controls": [
        {
          "name": "Already received",
          "description": "Records an existing receipt of money; no new card charge, bank debit or store-credit application."
        },
        {
          "name": "Saved card / bank",
          "description": "Attempts a separately authorized collection from a supported saved customer method."
        },
        {
          "name": "Amount",
          "description": "Positive cents, no more than the current invoice balance."
        },
        {
          "name": "Payment Type",
          "description": "Enabled POS-channel type allowed at the current location; unsupported collection types are disabled."
        },
        {
          "name": "Reference",
          "description": "Method-specific evidence such as a check number when required."
        },
        {
          "name": "Received on",
          "description": "Actual receipt date, not a future date; controls register-session treatment."
        },
        {
          "name": "Payment has already been received",
          "description": "Required confirmation for the financial recorder."
        },
        {
          "name": "Record received payment",
          "description": "Submits the existing incoming payment once."
        },
        {
          "name": "Check original payment",
          "description": "Rechecks the retained received-payment operation instead of creating another."
        },
        {
          "name": "Charge reviewed saved card",
          "description": "Uses the eligible saved card and reviewed invoice amount."
        },
        {
          "name": "One-time bank authorization",
          "description": "Separate review for the saved bank account, invoice and amount."
        },
        {
          "name": "Check original payment attempt",
          "description": "Resolves the existing saved-method collection without duplicating it."
        },
        {
          "name": "Paid · deposit pending",
          "description": "Invoice balance is settled while processor/bank settlement remains pending."
        },
        {
          "name": "QuickBooks sync note",
          "description": "Accounting-copy state, separate from whether the invoice payment was recorded."
        },
        {
          "name": "Invoice and collection eligibility",
          "description": "Issuance, required acceptance, balance, pending collection and active-plan checks can block this recorder."
        }
      ],
      "expectedResult": "The intended payment appears once against the correct invoice and receipt, the balance reflects the confirmed amount, and any unresolved collection, deposit or accounting state remains visible for follow-up.",
      "troubleshooting": [
        "If an earlier payment is awaiting confirmation, keep the original request and check its status. Do not record or charge another payment to make the screen look complete.",
        "If recording or charging is blocked, check the business, role, current invoice balance, location, payment type, method eligibility and register-session requirement. Do not use an unrelated method or change the real payment date to bypass a block.",
        "If a saved-method review or local recovery storage is unavailable, resolve that condition before submitting. Removing recovery state or switching browsers can hide an unresolved payment rather than cancel it.",
        "For support, provide the safe invoice/receipt reference, amount, actual date, payment method label and exact error. Keep raw card/bank information, authorization payloads, tokens and browser storage out of messages."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "invoice-account-link",
      "url": "https://platform.getcentri.com/centripos/invoice-account-link",
      "title": "Open an invoice or account statement",
      "summary": "Review the intended private invoice or statement, download available documents, and pay only the current eligible balance through the enabled secure checkout.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "Invoice, account-statement and Customer Account Portal links have different purposes. A private invoice or statement can show account balances and documents without granting staff access. Treat the complete branded link as private and use only the payment choices actually offered for that account.",
      "beforeYouBegin": "Use the link sent by the business, confirm its branded pos.getcentri.com destination and the intended customer account, and stop if the merchant, invoice, location or amount is unexpected.",
      "steps": [
        "Open the invoice or statement link from the business. It may use a short private /s/ link or a longer signed account-document path. Let the application resolve it; do not decode or change its token, add another invoice ID, or move a token to another business path.",
        "Wait for Loading your invoice or Loading your statement. This invoice is unavailable or This statement is unavailable can mean access or data could not be verified; use the offered retry only when appropriate or ask the business for a fresh link. Do not diagnose the cause from the customer wording alone.",
        "For an invoice, confirm merchant and customer identity, invoice number, status, issued/due dates, terms, bill-to/ship-to and any other displayed invoice details. An invoice preview explicitly says it is not yet awaiting payment. Do not pay a preview or treat a copied link as evidence that an invoice was issued.",
        "Review every line, quantity, rate, discount, tax, invoice total, paid amount and remaining balance. Check the memo and payment instructions. The displayed balance, not an old email or saved PDF, governs an offered current payment.",
        "Use View invoice PDF for the invoice copy. On a native app surface the control may open the PDF in the browser. Inspect the downloaded or opened document independently, and keep the file private after closing the original link.",
        "Open Included documents only for the attachments offered for this invoice. A paid copy can also show payment date, method, reference, applied amount, surcharge and a total that covers multiple invoices. Do not count the full multi-invoice payment once for every invoice.",
        "When Proof of delivery is shown, review the saved signature, date and displayed signer for the correct invoice. Delivery evidence is private and does not itself prove settlement or authorize a further charge.",
        "For a statement, confirm the statement type, as-of date, period and any location name. Open Item, Balance Forward and Transaction Statement describe different reports. Read a location statement balance separately from the whole-account balance.",
        "Read historical statement sections as dated evidence. Transaction Statement activity totals are not an amount due, and a historical statement balance may differ from current open invoices. Payment tools below the report always use balances still open today.",
        "Use View statement, Download statement and the available invoice-packet control to inspect the report or selected invoice documents. Check the actual file list and result; downloading a packet is not sending it or paying the invoices.",
        "Review the account’s current open invoice list and overdue indicators. An overdue amount is included in the open balance rather than an additional charge. Open an invoice number to inspect its individual detail before choosing it for payment.",
        "Where selection is available, choose only the intended payable invoices and review the selected count and total. The screen caps one selection at 50 invoices. A disabled invoice is not currently payable through that control.",
        "Choose Pay or How to pay and review the account name, selected invoices, due dates and selected balance again. Some accounts provide payment instructions, some route each invoice to its own secure checkout, and only explicitly enabled accounts offer one combined checkout.",
        "If the review says Choose an invoice to pay, use that invoice’s individual action. Do not assume that selecting several invoices combines their charge. If the screen says Payment submission isn’t enabled yet or Payment not enabled, it is a preview and does not collect payment details.",
        "For an enabled secure checkout, review all supported methods and any card/bank fee before the final confirmation. Enter payment information only into the provided secure fields. Confirm once and wait for the original payment outcome rather than refreshing or submitting another payment while processing.",
        "If Use a saved card or bank account is offered, verify an email associated with this exact account using the offered code workflow. Choose the intended masked saved method only after verification. New details, saved methods, account defaults and automatic-payment consent are separate decisions; follow the actual enabled checkout.",
        "Use Access account for fuller customer account management. Follow the customer identity verification required there; an invoice link must not be treated as staff sign-in or permission to view a different customer account.",
        "After a reported payment, reopen the original invoice and verify its current status, applied amount and remaining balance. If the result is processing, uncertain or inconsistent, contact the business with a safe invoice/payment reference before trying again. A browser return or opened PDF is not settlement proof.",
        "Keep private links, saved documents, signatures and payment references with the intended recipient. Ask the business for a fresh statement link after expiry rather than editing its date or token. Never paste the full link or payment credentials into a public support request."
      ],
      "controls": [
        {
          "name": "Invoice preview",
          "description": "Document is not yet awaiting payment."
        },
        {
          "name": "View invoice PDF / Included documents",
          "description": "Invoice copy and authorized attachments; inspect actual returned files."
        },
        {
          "name": "Paid invoice payment details",
          "description": "Applied amount can differ from the whole payment when several invoices were covered."
        },
        {
          "name": "Statement type and dates",
          "description": "Historical report scope distinct from today’s current payable list."
        },
        {
          "name": "Location / whole-account balance",
          "description": "A location statement can be one part of the account."
        },
        {
          "name": "Selected invoices",
          "description": "Only currently payable rows; one selection is limited to 50."
        },
        {
          "name": "Pay / How to pay",
          "description": "Review enabled payment path or instructions, not a guarantee of online collection."
        },
        {
          "name": "Email verification",
          "description": "Required before exposing offered saved payment methods for the exact account."
        },
        {
          "name": "Access account",
          "description": "Opens the customer account access/verification path, separate from staff CentriPOS."
        }
      ],
      "expectedResult": "The customer can identify and review the correct invoice or statement, obtain only its permitted documents, and complete at most one confirmed payment through an actually enabled checkout using current balances.",
      "troubleshooting": [
        "If merchant, customer, invoice, date, location or balance is unexpected, stop and contact the business before payment.",
        "A historical statement discrepancy is a reconciliation issue, not permission to change its token or pay its historical total again.",
        "If a payment or saved-method option is unavailable, use the provided business instructions; do not attempt to activate hidden controls or supply a gateway key."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-statements",
      "url": "https://platform.getcentri.com/centripos/customer-statements",
      "title": "Prepare, review, and send customer statements",
      "summary": "Choose the right statement type and dates, review separate location balances, send a reviewed document, and distinguish prepared history from confirmed delivery.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Customer Accounts",
      "introduction": "A customer statement is a dated report of account activity, not a new invoice or a payment. Preparing, previewing, copying and downloading a statement do not send it. A historical balance and today’s payable balance can be different.",
      "beforeYouBegin": "Confirm the correct business, customer, location and permitted billing workflow. Review recipient contact details and the business timezone before preparing or sending private financial information.",
      "steps": [
        "Open Invoicing and choose Statement, or choose Craft statement for the intended customer. Select the customer in Prepare a statement and confirm the displayed name, saved To/CC/BCC addresses and phone. These details are a starting point; review recipients again when sending.",
        "Choose Statement type. Open Item lists invoices with an amount still owed as of the statement date. Balance Forward includes an opening balance plus invoices and payments in the chosen period. Transaction Statement reports activity billed and received during the period; its activity total is not itself an amount due.",
        "For Open Item, set Statement date. For Balance Forward or Transaction Statement, set From and Through. The end date cannot be in the future, and the start date must not be later than the end date. Changing type, date or customer clears the previously prepared links so they must be prepared again.",
        "Choose Prepare statement once and wait for the result. This prepares separate statement links for the locations with balances. It does not send email or text, collect payment, or alter the account’s financial history.",
        "Review every location statement. Confirm location name, statement balance, type and dates. When multiple location balances exist, distinguish the statement’s location amount from the displayed whole-account balance; do not add repeated whole-account figures together.",
        "Choose View statement to inspect the customer page. Check business/customer identity, as-of date, invoice references, terms/detail fields and relevant payments or credits. Use Download PDF to inspect the matching report. The page and PDF must use the same statement type, dates and detail settings.",
        "For historical statements, compare their dated totals with current open invoices separately. A payment received after the as-of date can reduce today’s payable balance without rewriting the historical statement balance. A Transaction Statement describes activity, while current payment controls show what remains payable now.",
        "Use Copy link only for the approved recipient/channel. The generated branded pos.getcentri.com link can be a short private document link or a signed account-statement link. Do not edit its path/query/token or expose it in public support. The prepared private link expires after 30 days; a saved PDF can remain accessible after link expiry.",
        "To deliver a location statement, choose Send statement. Review Send to customer, the available Email/Text route, location sender and destination. A disabled route or sending-not-enabled message requires communication configuration; it does not authorize using another location’s sender.",
        "For email, check To, CC, BCC, From, permitted Reply-To and the message. Inspect the attachment list where provided: select only intended documents and open the displayed PDFs/files for review. If attachment selection is unavailable, follow the stated attachment behavior rather than assuming every invoice file is included.",
        "Choose Review email, inspect the subject, selected files and rendered message, then choose Send statement once. Review-only text means nothing has been sent yet. Any recipient, message, sender or attachment change can require a new email review.",
        "For Text, verify the customer’s mobile number and actively confirm agreement to receive the transactional text. Review the message and secure link, then send once only when that route is enabled. The channel consent and sending setup remain separate requirements.",
        "If the send result is uncertain, use Check sending status for the original request. Do not close the workflow and create a second send merely because the first response was interrupted. A QuickBooks update still finishing is separate from confirmed customer delivery.",
        "Review the customer profile’s Statements history. Prepared means a document was created, not sent. Sent, Not sent, Sending and Send not confirmed distinguish recorded attempts. Open Send history to inspect time, recipients, sender, Reply-To, subject and resends; an earlier successful send can coexist with a later failed resend.",
        "Use Refresh or Show older statements as needed. Private link expired means the history remains but that link must not be reused. Prepare a fresh, correctly scoped statement when needed rather than editing an expired link or deleting the old delivery evidence."
      ],
      "controls": [
        {
          "name": "Statement type",
          "description": "Open Item, Balance Forward or Transaction Statement."
        },
        {
          "name": "Statement date / From / Through",
          "description": "As-of date and optional historical period; valid dates end today or earlier."
        },
        {
          "name": "Prepare statement",
          "description": "Creates private location-specific reports; sends nothing."
        },
        {
          "name": "Location balance / whole-account balance",
          "description": "Separate figures that must not be combined repeatedly."
        },
        {
          "name": "View statement / Download PDF / Copy link",
          "description": "Review or share the prepared document using the same type and dates."
        },
        {
          "name": "Send statement",
          "description": "Opens the reviewed delivery workflow; preparation alone does not send."
        },
        {
          "name": "Review email",
          "description": "Required statement-email review before the explicit send."
        },
        {
          "name": "Check sending status",
          "description": "Recovers the original uncertain send instead of duplicating it."
        },
        {
          "name": "Statements history",
          "description": "Prepared documents and delivery attempts, with expiry and separate resend outcomes."
        }
      ],
      "expectedResult": "The intended customer receives only the reviewed statement for the correct type, dates and location through an authorized sender; preparation, historical totals, current payable amounts and confirmed delivery remain distinct.",
      "troubleshooting": [
        "If no statement is produced, check the selected customer, statement dates, eligible issued invoices and current balance before retrying. Do not create an invoice to force a statement to appear.",
        "A balance or payment-history review error requires reconciliation of the underlying records. Do not manually change history merely to make a report generate.",
        "If email/text is unavailable, ask the authorized administrator to review the location’s sender settings. Do not change another location’s integrations or send under another merchant identity."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "event-payment-plans",
      "url": "https://platform.getcentri.com/centripos/event-payment-plans",
      "title": "Offer event deposits and payment plans",
      "summary": "Let a customer pay an event receipt in full or place an approved deposit, then follow one accessible installment schedule without creating a second payment ledger or disconnecting the registration from its household receipt.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Event payments",
      "introduction": "Event payment plans extend the normal CentriPOS receipt and customer-account workflow. The sale remains the booked total and open balance, sale_payments remains the only tender ledger, and invoice_billing_plans with invoice_installments stores the schedule. Event records add the offering policy and registration relationship; they do not copy money into a separate event ledger. This is a controlled-rollout capability, so a documented screen, API resource, webhook, or HighLevel definition is usable only after it is enabled for the selected business.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open the offering and choose Payments. Confirm the business and the offering timezone before changing a policy. If Payments is absent, the event payment-plan rollout is not enabled for this business; do not simulate a plan with discounts, custom zero-dollar lines, duplicate receipts, or manually confirmed registrations.",
        "Keep Pay in full available unless the business has an approved reason to require a plan. For each plan, enter a staff-readable name and code, choose Draft or Active, decide whether customers may select it, and optionally limit it to one ticket option. Archive an obsolete policy instead of reusing its identity for different terms.",
        "Choose a percentage or fixed deposit. The server calculates the deposit from the authoritative quoted receipt total and rejects a deposit that is zero, equals the total, exceeds the total, or cannot leave valid installments. Browser-entered prices and dates are never payment-plan authority.",
        "Set the number of remaining installments, first-payment delay, cadence in days, weeks, or months, and optional final-due offset before the first event start. Set the grace period separately. Preview the real cent amounts and calendar dates in the offering timezone; the final installment absorbs any rounding remainder.",
        "Choose the capacity, admission, and delinquency behavior deliberately. The normal camp pattern is Deposit reserves capacity and confirms the registration, while a stricter event can require Paid in full before admission. A future installment is not delinquent; delinquency begins only when an unpaid due date passes its configured grace boundary.",
        "Review every ticket option covered by the policy. A plan applies to the complete qualifying event receipt, including separately sold shirts, kits, meals, or take-home robots on that receipt. If event tickets in one cart do not share a compatible offering policy and currency, split the purchases rather than joining incompatible schedules.",
        "Use the policy preview before publication. Confirm amount due today, balance after deposit, every installment amount and due date, final event deadline, grace period, capacity behavior, admission rule, customer-selectability, and affected ticket options. Publication validation should fail closed when the schedule cannot reconcile or extends beyond an enforced final deadline.",
        "At customer checkout, present Pay in full and each eligible Payment plan as keyboard-operable radio choices with visible focus. State the full total, amount due today, balance after deposit, every amount and due date, and capacity, cancellation, delinquency, and admission terms in text—not color alone. Put validation next to the affected choice and move focus to the error summary after a failed submission.",
        "When the customer chooses a plan, CentriPOS authorizes and records only the server-derived deposit. A successful deposit becomes a normal sale_payment; the receipt retains its full total, amount paid, and remaining balance; the receipt-backed A/R invoice and installment plan are created; and the storefront order becomes payment_plan_active. Registration and scarce-capacity commitments follow the immutable policy snapshot captured with the quote.",
        "Do not treat registration confirmation as proof of full payment. Registration status, plan status, installment status, receipt balance, and ticket/admission eligibility are separate fields. A policy may confirm a camper after the deposit while still showing an open customer balance, and a paid-in-full admission rule can withhold admission without putting a depositor back into an expiring pending hold.",
        "In the customer account experience, show one household receipt plan once even when it covers siblings or several registrations. Show deposit paid, total paid, remaining balance, next due date, past-due amount, schedule, plan status, and whether event admission has been released. Make a payment opens the ordinary branded receipt link: a scheduled installment amount may be prefilled as a suggestion, but the customer can choose the full balance or enter another positive partial amount up to the remaining balance. Never expose a vault token, processor payload, database route, or reusable payment capability.",
        "Apply every later card, ACH, cash, check, or other approved tender through the normal receipt payment workflow. CentriPOS allocates valid payments against the schedule and recalculates the plan; an extra payment reduces the balance and an early payoff completes it. Never mark an installment paid by editing a plan or event row, and never create a duplicate event payment to mirror a sale_payment.",
        "Use staff receipt and account controls to collect a payment or, when the operation is enabled, pause, resume, cancel the plan, send the branded customer payment link, or explicitly reinstate admission after a released plan is fully settled. Require an audit reason for a material schedule or lifecycle change. Reinstatement requires its own nonblank 1–1000 character reason and a unique Idempotency-Key. A plan setting does not authorize automatic card charges: auto-collection requires a supported saved method and separate timestamped customer consent.",
        "Read the lifecycle precisely. A plan can be Draft, Active, Paused, Delinquent, Completed, or Canceled; an installment can be Scheduled, Due, Processing, Paid, Failed, or Canceled; and a storefront schedule can be Pay in full, Pending deposit, Active, Delinquent, Completed, or Canceled. The registration keeps its own confirmed, waitlisted, cancelled, transferred, refunded, checked-in, or completed state as applicable.",
        "In Events → Registrations and Reports, show booked registration value, deposit and other completed cash collected, remaining scheduled balance, amount currently due, amount past due, refunds, next due date, plan status, and admission-released count/state as separate measures. Pending payments never count as collected or paid-in-full. Group registrations sharing one sale before totaling financial balances so a sibling household plan is not counted once per camper.",
        "For server integrations, use event-payment-plan-policies for offering policy CRUD and event-registration-payment-plans for the receipt-backed plan lifecycle. Every registration-plan GET requires invoices:read plus events:registrations:read. POST the collection to create a plan, then use /{registration_payment_plan_id}/pause, /resume, /cancel, /send-customer-link, or /reinstate-admission for explicit lifecycle work; every command requires events:registrations:write plus invoices:write, operation class payment_adjacent, and a unique Idempotency-Key. Create verifies that the tenant receipt has an event registration and matching event-ticket receipt line before calling the authoritative invoice-plan command. Pause, resume, and cancel change lifecycle state without recording money. send-customer-link returns a safe branded capability ready for caller delivery, not proof of delivery or payment. There is no mark-paid route and no command silently auto-charges a saved method. The OpenAPI x-centripos-status and runtime response remain the availability source of truth for each entitled tenant.",
        "Subscribe only enabled endpoints to event_payment_plan_policy.created, event_payment_plan_policy.updated, event_payment_plan_policy.archived, event_registration_payment_plan.activated, event_registration_payment_plan.paused, event_registration_payment_plan.resumed, event_registration_payment_plan.delinquent, event_registration_payment_plan.completed, event_registration_payment_plan.canceled, or event_registration_payment_plan.admission_reinstated, plus the existing sale and completed-payment events genuinely needed by the receiver. Policy delivery requires events:read; registration-plan delivery requires invoices:read. Verify the signed webhook, deduplicate its immutable event ID, and fetch broader financial detail only with a separately scoped key. Payloads exclude child-sensitive answers, medical or waiver data, card and vault data, raw processor responses, payment links, and command-only count output.",
        "After HighLevel Marketplace and per-location activation, use the matching payment-plan lifecycle triggers for appropriate reminders and household communications. Enabled actions are centripos_receipt_payment_plan_create, centripos_receipt_payment_plan_pause, centripos_receipt_payment_plan_resume, centripos_receipt_payment_plan_cancel, centripos_receipt_payment_plan_send_customer_link, and centripos_receipt_payment_plan_reinstate_admission. Reinstatement requires payment_plan_id and a nonblank reason, calls the same capacity-safe receipt-plan command, and returns safe registrations_reinstated, occurrence_enrollments_reinstated, seats_reinstated, and tickets_issued counts. There is intentionally no Mark paid action: money must arrive through an authoritative completed receipt tender with an external reference and audit evidence.",
        "For imported Event Espresso history, preserve each known transaction, payment entry, paid amount, balance, and registration state. Do not infer an installment schedule merely because a historical transaction was partially paid or had several payments; create historical plan rows only when the source contains explicit schedule terms. Reconcile a sample from registration to participant, household purchaser, ticket product, receipt line, sale payments, receipt balance, and any verified plan before enabling customer access or automation.",
        "For an API-created plan, POST /event-registration-payment-plans with sale_id, starts_on, interval_unit, interval_count, installment_count, and optional plan_name. Reuse the same Idempotency-Key for an uncertain retry. A new plan returns 201; a database-level replay can return 200. The result is the same receipt-backed invoice plan used by normal CentriPOS A/R, with bounded cancellation-reason-free registration links—not a duplicate event payment ledger.",
        "Use POST /event-registration-payment-plans/{registration_payment_plan_id}/pause, /resume, or /cancel with an optional 1–1000 character reason. Each returns the safe plan projection plus requested_status, prior_status, and lifecycle_result. These commands require both registration-write and invoice-write permission and never create sale_payments, mark an installment paid, refund a receipt, or imply card-on-file consent.",
        "Use POST /event-registration-payment-plans/{registration_payment_plan_id}/send-customer-link with optional installment_id and expires_minutes from 5 through 10,080. The returned customer_payment_link contains only a trusted tenant-bound HTTPS receipt URL, suggested amount, canonical expiry, reuse state, and ready_for_delivery status. The caller chooses an authorized delivery channel; the API response does not itself send a message. A replay under the same Idempotency-Key returns only the exact unchanged still-live capability. Expiry, token rotation, plan completion or cancellation, remaining-balance drift, or installment amount/status drift fails closed; after resolving the current state, submit the intended request with a new Idempotency-Key instead of accepting stale link data.",
        "When a configured post-grace policy releases capacity, CentriPOS records the admission-released state, cancels only the affected payment-plan registrations, voids their credentials, and atomically releases their preserved daypart or session occurrence selections and physical seat assignments. A late payoff settles the receipt but does not silently reclaim capacity. Staff must use the explicit reinstatement command after the current authoritative receipt balance is zero; the command locks and rechecks live registration, occurrence, and physical-seat availability, restores only the registrations, selections, and original still-available seats released for that receipt, restores or issues tickets, and fails closed without partial restoration if any required capacity is no longer available.",
        "Treat payment-link expiration as returned data, not a promise calculated from the request. requested_expires_minutes applies only when CentriPOS must create a new canonical receipt token. If a still-live canonical token is reused, the returned expires_at is its actual existing expiry and the request neither extends nor shortens it. Idempotent replay is deliberately state-bound: only the same unchanged still-live capability can replay. Expiry, token rotation, plan completion or cancellation, balance drift, or installment drift fails closed and requires a new Idempotency-Key for the intended current request. The scheduled installment in payment_url is only a payment_amount prefill on the ordinary receipt page; the customer may pay that amount, the full balance, or another valid partial amount.",
        "Use POST /event-registration-payment-plans/{registration_payment_plan_id}/reinstate-admission only after the authoritative receipt balance is zero and live capacity has been reviewed. Admission reinstatement returns lifecycle_result plus safe registrations_reinstated, occurrence_enrollments_reinstated, seats_reinstated, and tickets_issued counts. A successful first command reports the work performed; an idempotent replay reports lifecycle_result replayed and may return null counts. Customer portal and staff registration summaries continue to show admission released until the atomic command succeeds."
      ],
      "controls": [
        {
          "name": "Event payment-plan policy",
          "description": "Offering-level or ticket-specific rules for deposit, installments, capacity, admission, grace, delinquency, and customer selection."
        },
        {
          "name": "Shared receipt ledger",
          "description": "sales carries the total and balance, sale_payments carries tender evidence, and no event table duplicates a payment."
        },
        {
          "name": "Deposit",
          "description": "Server-calculated amount due at checkout before the remaining schedule is activated."
        },
        {
          "name": "Amount due today",
          "description": "Authoritative deposit for a plan or the full total for Pay in full."
        },
        {
          "name": "Installment schedule",
          "description": "Remaining cent-exact amounts and due dates stored through the normal invoice-plan foundation."
        },
        {
          "name": "Final due offset",
          "description": "Optional rule requiring the last installment a configured number of days before the event begins."
        },
        {
          "name": "Grace period",
          "description": "Time after a due date before an unpaid installment makes the plan delinquent under its policy."
        },
        {
          "name": "Capacity policy",
          "description": "Whether a successful deposit reserves capacity, releases it after grace, or requires staff review."
        },
        {
          "name": "Admission policy",
          "description": "Whether an active current plan is sufficient for entry or the receipt must be paid in full."
        },
        {
          "name": "Delinquency policy",
          "description": "Manual review, portal pause, or approved post-grace cancellation behavior; it does not make a future balance past due."
        },
        {
          "name": "payment_plan_active",
          "description": "Storefront order has a successful deposit and an active schedule for its remaining receipt balance."
        },
        {
          "name": "Receipt-backed A/R invoice",
          "description": "Customer-account mirror of the same sale, not another sale or payment ledger."
        },
        {
          "name": "Plan status",
          "description": "Draft, Active, Paused, Delinquent, Completed, or Canceled."
        },
        {
          "name": "Installment status",
          "description": "Scheduled, Due, Processing, Paid, Failed, or Canceled."
        },
        {
          "name": "One household plan",
          "description": "One sale-level balance shared by all registrations on the receipt; reports and portal views must not multiply it by camper count."
        },
        {
          "name": "Customer-initiated payment",
          "description": "Approved tender entered through a branded receipt or account payment path and then allocated to the schedule."
        },
        {
          "name": "Auto-collection consent",
          "description": "Separate, timestamped permission tied to a supported saved method; enabling a policy is not consent."
        },
        {
          "name": "event-payment-plan-policies",
          "description": "Authenticated-live policy resource for entitled tenants: GET/POST collection and GET/PATCH/DELETE item operations under event scopes."
        },
        {
          "name": "event-registration-payment-plans",
          "description": "Authenticated-live receipt-backed plan lifecycle: three dual-read-scope GET routes plus idempotent create, pause, resume, cancel, send-customer-link, and reinstate-admission commands under events:registrations:write plus invoices:write. Commands cannot mark paid or auto-charge."
        },
        {
          "name": "Payment-plan webhook",
          "description": "Signed, retryable lifecycle notification with a complete scalar safe snapshot; policy objects use events:read and registration-plan objects use invoices:read."
        },
        {
          "name": "HighLevel payment-plan action",
          "description": "Bounded authoritative command for plan creation or lifecycle communication; never a command to mark money paid."
        },
        {
          "name": "Historical schedule caveat",
          "description": "Multiple Event Espresso payment rows or an open balance prove payment history, not agreed future installment dates."
        },
        {
          "name": "Controlled rollout",
          "description": "The API routes are registered for entitled tenants; staff UI, customer experience, tenant rollout, webhook subscriptions, and HighLevel Marketplace activation must still each be verified."
        },
        {
          "name": "Payment-plan command scopes",
          "description": "events:registrations:write plus invoices:write are required together for create, pause, resume, cancel, send-customer-link, and reinstate-admission; every command also requires Idempotency-Key."
        },
        {
          "name": "payment_adjacent",
          "description": "Rate-limit and audit class for all six receipt-plan lifecycle commands; none is a mark-paid or automatic-charge operation."
        },
        {
          "name": "Admission released",
          "description": "Capacity and credentials were released under the plan policy; receipt payoff alone does not reactivate attendance."
        },
        {
          "name": "reinstate-admission",
          "description": "Idempotent paid-in-full, live-capacity-checked command with a required 1–1000 character audit reason; it restores the receipt registrations, daypart/session selections, original still-available physical seats, and tickets atomically."
        },
        {
          "name": "Canonical payment-link expiry",
          "description": "The returned expires_at is authoritative; requested TTL applies only when a new receipt token is created."
        },
        {
          "name": "Suggested installment amount",
          "description": "payment_amount prefill on the ordinary receipt link, not a forced charge; the customer may choose scheduled, full, or another valid partial amount."
        },
        {
          "name": "Pending payment",
          "description": "Unsettled processor attempt that does not count as collected cash, plan completion, receipt paid-in-full, or admission eligibility."
        }
      ],
      "expectedResult": "The deposit, receipt total, completed sale payments, remaining balance, installment allocations, customer-account invoice, registration links, capacity behavior, and reported plan status reconcile to the cent; the customer can understand and operate the enabled payment path; and no event, API, webhook, HighLevel, or imported-history record fabricates a payment or schedule.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "api-center",
      "url": "https://platform.getcentri.com/centripos/api-center",
      "title": "Manage API Clients, Keys, and Webhooks",
      "summary": "Create tenant-bound integration clients, issue one-time restricted keys, control live and test access, subscribe signed endpoints to approved events, and audit every request and delivery.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → API Center is the merchant control plane for private CentriPOS integrations. Access is subscription- and rollout-gated. A credential is bound to the current company, one client, one environment, and explicit scopes; callers never supply a tenant ID or data-plane route. Raw key and signing-secret values are shown once.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → API Center and confirm the company name in the global header before doing anything. API resources are isolated to that selected company. The capacity row says Up to and describes plan limits, not existing clients, keys, or endpoints.",
        "Read the entitlement banner. Developer API not included means new credentials and operational delivery are blocked. Live access included permits approved read requests against the active dedicated data plane. Test access requires an assigned isolated preview data plane; it never falls back to live.",
        "Create a separate integration client for each external application, agency, or automation. Enter an owner-readable name and purpose. Select only the default scopes the integration genuinely needs. A client is an administrative boundary, not a secret by itself.",
        "Treat read and write scopes separately. Event integrations use events:read/write for offerings and publication, events:registrations:read/write for enrollment records, events:attendance:read/write for atomic attendance, events:credentials:read/write for ticket credential issuance and lifecycle, and events:sensitive:read/write only for specifically authorized protected participant, answer, or consent data. Calendar, reports, audit, webhooks, and every other domain have separate scopes. Controlled operations remain disabled until their operation-specific rollout gate passes.",
        "Issue a key from the intended client. Choose Test or Live only when the matching environment is approved, give the key a narrow name, review its scopes, and set an expiration appropriate to the integration. Never grant cost, sensitive-event, or attendance-credential scopes unless the caller genuinely needs them.",
        "Capture the raw key from the one-time reveal into the integration’s server-side secret manager. Do not put it in browser JavaScript, a mobile bundle, source control, analytics, screenshots, tickets, URLs, query strings, or the public support-site explorer. CentriPOS retains only a keyed digest, prefix, last four, environment, scope, and lifecycle metadata.",
        "Call the branded https://pos.getcentri.com/api/retail/v1 base from the integration server using Authorization: Bearer <restricted key> and Accept: application/json. Do not send a tenant ID, Supabase hostname, project reference, database route, or service-role credential.",
        "Use the date-pinned Retail API OpenAPI contract on support.centripos.com. Operations marked Authenticated live are available only to explicitly entitled tenants with the required scope. Controlled rollout operations remain documented but fail closed until enabled.",
        "For every response, record X-Request-ID and the HTTP status. A 401 means the credential is missing, malformed, expired, or revoked. A 403 means the key is valid but lacks scope or tenant policy. A 503 operation_not_enabled means the contract exists but execution is still gated.",
        "Open Request log to inspect the admitted request ID, client, key, environment, version, operation, scope, method, route template, result, duration, response size, rate-limit decision, idempotency result, safe user-agent metadata, and error code. Request bodies, response payloads, and raw credentials are not stored in this log.",
        "Create a webhook endpoint under the client only after the receiving HTTPS service is ready. Give it a clear name, choose the correct environment, enter the exact HTTPS URL, and subscribe only to the event types that company has authorized. Operational events require the matching subscription entitlement and the client must retain the matching resource-read scope.",
        "Capture the one-time signing secret in the receiver’s secret manager. Read CentriPOS-Signature in t=<timestamp>,v1=<hex> form and verify HMAC-SHA256 over <timestamp>.<exact raw JSON body> before parsing or trusting the body. Enforce the replay window, deduplicate the immutable event ID, and correlate CentriPOS-Delivery-ID, CentriPOS-Event, and CentriPOS-API-Version.",
        "Event and calendar webhook bodies include the complete allowlisted scalar safe snapshot for that resource inline in data.object, plus changed_fields when supplied and a branded resource_url when an item route exists. They never embed arbitrary JSON metadata, registration answers, medical or accessibility details, waiver signature evidence, ticket credentials, payment data, or portal secrets. Deleted resources are identity-only tombstones. General or legacy domain webhooks may still use bounded notification projections; inspect the event-specific OpenAPI contract.",
        "Use resource_url with a separately scoped key when the receiver needs a fresher or broader supported representation. The inline event snapshot is immutable delivery evidence, not a substitute for scope-gated retrieval and never permission to query internal tables.",
        "Use the delivery log to inspect queued, succeeded, retrying, and failed attempts. Test sends a synthetic webhook.test event. Runtime delivery treats 2xx as success and makes up to six total attempts with bounded exponential backoff and jitter. Retry only after the receiver is corrected; consumers must remain idempotent because legitimate retries retain the same event ID.",
        "Pause an endpoint before planned receiver maintenance and resume it only when signature verification and idempotency are healthy. Rotate a webhook signing secret deliberately and update the receiver during the supported overlap. Disable endpoints no longer owned by an active integration.",
        "Rotate or revoke an API key immediately when it may have been exposed, an integration changes ownership, or its scope is no longer appropriate. Revocation is immediate and does not delete immutable request history. Issue the replacement first only when an approved overlap is required.",
        "Keep one client per integration and one narrowly scoped key per environment. Do not share a merchant, agency, or platform credential with another tenant. Branding, subscription entitlement, environment, rate limits, audit history, and webhook subscriptions all remain attached to the exact selected company.",
        "Before certifying an integration, verify missing-key rejection, wrong-scope rejection, test/live isolation, tenant isolation, rate limiting, expiration and revocation, complete supported payload shape, request-log correlation, webhook signature rejection, retry deduplication, and fail-closed mutations."
      ],
      "controls": [
        {
          "name": "Current company",
          "description": "Global company context that owns every client, key, endpoint, request log, and delivery visible on the page."
        },
        {
          "name": "Plan capacity",
          "description": "Up to limits for clients, active keys, and webhook endpoints; not a count of resources already created."
        },
        {
          "name": "Integration client",
          "description": "Tenant-bound administrative container for one external application or automation."
        },
        {
          "name": "Default scopes",
          "description": "Least-privilege permissions proposed when keys are issued under the client."
        },
        {
          "name": "Test environment",
          "description": "Restricted key routed only to an assigned isolated preview data plane."
        },
        {
          "name": "Live environment",
          "description": "Restricted key routed only to the company’s approved active dedicated data plane."
        },
        {
          "name": "One-time key reveal",
          "description": "Only opportunity to capture the raw cp_test_ or cp_live_ secret; CentriPOS stores a keyed digest rather than the raw value."
        },
        {
          "name": "Expiration",
          "description": "Optional key lifetime boundary; expired keys fail authentication."
        },
        {
          "name": "Revoke",
          "description": "Immediately disables the key while preserving immutable audit history."
        },
        {
          "name": "Authenticated live",
          "description": "Operation available only for an explicitly entitled tenant and correctly scoped key."
        },
        {
          "name": "Controlled rollout",
          "description": "Documented operation that remains fail-closed until its independent activation gates pass."
        },
        {
          "name": "Request log",
          "description": "Append-only safe metadata for admitted and rejected API activity; no raw keys, request bodies, or response payloads."
        },
        {
          "name": "Webhook endpoint",
          "description": "Tenant- and client-bound HTTPS receiver subscribed to explicit approved event types."
        },
        {
          "name": "Signing secret",
          "description": "One-time HMAC secret used by the receiver to authenticate CentriPOS webhook deliveries."
        },
        {
          "name": "webhook.test",
          "description": "Synthetic event used to verify endpoint connectivity and signature handling."
        },
        {
          "name": "Delivery log",
          "description": "Attempt status, response, timing, retry, and error metadata for signed webhook delivery."
        },
        {
          "name": "Event safe snapshot",
          "description": "Complete event-specific allowlisted scalar projection embedded in data.object; protected, credential, payment, arbitrary JSON, and portal-secret fields are excluded."
        },
        {
          "name": "Deleted tombstone",
          "description": "Identity-only deleted-resource object with id, object, optional changed_fields, and resource_url."
        },
        {
          "name": "Resource URL",
          "description": "Branded Retail API URL used with a separately scoped key to retrieve the current supported resource."
        },
        {
          "name": "No exact screenshot",
          "description": "The public guide intentionally contains no real merchant key, endpoint URL, signing secret, request log, or private payload capture."
        }
      ],
      "expectedResult": "This workflow is complete only after CentriPOS reflects the intended result. Final checkpoint: Before certifying an integration, verify missing-key rejection, wrong-scope rejection, test/live isolation, tenant isolation, rate limiting, expiration and revocation, complete supported payload shape, request-log correlation, webhook signature rejection, retry deduplication, and fail-closed mutations.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "label-templates",
      "url": "https://platform.getcentri.com/centripos/label-templates",
      "title": "Create and manage label templates",
      "summary": "Build reusable product, sale, shipping, or general label layouts; set physical dimensions; place text, barcode, shape, check, scale, and logo elements; and safely control default and category-specific templates.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Label Templates",
      "introduction": "Admin → Labels uses the Tags icon. Templates are tenant configuration. Saving a Product template can also change category assignments, and making a template default changes which layout CentriPOS selects for that source, so verify both the template and its scope before operational printing. The approved Harbor & Hearth capture set has no exact Labels screen, so this guide does not substitute a different settings image.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Labels. Confirm the active business before editing. The table identifies each template by name, default state, source, physical size, and Active or Inactive status.",
        "Choose New template, then start with Barcode label (2.25 × 1.25 inches) or Price tag (4 × 6 inches). Enter a clear name. The first saved template for a source becomes its default; new Product templates begin active.",
        "Under Setup, choose the source: Product, Sale, Shipping, or General. Select a size preset or Custom, then enter positive width and height values. Use Swap orientation when the stock is correct but portrait and landscape are reversed.",
        "Set horizontal and vertical print offsets only after a measured test. Offsets move the entire printed layout and should correct printer alignment, not compensate for misplaced individual elements. Choose the intended background color.",
        "For a Product template, choose its product categories when this layout should override the normal Product default. Saving removes those categories from other Product templates to prevent overlapping assignments, so review the full category list before saving.",
        "Add elements from the canvas toolbar: Text, Barcode, Line, Box, Check, Scale, or Logo. Select an element to edit its X and Y position plus width and height. Keep every element inside the physical label boundary.",
        "For Text, enter fixed wording or supported data bindings/tokens, then set font, size, weight, style, alignment, and color. Print a test using a representative record so long names, prices, addresses, or identifiers do not clip.",
        "For Barcode, choose the intended value and barcode settings. Make the element large enough for the printer resolution and scanner, leave usable quiet space, and validate the printed code against the source record before production use.",
        "Configure Line and Box elements for separation or borders. Use Check and Scale only when those marks match the business workflow. For Logo, choose the current store logo, upload an approved asset, or use an authorized image URL; confirm the logo remains legible at final print size.",
        "Choose Save. CentriPOS requires a name and positive dimensions. If the template is marked default, saving clears the previous default for the same source. A category-assignment warning can occur after the template itself saved, so read the result and verify both records instead of saving repeatedly.",
        "Use Duplicate to create an editable copy without risking the working template. Use Export JSON to download a portable definition and Import JSON only for a trusted CentriPOS template file; inspect imported dimensions, source, elements, and bindings before activating it.",
        "Choose Make default only when this should be the fallback template for that source. The action activates the template and replaces the prior default. Reopen the list and verify the Default badge.",
        "Choose Delete only after confirming the named template and its replacement. The delete confirmation is destructive. Do not remove the only operational template or a default until another tested layout is ready.",
        "Run a non-customer test print on the actual printer and stock. Verify orientation, margins, text, logo, barcode scan, data bindings, category routing, and default selection before using the template in live product, sale, or shipping work.",
        "No screenshot is published because the approved Amelia Grant Harbor & Hearth manifest contains no exact /admin/labels capture. Receipt Templates or another Admin screen would be misleading and is not used."
      ],
      "controls": [
        {
          "name": "Tags icon",
          "description": "Exact Admin navigation icon for Labels."
        },
        {
          "name": "Template table",
          "description": "Shows name/default, source under Use for, physical size, and Active or Inactive state."
        },
        {
          "name": "Barcode label starter",
          "description": "Creates a 2.25 × 1.25 inch starter Product template."
        },
        {
          "name": "Price tag starter",
          "description": "Creates a 4 × 6 inch starter Product template."
        },
        {
          "name": "Source",
          "description": "Product, Sale, Shipping, or General data context used by the layout."
        },
        {
          "name": "Size preset / Custom",
          "description": "Physical label dimensions; width and height must be positive."
        },
        {
          "name": "Offsets",
          "description": "Whole-layout horizontal and vertical print adjustments."
        },
        {
          "name": "Swap orientation",
          "description": "Exchanges width and height."
        },
        {
          "name": "Product categories",
          "description": "Routes selected categories to this Product template and removes conflicts from other Product templates on save."
        },
        {
          "name": "Canvas",
          "description": "Physical design surface containing positioned label elements."
        },
        {
          "name": "Text",
          "description": "Fixed copy or supported record binding with typography and alignment controls."
        },
        {
          "name": "Barcode",
          "description": "Machine-readable element whose value, size, print quality, and scan result must be tested."
        },
        {
          "name": "Line / Box",
          "description": "Visual separator and border elements."
        },
        {
          "name": "Check / Scale",
          "description": "Workflow-specific mark elements."
        },
        {
          "name": "Logo",
          "description": "Current store logo, approved upload, or authorized image URL."
        },
        {
          "name": "Duplicate",
          "description": "Creates a copy for safe editing."
        },
        {
          "name": "Import JSON",
          "description": "Loads a trusted portable CentriPOS template definition for inspection."
        },
        {
          "name": "Export JSON",
          "description": "Downloads the current template definition."
        },
        {
          "name": "Make default",
          "description": "Activates the template and replaces the previous default for the same source."
        },
        {
          "name": "Delete",
          "description": "Permanently removes the confirmed template."
        },
        {
          "name": "Partial category warning",
          "description": "Template save succeeded but category synchronization had a problem; verify before retrying."
        },
        {
          "name": "No exact screenshot",
          "description": "No approved Harbor & Hearth Labels capture exists; no substitute is published."
        }
      ],
      "expectedResult": "This workflow is complete only after CentriPOS reflects the intended result. Final checkpoint: No screenshot is published because the approved Amelia Grant Harbor & Hearth manifest contains no exact /admin/labels capture. Receipt Templates or another Admin screen would be misleading and is not used.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "projects-work",
      "url": "https://platform.getcentri.com/centripos/projects-work",
      "title": "Manage service projects and work items",
      "summary": "Organize work across stable reporting stages, control project access, link contacts and invoices, and distinguish internal notes from requester-visible updates.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Service",
      "introduction": "Service → Projects opens the Projects & Work workspace for the active business. Workspace projects follow normal access rules; Restricted projects are visible only to owners, super admins and assigned users. Connected customers, invoices and service jobs provide context without changing billing.",
      "beforeYouBegin": "Confirm the active business, project and permitted audience. Only authorized project managers should change access, public intake or notification settings. Customer tracking links and external updates can expose project information.",
      "steps": [
        "Go to Service → Projects and confirm the active business. Read Active projects, At risk, Due soon and Open work. Open work excludes Done and Cancelled items; Due soon covers the next seven days and excludes completed/cancelled projects.",
        "Choose an existing project from the newest-updated list or choose New project. On phone layouts, selecting a project moves from the project list into its workspace; use the back control to return.",
        "For a new project, enter the required Name, optional Description, Type, Health, Due date, and an assigned Location when appropriate. Types include Service, Implementation, Retainer, Digital, Marketing, Installation, Internal, and Other. New projects begin in Planned status and use the effective profile as owner/creator.",
        "Open Project settings to manage visibility and relationships. Owners and super admins can change Workspace versus Restricted visibility and assigned-user membership. Confirm everyone who must operate a restricted project is assigned. Choose the project location deliberately because communication delivery uses its provider settings before storefront defaults.",
        "Search and connect the exact customer/contact. Connected contacts provide identity context and become eligible for work-item relationships. Disconnecting a contact removes only the project link; it does not delete or edit the customer.",
        "Under Suggested invoices, review invoices for connected contacts and link only records that belong to this project. Linking or unlinking a contact/invoice does not change invoice status, balance, accounting sync or collection. Use Linked jobs to open related service work in its own job workspace.",
        "Choose Work item. Enter the required Title plus optional Description, Type, Priority, staff Assignee, Related contact, and Due date/time. Item types include Task, Service, Visit, Deliverable, Approval, Bug, Follow-up, Recurring, and Other.",
        "Use Board to move work among Backlog, Ready, In progress, Blocked, Review, and Done. Drag a card to the intended list and verify the updated status. Cancelled is available from item detail but is not a normal board column.",
        "Use Lists to rename the project board columns. The visible terminology changes, but each column keeps its stable reporting status key. Do not rename columns in a way that reverses the meaning of Backlog, Review, Done, or another reporting stage.",
        "Use Milestone to add a title and optional due date. The Milestones tab shows stored status and due date; the current visible screen provides creation and display, not a general milestone edit/delete workflow.",
        "Use List for a compact work-item view. Open an item to review item number, title, status, assignee, due time, description, checklist, approvals, and comments. Changing Status writes immediately, so verify the chosen stage before closing.",
        "Add checklist items as concrete completion steps. Choosing an item toggles its complete state and completion time. Checklist progress supports the work record; it does not automatically move the parent item to Done.",
        "Request an approval by choosing an approver and optional note. A pending approval can be Approved or Rejected from the item detail. Verify the named approver and decision because this is durable project evidence, not a private draft.",
        "Use Updates and choose Internal note or External update before posting. Internal notes are for the team; External updates are visible to the requester on the private tracking page. Check the audience and remove credentials, payment data and unrelated customer details before choosing Post update.",
        "When an authorized requester needs a tracking link, enter the correct Requester name and Requester email in Updates, then choose Tracking link. Verify the generated link and recipient through your approved delivery process. Keep private tracking links out of public screenshots and general messages.",
        "In Project settings, use Public ticket intake only when an authorized manager intends to expose a project-specific intake form. Create intake link or Rotate intake link generates a revocable URL, and each submitted ticket becomes a work item with its own private tracking link. Review where the intake URL will be distributed before sharing it.",
        "If New support ticket notifications is shown for the project, review the exact active recipient and enabled in-app, email or SMS channels. Channel availability and recipient contact details limit the choices; changing a notification setting is not proof that a future message was delivered.",
        "After creating, moving, linking, changing access or posting an update, reopen the project and verify the exact record and audience. Use the linked service job, customer, invoice, receipt or accounting screen to verify operational results outside the project."
      ],
      "controls": [
        {
          "name": "FolderKanban icon",
          "description": "Current Service → Projects navigation icon."
        },
        {
          "name": "Active projects",
          "description": "Loaded projects whose status is Active."
        },
        {
          "name": "At risk",
          "description": "Projects whose health is At risk or Off track."
        },
        {
          "name": "Due soon",
          "description": "Noncompleted/noncancelled projects due within seven days."
        },
        {
          "name": "Open work",
          "description": "Tenant work items whose status is not Done or Cancelled."
        },
        {
          "name": "New project",
          "description": "Creates a Planned project with name, description, type, health, location, owner, and due date."
        },
        {
          "name": "Workspace visibility",
          "description": "Project available under normal tenant access rules."
        },
        {
          "name": "Restricted visibility",
          "description": "Visible only to owners, super admins, and assigned project members."
        },
        {
          "name": "Project settings",
          "description": "Visibility, project location, assigned users, public intake, support alerts, connected contacts and invoice references."
        },
        {
          "name": "Connected contact",
          "description": "Project relationship to an existing customer/contact; disconnect does not delete the contact."
        },
        {
          "name": "Suggested invoices",
          "description": "Invoices belonging to connected contacts; linking does not change billing status."
        },
        {
          "name": "Work item",
          "description": "Task, service, visit, deliverable, approval, bug, follow-up, recurring, or other unit of work."
        },
        {
          "name": "Priority",
          "description": "Low, Normal, High, or Urgent item priority."
        },
        {
          "name": "Team assignee",
          "description": "Active tenant profile responsible for the item, or Unassigned."
        },
        {
          "name": "Related contact",
          "description": "One of the contacts already connected to the project."
        },
        {
          "name": "Board",
          "description": "Status-based workflow view with draggable work-item cards."
        },
        {
          "name": "Stable status key",
          "description": "Backlog, Ready, In progress, Blocked, Review, Done, or Cancelled reporting meaning retained when a list is renamed."
        },
        {
          "name": "Milestones",
          "description": "Project checkpoints with stored title, status, and optional due date."
        },
        {
          "name": "List",
          "description": "Compact row view of project work items."
        },
        {
          "name": "Checklist",
          "description": "Independent completion steps; toggling one does not complete the parent automatically."
        },
        {
          "name": "Approvals",
          "description": "Pending durable request that an approver can Approve or Reject."
        },
        {
          "name": "Updates",
          "description": "Choose Internal note for the team or External update for the requester tracking page before posting."
        },
        {
          "name": "Tracking link",
          "description": "Generated for the selected work item and named requester; treat the link as private."
        },
        {
          "name": "Public ticket intake",
          "description": "Authorized project-specific intake link creation/rotation; submitted tickets become work items."
        },
        {
          "name": "Support ticket notifications",
          "description": "Conditional recipient/channel settings; delivery requires working provider configuration."
        },
        {
          "name": "Linked jobs",
          "description": "Opens related service jobs without changing their billing or completion state."
        }
      ],
      "expectedResult": "The intended project has correct access, work stages, assignees and relationships, and each note/update uses the intended internal or requester audience. Project links remain distinct from invoice/payment outcomes.",
      "troubleshooting": [
        "If a project is missing, check the active business and Restricted visibility membership before creating a replacement.",
        "If a contact or invoice is unavailable, verify the connected customer and intended project; do not link a similar record merely to complete a form.",
        "If a public or private link fails, inspect its current lifecycle and request a fresh authorized link; do not edit capability tokens.",
        "If a notification is not delivered, check recipient/channel availability and original provider evidence before resending."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sign-in",
      "url": "https://platform.getcentri.com/centripos/sign-in",
      "title": "Sign in to CentriPOS",
      "summary": "Use the Google identity or email-and-password Centri Account established from your personal business invitation, then enter only the business and operating context assigned to that identity.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Signing in",
      "introduction": "CentriPOS access is invitation-only. The current production screen offers Continue with Google and email-and-password sign-in; neither option creates a public self-service account. A successful sign-in clears the browser’s previous CentriPOS tenant, location, register, proxy-user, and register-session selections before loading the invited identity, which helps prevent an old operating context from carrying into the new session.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Open https://pos.getcentri.com. When no valid session is present, CentriPOS opens the branded CentriPOS Sign in to your account screen at /login. Confirm the host is pos.getcentri.com before entering or choosing an identity.",
        "Use Continue with Google when the invited Centri Account is tied to that Google email. Complete the Google account choice only on Google’s authentic sign-in surface, then return to CentriPOS. Google authentication does not add a business membership or bypass the invitation requirement.",
        "To use a Centri Account password instead, enter the exact invited Email address. CentriPOS trims spaces and normalizes the address to lowercase before authentication; this does not create an account for a similar or alternate address.",
        "Enter the Centri Account Password. Choose the eye control to Show password only when the screen and surrounding area are private, then hide it again before sharing or capturing the screen.",
        "Choose Sign in once. The button shows a loading indicator while CentriPOS clears the previous browser context and authenticates the entered identity. Do not repeatedly submit, refresh, or switch browsers while it is working.",
        "If Login failed appears, read the message without exposing it alongside the password. Confirm the invited address first, then use Forgot password? when the password is unknown. A reset changes an existing credential; it does not create a missing invitation or membership.",
        "If Google or another identity path returns an account that does not match an active invited CentriPOS profile, stop and return to the login screen. Choose the intended Google account or use the exact invited email rather than continuing under a different identity.",
        "After authentication, Choose your business appears when more than one active business membership is available. Select only the business whose customer, inventory, payment, and reporting data you intend to use.",
        "Choose the location and register required for the workflow. A location with one active register can be selected automatically; otherwise choose the register explicitly. An open register routes to Sell, while a closed register routes to Session Control.",
        "Before any operational action, confirm the signed-in identity in User Hub and verify the business, location, register, and session state in the application header. Use Switch or Sign out / switch user when any part of that context is wrong."
      ],
      "controls": [
        {
          "name": "CentriPOS logo",
          "description": "The official CentriPOS mark at the top of the branded sign-in card."
        },
        {
          "name": "Continue with Google",
          "description": "Authenticates an invited Centri Account through Google; it does not self-register a user or grant a business membership."
        },
        {
          "name": "or use email",
          "description": "Divider between Google authentication and the Centri Account email/password form."
        },
        {
          "name": "Email",
          "description": "Exact address connected to the invitation and active CentriPOS profile; spaces are trimmed and capitalization is normalized for sign-in."
        },
        {
          "name": "Password",
          "description": "Centri Account password; the eye control shows or hides the entered value."
        },
        {
          "name": "Sign in",
          "description": "Clears prior browser account context, authenticates the credential, and loads the active CentriPOS memberships for that identity."
        },
        {
          "name": "Loading indicator",
          "description": "Shows that the sign-in request is still running; it is not a prompt to submit again."
        },
        {
          "name": "Login failed",
          "description": "Authentication was not accepted; use the displayed message and the password-recovery flow without sharing credentials."
        },
        {
          "name": "Wrong Google identity",
          "description": "An authenticated Google account still needs an active invited CentriPOS profile for the matching email. Return and choose the intended identity when access does not match."
        },
        {
          "name": "Forgot password?",
          "description": "Changes the card to the email reset request. A successful request shows Check your email and sends a branded recovery link."
        },
        {
          "name": "Access is by invitation only",
          "description": "A business administrator must invite the user; the public login screen does not provide self-registration."
        },
        {
          "name": "Terms / Privacy / Support",
          "description": "Open the current Centri legal and help destinations from the sign-in footer."
        },
        {
          "name": "Choose your business",
          "description": "Appears when the account can enter more than one active Centri business membership."
        },
        {
          "name": "Choose a location",
          "description": "Lists active locations for the selected business and may show address, contact, register-count, and open-register information."
        },
        {
          "name": "Choose a register",
          "description": "Lists active registers and their latest open or closed session state; a single register can be selected automatically."
        },
        {
          "name": "Business, location, register, and session context",
          "description": "Operational scope chosen after authentication; it remains separate from proving the account identity."
        },
        {
          "name": "No public screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth capture set does not contain a safe exact sign-in image, so this guide intentionally uses no substituted or fabricated screenshot."
        }
      ],
      "expectedResult": "CentriPOS accepts the invited identity and opens either the authorized business picker or the permitted workspace. The business, location, and register shown next must match the access granted to that account.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "choose-store-location-register",
      "url": "https://platform.getcentri.com/centripos/choose-store-location-register",
      "title": "Choose a business, location, and register",
      "summary": "Set the Centri business, physical or operational location, active register, and register-session context that will scope customer, inventory, payment, fulfillment, and reporting work.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Getting oriented",
      "introduction": "Authentication proves who you are. Active business memberships, locations, registers, role permissions, and the latest register-session status determine where the account can work and where CentriPOS sends it next. Selecting a context never grants access that the administrator did not assign.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "When the account has multiple active business memberships, CentriPOS opens Choose your business after sign-in. Confirm the Signed in as email, then choose the exact business whose data you intend to use. Each card shows its business name, your profile display name, available logo, and Platform or Agency label when applicable.",
        "When four or more businesses are available, use Search businesses and the List view or Grid view control. The result count reflects the current search. This business-picker view choice is temporary on the page; unlike the later location and register selectors, it has no Set as default control.",
        "Choose Sign out if the email at the top is wrong. Selecting a business saves that membership as the active tenant and continues to Choose a location; it does not open or select a register by itself.",
        "On Choose a location, first verify the business logo or name and Welcome display name. Cards include the location name and can show address, phone, email in list view, total active register count, and how many registers currently have an open session.",
        "Use List view or Grid view as preferred. Set as default stores only this location-selector layout in the current browser; it does not choose a default location. Search locations appears only when more than four active locations exist and matches the location name or address.",
        "Choose the physical or operational location where the work belongs. CentriPOS then opens Choose a register with that location named at the top. If No locations configured yet appears, an administrator must create or activate a location; search filters cannot reveal an inactive or unauthorized record.",
        "On Choose a register, use Search registers at any register count, switch between List and Grid, or use Set as default to store only that selector layout. Choose Back to locations when the named location is wrong.",
        "If exactly one active register exists at the selected location, CentriPOS automatically stores the location/register context and routes onward without showing a choice. With multiple registers, each card can show Open or Closed plus the latest opened/closed date and staff name when session data exists.",
        "Selecting a register records a register_switch activity event. When its latest session is Open, CentriPOS routes to Register → Sell. When the latest session is closed or absent, it routes to Register → Session Control so the register can be reviewed or opened by an authorized user.",
        "Confirm the business, location, register, and open/closed state in the operating-context bar before starting a sale, taking payment, moving inventory, changing fulfillment, or reading a scoped report. Use Switch for a different location/register and User Hub → Switch store for a different business membership."
      ],
      "controls": [
        {
          "name": "Choose your business",
          "description": "Branded business-membership selector shown when the account must choose among multiple active Centri tenants."
        },
        {
          "name": "Signed in as",
          "description": "Email of the authenticated Centri Account; use Sign out when it is not the intended identity."
        },
        {
          "name": "Business card",
          "description": "Shows the tenant logo or building icon, business name, the membership profile display name, and Platform or Agency type when applicable."
        },
        {
          "name": "Search businesses",
          "description": "Appears with four or more business options and matches business name or profile display name."
        },
        {
          "name": "Business List / Grid",
          "description": "Temporary layout control on the business picker; it is not saved as a default."
        },
        {
          "name": "Choose a location",
          "description": "Lists active locations for the selected business and displays its tenant branding."
        },
        {
          "name": "Location card",
          "description": "Shows the location name and supported address, phone, email, active-register count, and open-register count; grid view contains a more compact subset."
        },
        {
          "name": "Search locations",
          "description": "Appears only when more than four active locations exist and matches name or address."
        },
        {
          "name": "Location List / Grid",
          "description": "Changes the selector layout without changing access."
        },
        {
          "name": "Location Set as default",
          "description": "Stores only the current list-versus-grid preference in this browser."
        },
        {
          "name": "No locations configured yet",
          "description": "No active location rows were returned for the selected business; an administrator must configure access or records."
        },
        {
          "name": "Choose a register",
          "description": "Lists active registers belonging to the location named at the top."
        },
        {
          "name": "Search registers",
          "description": "Matches the active register name and is available even when only a few registers exist."
        },
        {
          "name": "Register List / Grid",
          "description": "Changes the register selector layout without changing access."
        },
        {
          "name": "Register Set as default",
          "description": "Stores only the register selector’s list-versus-grid preference in this browser."
        },
        {
          "name": "Back to locations",
          "description": "Returns to the location selector without signing out."
        },
        {
          "name": "Single active register",
          "description": "Automatically selected after its latest session status is checked."
        },
        {
          "name": "Open",
          "description": "Latest register session is open; selection routes to Sell."
        },
        {
          "name": "Closed or no prior session",
          "description": "Selection routes to Session Control."
        },
        {
          "name": "Register activity event",
          "description": "CentriPOS records the selected register and location, including whether a one-register choice was automatic."
        },
        {
          "name": "Sign out",
          "description": "Ends the authenticated identity from the business, location, or register selection surface."
        },
        {
          "name": "Operating-context bar",
          "description": "Final confirmation of the active business, location, register, and register-session state."
        },
        {
          "name": "No substituted screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no exact safe business/location/register selector capture, so this guide intentionally publishes without a generic image."
        }
      ],
      "expectedResult": "The top bar shows the intended business, physical location, and register before any sale, inventory, payment, or reporting work begins.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "navigate-centripos",
      "url": "https://platform.getcentri.com/centripos/navigate-centripos",
      "title": "Navigate the CentriPOS workspace",
      "summary": "Use the exact desktop rail, section panels, operating-context bar, mobile tabs, More sheet, and personal tools without losing track of the business, location, or register you are working in.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Getting oriented",
      "introduction": "CentriPOS shows navigation that fits the signed-in role, tenant type, enabled products, permissions, screen width, and UI scale. If another user sees a different menu, first compare their business, role, location access, and permissions rather than assuming the screen was removed.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "On a desktop-sized window, start with the vertical rail on the left. Dashboard opens directly. Register, Sales, Inventory, Products, Contacts, Communications, and Reports open their first screen and expose their own screen list. CentriPay and Admin appear only when the current account has their required access.",
        "Hover over an area you are not currently using to open its temporary flyout, then choose the exact screen by its product icon and name. When an area is active, its screen list stays open as a second panel. Use the small panel control below the active rail icon to collapse or expand that list.",
        "If the rail or flyout says More above or More below, scroll inside that navigation area. Those cues mean additional destinations are outside the visible height; they do not mean the feature is unavailable. Increasing UI Scale can cause the rail to need more scrolling or move a tighter window into compact navigation.",
        "Read the operating-context bar before doing work. The business name opens Dashboard. The location and register name open Session Control, where the lock icon shows whether the selected register is open or closed. These links inspect the current context; they are not the store switcher.",
        "Use the other context-bar controls when present: Customer Display manages the selected register’s display and requires an open register session, the phone button opens or closes Dialpad CTI, and Ask Centri opens CentriAI with the current location and register context. A warning beneath the bar means the register has remained open for more than 24 hours and should be reviewed for closing and reconciliation.",
        "At the bottom of the desktop rail, open Tools when the actions are not already visible. Switch opens the supported location/register/sign-out switcher, Out signs out the displayed user, and Refresh performs a hard application refresh. Save an active cart or form and never refresh during an uncertain terminal payment.",
        "Choose the avatar at the bottom of the rail to open User Hub. This is the personal area for the signed-in Centri Account: identity, theme, UI scale, phone behavior, time clock, personal performance, Refresh data, Sign out / switch user, and Switch store when the account belongs to more than one business.",
        "On a phone or touch-mobile layout, use the fixed bottom tabs for Register, Sales, Products, and Inventory. The first tap opens that area’s first screen. While an area is active, tapping its tab again opens Choose a section so you can move among that area’s screens without returning to its first page.",
        "Tap More for Reports, CentriPay, Contacts, Communications, Network, and Admin when available. Tap the area name to open its first screen, or use the arrow button to open its full section menu. Network appears only for a network-enabled or child business; Admin and its individual screens remain permission-filtered.",
        "Use the bottom row of the More sheet for Profile, Refresh, Switch, and Comms. The Share button at the top can Copy Page Link, Open in Browser, or Email Link. Shared links use pos.getcentri.com and can preserve the current path, filters, or report view, but the recipient must still sign in and have permission to open that screen.",
        "After navigating, verify three things before acting: the intended area and screen are highlighted, the business/location/register context is correct, and the required control is available to your role. Use Switch for a different operating context; use User Hub → Switch store only when you intend to enter another business membership."
      ],
      "controls": [
        {
          "name": "Desktop rail",
          "description": "Permanent left-hand area icons on a desktop-sized window, beginning with Dashboard."
        },
        {
          "name": "Area icon",
          "description": "The same product icon used for that CentriPOS section; selecting it opens the section’s first screen."
        },
        {
          "name": "Flyout",
          "description": "Temporary screen list shown while hovering over an inactive desktop area."
        },
        {
          "name": "Active section panel",
          "description": "Persistent second navigation panel for the area currently open."
        },
        {
          "name": "Collapse / Expand panel",
          "description": "Small control below the active rail icon that hides or restores the persistent screen list."
        },
        {
          "name": "More above / More below",
          "description": "Scroll cues showing that the rail or flyout contains additional destinations outside the visible height."
        },
        {
          "name": "Operating-context bar",
          "description": "Row showing the active business, location, register, register-session state, and available operational tools."
        },
        {
          "name": "Business link",
          "description": "Opens Dashboard for the current business; it does not switch businesses."
        },
        {
          "name": "Location / register link",
          "description": "Opens Session Control for the currently selected operating context."
        },
        {
          "name": "Open / closed lock",
          "description": "Green open or destructive closed register-session indicator beside the register."
        },
        {
          "name": "Customer Display",
          "description": "Pairs or manages the customer-facing display for the selected register; live management requires an open session."
        },
        {
          "name": "Dialpad CTI",
          "description": "Phone control that opens or closes the configured calling experience."
        },
        {
          "name": "Ask Centri",
          "description": "Launches CentriAI with current page and operating context."
        },
        {
          "name": "Tools",
          "description": "Desktop action group containing Switch, Out, and Refresh; it collapses behind a Tools button on shorter layouts."
        },
        {
          "name": "Switch",
          "description": "Opens the location/register switch flow and supported sign-out choice."
        },
        {
          "name": "Out",
          "description": "Signs out the identity named in its tooltip."
        },
        {
          "name": "Refresh",
          "description": "Hard-refreshes the application and latest records; it is not a safe payment-retry control."
        },
        {
          "name": "User Hub",
          "description": "Personal Centri Account profile, appearance, clock, performance, phone, refresh, sign-out, and business-switching workspace."
        },
        {
          "name": "Mobile primary tabs",
          "description": "Register, Sales, Products, and Inventory fixed at the bottom of the mobile layout."
        },
        {
          "name": "Choose a section",
          "description": "Bottom sheet opened by tapping an already-active mobile primary tab."
        },
        {
          "name": "More sheet",
          "description": "Mobile access to Reports, CentriPay, Contacts, Communications, Network, Admin, Profile, Refresh, Switch, Comms, and page sharing as permissions allow."
        },
        {
          "name": "Share This Page",
          "description": "Creates a branded pos.getcentri.com link for the current path and supported view state; it does not grant access."
        },
        {
          "name": "Permission-filtered navigation",
          "description": "Screens can be hidden by role, explicit permission, tenant type, network state, or product availability."
        }
      ],
      "expectedResult": "The selected area opens, its current section is highlighted, and the top bar continues to show the correct working context.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "user-hub",
      "url": "https://platform.getcentri.com/centripos/user-hub",
      "title": "Use the User Hub",
      "summary": "Review the effective Centri Account identity and role, change personal appearance, manage company appearance defaults when authorized, refresh the app, and switch users or businesses.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Personal settings",
      "introduction": "User Hub currently includes several visible preview areas. Clock, sales performance, top products, target attainment, and Timesheet are not connected to live operational records, so never use their displayed values for payroll, commission, attendance, or sales reporting. The identity header does not print the current business name; verify the business separately in the operating-context bar.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Open User Hub from the avatar at the bottom of the desktop navigation rail, or choose Profile from the bottom row of the mobile More sheet.",
        "Confirm the displayed photo or initials, name, email address, and role label. In supported proxy-user mode, these fields follow the effective profile rather than necessarily the underlying authenticated owner. The role query uses the effective user inside the active tenant and prefers Account owner, then Super Admin, a custom-role name, Manager, Inventory Clerk, or Cashier.",
        "Verify the active business, location, and register in the operating-context bar because User Hub does not display the business name beside the identity. If either identity or operating context is wrong, do not continue into customer or financial work.",
        "Choose Dark, Light, or System under Appearance. The badge states Using company default with the inherited theme or Saved to your profile. When a personal override exists, Use company default clears that override and resumes the current business setting.",
        "On a supported desktop or fine-pointer layout, set UI Scale from 90% to 150% in 5% steps, or use 90%, 100%, 110%, 125%, or 140% presets. Around 125% and above, a tight window can change to compact navigation. UI Scale is hidden when the short viewport edge is below 1024 pixels and the device reports coarse pointer or no hover.",
        "Owners and Super Admins can see Company Defaults. Choosing a company theme saves immediately; moving or choosing a Default UI Scale saves the inherited scale. These defaults affect users who have no personal override, including users who later choose Use company default. Wait for Company defaults updated, and stop if Failed to update company defaults appears.",
        "Choose Shuffle under Category Colors only when you want a different sticky product-picker category-color mapping for the current user. The success message is Category colors shuffled. It changes visual mapping, not categories, products, or catalog assignments.",
        "Choose Refresh only after saving any active cart or form. Although the card says Reload the latest records without leaving this page, the implementation runs the application hard-refresh path and can rebuild app state. Never refresh during an active or uncertain terminal payment.",
        "Use Sign out / switch user to end the authenticated session. Switch store appears only when more than one business membership is available; it clears the active tenant selection and opens Choose your business without granting another membership or changing the signed-in identity.",
        "Treat Clock in / Clock out as a local on-screen preview. It only toggles component state, always reports 0hrs, 0min today, and does not persist a time entry. Leaving or refreshing the view loses that badge state. Use the approved timekeeping system instead.",
        "Treat Today, This Week, This Month, This Year, Avg Sale Value, Avg Discount Rate, Items Sold, Conversion Rate, Your Top Products, and target progress as placeholders. The implementation initializes sales, revenue, averages, items, and top products to zero/empty and does not query live sales. Profile target amounts may be real, but the actual attainment shown here is still the zero placeholder.",
        "Treat Timesheet as coming soon. Clock history, hours by day, and weekly summaries are not currently available. Use CentriPOS Reports for operational sales totals and the business’s approved system for time records."
      ],
      "controls": [
        {
          "name": "Identity header",
          "description": "Shows the effective profile photo or initials, display name, email, role label, and local clock badge; it does not show the current business name."
        },
        {
          "name": "Effective profile",
          "description": "Proxy-user profile when proxy mode is active; otherwise the signed-in account profile."
        },
        {
          "name": "Primary role label",
          "description": "Priority display of Account owner, Super Admin, custom-role name, Manager, Inventory Clerk, or Cashier from roles in the active tenant."
        },
        {
          "name": "Operating-context bar",
          "description": "Authoritative visible confirmation of the current business, location, register, and session state outside User Hub."
        },
        {
          "name": "Sign out / switch user",
          "description": "Ends the authenticated session; it is different from changing only the business, location, or register."
        },
        {
          "name": "Switch store",
          "description": "Appears only with multiple business memberships, clears the selected tenant context, and opens Choose your business."
        },
        {
          "name": "Refresh data",
          "description": "Runs the hard application refresh path. Save work first and never use it as a payment retry."
        },
        {
          "name": "Appearance",
          "description": "Personal Dark, Light, or System theme selection."
        },
        {
          "name": "Using company default",
          "description": "No personal override is active for that setting."
        },
        {
          "name": "Saved to your profile",
          "description": "A personal theme or UI-scale preference overrides the inherited business default."
        },
        {
          "name": "Use company default",
          "description": "Clears the personal override and resumes inheriting the active business default."
        },
        {
          "name": "UI Scale",
          "description": "Fine-pointer readability/density setting from 90% through 150%; hidden on qualifying smaller touch layouts."
        },
        {
          "name": "Company Defaults",
          "description": "Owner/Super Admin controls for the theme and scale inherited by users without personal overrides."
        },
        {
          "name": "Company defaults updated",
          "description": "The tenant appearance save succeeded."
        },
        {
          "name": "Failed to update company defaults",
          "description": "The tenant update failed and the scale control returns to the prior displayed value."
        },
        {
          "name": "Category Colors / Shuffle",
          "description": "Selects another stable product-picker color mapping for the current user; it does not edit catalog data."
        },
        {
          "name": "Clock in / Clock out",
          "description": "Non-persistent component preview only; it does not create a timekeeping record."
        },
        {
          "name": "Your Sales Performance",
          "description": "Placeholder cards initialized to zero rather than live reporting queries."
        },
        {
          "name": "Targets",
          "description": "Profile target amounts compared with placeholder zero actuals; not current attainment reporting."
        },
        {
          "name": "Your Top Products",
          "description": "Empty placeholder panel showing No sales data yet."
        },
        {
          "name": "Timesheet",
          "description": "Coming-soon panel with no clock history, daily hours, or weekly summaries."
        },
        {
          "name": "No substituted screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth capture manifest contains no exact safe User Hub image, so this guide intentionally publishes without an unrelated screenshot."
        }
      ],
      "expectedResult": "The intended Centri Account and role remain visible, saved personal appearance choices report Saved to your profile (or correctly inherit company defaults), and any user or business switch reaches the expected selection flow. Clock, performance, products, targets, and timesheet values remain explicitly treated as previews until they are connected to live records.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "install-app",
      "url": "https://platform.getcentri.com/centripos/install-app",
      "title": "Install CentriPOS on desktop, iPhone, or iPad",
      "summary": "Install the branded CentriPOS web app from pos.getcentri.com, understand the company-provided native shell, and verify the correct business and register before using the device operationally.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Devices",
      "introduction": "CentriPOS publishes an installable standalone web-app manifest and service worker. Installation makes the app easier to launch; it does not grant a Centri Account, choose a business, pair hardware, or guarantee offline selling and payments. There is no public App Store/TestFlight download linked from the current product code, so use a native build only when your company provides and manages it.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Before installation, open https://pos.getcentri.com directly and confirm the address bar shows the branded host. Do not install from a Supabase, preview, or unfamiliar domain. Sign in only with the Centri Account established from your invitation.",
        "On desktop Chrome, use the Install icon in the address bar when shown, or More → Cast, save, and share → Install page as app. On Microsoft Edge, use the App available icon or Settings and more → Apps → Install this site as an app. Browser wording can change; the destination must still be pos.getcentri.com and the installed name should be CentriPOS.",
        "On iPhone or iPad, open pos.getcentri.com in Safari, choose Share, then Add to Home Screen. Enable Open as Web App when Safari offers it, confirm the CentriPOS name and icon, and choose Add. The icon is installed only on that device.",
        "Launch CentriPOS from the new desktop, dock, Start, or Home Screen icon. The web manifest requests standalone display, so the installed web app should open in a focused window without the normal browser chrome. If it opens as a regular tab, remove the shortcut and repeat the browser’s web-app installation flow rather than creating a plain bookmark.",
        "If your company distributes a native iPhone/iPad CentriPOS build, install it only through that approved company channel. The current Capacitor shell uses app ID com.getcentri.pos, app name CentriPOS, and loads https://pos.getcentri.com. A native shell is a container around the same hosted product, so most screen updates still arrive from the web deployment.",
        "Sign in and choose the authorized business, location, and register. Confirm those three values and the register-session state in the operating-context bar before scanning, selling, receiving inventory, opening a customer display, or taking payment. Installation does not retain authority to the last context when the account or device state requires a new selection.",
        "Allow a device permission only when the exact workflow needs it—for example, camera access while opening the barcode scanner. Denying an optional permission should not be treated as a reason to share credentials or weaken device security. A managed register device should use the company’s approved browser, lock-screen, update, printer, and network policies.",
        "Test the installed surface with a safe, non-financial workflow: open Dashboard, navigate to a permitted screen, close the app, and reopen it from its icon. Then separately test the required hardware workflows under company supervision. Never use a live card payment as the first installation test.",
        "Treat service-worker caching as recovery assistance, not an offline POS guarantee. CentriPOS can cache its shell, static assets, and previously visited navigation responses, but current customer, inventory, register, processor, and reporting data still depend on network services. If the device is offline, stop financial work until connectivity and transaction state are known.",
        "When an installed app appears stale, save work and use the in-app Refresh control once while online. If the version still does not update, close and reopen the installed surface and follow company support guidance before clearing app data or reinstalling; clearing stored site data can remove remembered device context."
      ],
      "controls": [
        {
          "name": "Branded web address",
          "description": "https://pos.getcentri.com is the only public CentriPOS application host customers should install."
        },
        {
          "name": "Web app manifest",
          "description": "Declares CentriPOS™, its branded icons, start URL /, standalone display, colors, and supported orientation for PWA installation."
        },
        {
          "name": "Install page as app",
          "description": "Chrome desktop command that creates the standalone CentriPOS web app when the site is installable."
        },
        {
          "name": "Install this site as an app",
          "description": "Microsoft Edge command for the installed web-app surface."
        },
        {
          "name": "Add to Home Screen",
          "description": "Safari action that places the CentriPOS web app icon on one iPhone or iPad."
        },
        {
          "name": "Open as Web App",
          "description": "Safari option that launches the saved site as an app-like standalone surface."
        },
        {
          "name": "Standalone display",
          "description": "Focused app window requested by the CentriPOS manifest; it does not change permissions or account membership."
        },
        {
          "name": "Native shell",
          "description": "Company-provided Capacitor container with app ID com.getcentri.pos that loads the branded production host."
        },
        {
          "name": "No public native download",
          "description": "The current product source does not publish an App Store or TestFlight destination for customers; obtain native builds only through the approved company channel."
        },
        {
          "name": "Service worker",
          "description": "CentriPOS background web component that caches the app shell/static assets and uses network-first navigation with a cached fallback."
        },
        {
          "name": "Cached fallback",
          "description": "Previously stored page response used when a network navigation fails; it can be stale and is not proof that live operational services are available."
        },
        {
          "name": "Device permission",
          "description": "Browser or OS access such as camera use, requested only when a feature requires it."
        },
        {
          "name": "Operating context",
          "description": "Selected business, location, register, and register-session state; verify it after every new installation or account switch."
        },
        {
          "name": "Refresh",
          "description": "Hard application refresh used after work is saved and no payment is processing."
        },
        {
          "name": "Reinstall / clear app data",
          "description": "Recovery actions that can remove remembered device and context state; use them only under approved support guidance."
        }
      ],
      "expectedResult": "The installed CentriPOS icon opens a focused surface backed by https://pos.getcentri.com, reaches the normal Centri Account and business-selection flow, and shows the intended business, location, register, and session state before operational use. No offline or native-only capability is assumed merely because installation succeeded.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "accept-invitation",
      "url": "https://platform.getcentri.com/centripos/accept-invitation",
      "title": "Accept a Centri Account invitation",
      "summary": "Open the personal welcome link, let CentriPOS verify its secure invitation token, and create the password credential required to finish the invited account setup.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Signing in",
      "introduction": "The invitation-acceptance route itself does not offer Continue with Google: it verifies the personal invite token and opens the CentriPOS password-creation screen. The separate current login page does offer Google for a matching invited identity, but that option does not accept, repair, or replace an unused membership invitation. Never forward the invitation or paste its token into a ticket, screenshot, or chat.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Open the newest CentriPOS welcome invitation in the same browser where you will finish setup. The link contains a personal token_hash and opens the branded Accept invitation page.",
        "Wait while Opening invitation is displayed. CentriPOS verifies the token as an invite, establishes a temporary secure session, and redirects automatically to Set password. There is no email, organization, or Google-sign-in choice on this invitation-loading screen.",
        "On Welcome to CentriPOS, verify the displayed first name or account identity and the business name when those details are available. A business logo may replace the CentriPOS mark, and the page can note access to additional stores. Stop and contact the administrator if the invitation belongs to the wrong person or business.",
        "Enter New password and Confirm password. Each field has its own show/hide control. The two values must match and the current minimum is six characters. Use a unique business password that meets any stronger company policy.",
        "Choose Update password once. A successful update saves the password, keeps the invited session authenticated, and routes into the normal app entry flow. Then choose only the business, location, and register granted to the new membership.",
        "If Invitation could not be opened reports a missing token, invalid/expired token, or failure to open the secure password session, choose Back to login and ask an administrator to send a fresh welcome invitation. The login page’s Google or email/password controls cannot repair a missing membership acceptance. Open the new invite link in one browser and do not reuse the older message.",
        "If the next page says Invitation link expired, the temporary invitation session is absent, expired, or already used. Return to login and request a resent welcome invitation; a normal password-reset email or Google login is not a substitute for accepting the membership invitation."
      ],
      "controls": [
        {
          "name": "Invitation link",
          "description": "Personal email link to /auth/accept-invite containing the secure token_hash used for invite verification."
        },
        {
          "name": "Opening invitation",
          "description": "Automatic loading state while CentriPOS verifies the invite token and establishes the temporary authenticated session."
        },
        {
          "name": "Invitation could not be opened",
          "description": "The token is missing, invalid, expired, or verified without a usable secure session."
        },
        {
          "name": "Back to login",
          "description": "Returns to the normal CentriPOS sign-in screen, which currently offers Google and email/password; neither option repairs or resends the invitation."
        },
        {
          "name": "Set password",
          "description": "Secure /reset-password?from=invite step reached automatically after successful token verification."
        },
        {
          "name": "Welcome to CentriPOS",
          "description": "Password-creation screen that can display the invited identity, store branding, tenant name, and count of other available stores."
        },
        {
          "name": "New password",
          "description": "Credential created for the invited Centri Account."
        },
        {
          "name": "Confirm password",
          "description": "Second entry that must exactly match New password."
        },
        {
          "name": "Show / Hide password",
          "description": "Per-field visibility controls; use them only on a private screen."
        },
        {
          "name": "Minimum length",
          "description": "Current application validation requires at least six characters; follow any stronger business password policy."
        },
        {
          "name": "Update password",
          "description": "Saves the credential for the invitation session and enters the normal authenticated app flow."
        },
        {
          "name": "Invitation link expired",
          "description": "The invite password session is unavailable or already used; an administrator must resend the welcome invitation."
        },
        {
          "name": "No Google option on invitation",
          "description": "The accept-invitation and invite-password screens contain no Google control. The separate login screen does; it authenticates a matching invited identity but does not accept a pending invitation."
        }
      ],
      "expectedResult": "The invitation is marked complete, the Centri Account can sign in, and only the businesses and locations granted by the administrator are available.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "reset-password",
      "url": "https://platform.getcentri.com/centripos/reset-password",
      "title": "Reset your Centri Account password",
      "summary": "Request the branded recovery email, establish its temporary secure session, and replace the password used by the current CentriPOS email-and-password sign-in.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Signing in",
      "introduction": "The current CentriPOS login screen does not offer Google sign-in. A password reset changes the credential for an existing Centri Account; it does not create a missing invitation, business membership, role, location, or register permission. Reset links are personal and should never appear in screenshots or support messages.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Open https://pos.getcentri.com/login and choose Forgot password?. The sign-in form changes to Reset your password.",
        "Enter the exact email address already connected to the Centri Account and choose Send reset link once. CentriPOS sends the request through its branded password-reset service and shows Check your email when the request succeeds.",
        "Open the newest CentriPOS reset email in the same browser where you will complete the reset. Older recovery messages can be invalid after a newer request. The link must return to the branded pos.getcentri.com reset page; do not enter a password on an unfamiliar host.",
        "Wait while Checking secure link is displayed. The recovery link establishes a temporary authenticated session. If CentriPOS cannot find that session, it shows Reset link expired and directs you to request another reset from the login screen.",
        "On Secure your account, review the displayed account name or email and business branding when available. The page may show the selected tenant name and note access to other stores; it does not let you add or change memberships. Stop if the identity is not yours.",
        "Enter New password and Confirm password. The fields must match and the current application minimum is six characters. Each field has a separate Show/Hide control; reveal it only on a private screen and follow any stronger company policy.",
        "Choose Update password once and wait for Password updated. CentriPOS returns to the application entry flow using the temporary recovery session. If the app asks you to sign in again, use the exact account email and the new password.",
        "After access succeeds, choose the intended business, location, and register. A successful reset does not prove that the account has the required membership or permission; an administrator must repair missing access separately.",
        "If no email arrives, check the exact address and spam/quarantine without repeatedly submitting. Then request one new reset and use only that newest message. Contact support with the email domain and request time—not the reset URL, password, or token—when delivery remains unavailable."
      ],
      "controls": [
        {
          "name": "Forgot password?",
          "description": "Switches the current login card from Sign in to Reset your password."
        },
        {
          "name": "Reset your password",
          "description": "Form that accepts the existing Centri Account email and requests the branded recovery message."
        },
        {
          "name": "Send reset link",
          "description": "Invokes the CentriPOS password-reset service with a return path to pos.getcentri.com/reset-password."
        },
        {
          "name": "Check your email",
          "description": "Success message confirming the request was accepted; it does not prove delivery or change the password by itself."
        },
        {
          "name": "Recovery link",
          "description": "Personal, time-limited link that establishes the temporary password-reset session."
        },
        {
          "name": "Checking secure link",
          "description": "Loading state while CentriPOS checks the recovery session and loads account context."
        },
        {
          "name": "Secure your account",
          "description": "Valid recovery screen that can display account/store branding before password entry."
        },
        {
          "name": "New password",
          "description": "Replacement credential for current CentriPOS email-and-password access."
        },
        {
          "name": "Confirm password",
          "description": "Second entry that must exactly match New password."
        },
        {
          "name": "Show / Hide password",
          "description": "Per-field visibility control; use only when the screen is private."
        },
        {
          "name": "Minimum length",
          "description": "Current application validation requires at least six characters; stronger company rules still apply."
        },
        {
          "name": "Update password",
          "description": "Saves the new credential for the current recovery session."
        },
        {
          "name": "Password updated",
          "description": "Success state before CentriPOS returns to its normal authenticated entry flow."
        },
        {
          "name": "Reset link expired",
          "description": "No usable recovery session exists because the link is invalid, expired, already used, or otherwise unavailable."
        },
        {
          "name": "Membership unchanged",
          "description": "Password recovery does not add a business, location, register, role, or permission."
        },
        {
          "name": "No Google option",
          "description": "The current login and reset surfaces use the invited Centri Account email and password; this guide does not manage a Google credential."
        }
      ],
      "expectedResult": "The newest branded recovery link accepts matching valid passwords, CentriPOS confirms Password updated, and the same account email can enter the normal Centri Account flow with the new credential. Existing business memberships and permissions remain unchanged.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "open-register-session",
      "url": "https://platform.getcentri.com/centripos/open-register-session",
      "title": "Open, Reconcile, and Close a Register Session",
      "summary": "Operate the selected register’s financial session from opening float through receipt activity, manual drawer movements, tender verification, notes, discrepancies, closure, and the last report.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Session control",
      "introduction": "Register → Session control uses the Banknote icon. A session belongs to the currently selected business, location, and register and groups receipts, tenders, manual drawer movements, users, timestamps, and closure evidence. Opening and closing require pos.register_open; Add/Remove cash requires cash.manage. Never use a manual cash movement to represent a sale tender or change, and never close a mismatch without recounting and documenting the approved reason.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Before opening, confirm the selected business, location, and register in the CentriPOS context bar. Go to Register → Session control, identified by the Banknote icon, and wait for the loaded Register closed or OPEN state.",
        "When closed, review Last Report first when present: closed time/user, expected cash, and Difference. Choose View in Reports for the closure record or Report Details for the printable summary. Resolve unexplained prior differences before opening another session.",
        "Count the physical drawer and enter Opening float as a nonnegative amount. Blank, invalid text, or 0 becomes a zero float. Enter an optional opening note for verified context such as a safe transfer or approved drawer variance.",
        "Choose Open Register once. The operation records tenant, selected register, opening user, amount, and note through the register-session operation. Wait for Register opened; CentriPOS then routes to Sell. If it fails, read the error and confirm access/context instead of clicking repeatedly.",
        "The Sell screen can be used to browse products and build estimates while the register is closed, but a normal register sale cannot be completed until an authorized user opens the session.",
        "Return to Session control and confirm the OPEN badge, exact location/register, opening-to-current time range, and Drawer cash. The displayed drawer base is opening float plus manual Add cash minus Remove cash; it intentionally excludes cash received through sales.",
        "Review Receipt Activity. It groups session-attached receipts into operational buckets such as Completed, Saved, Incomplete, Layaways, Layaway Payments, Account Balance Open, Account Paid, Layaway Completed, Returns, and Exchanges. Open a bucket/receipt to inspect the source record before reconciling.",
        "Use Cash drawer movements only for physical cash entering or leaving outside a sale, such as an approved pay-in, safe drop, or payout. It lists opening float and manual pay_in/pay_out with date, type, reason, and amount—not every cash sale.",
        "To Add cash or Remove cash, enter an amount greater than zero and an explanatory note, then choose the action once. The record stores the session, user, amount, pay_in/pay_out type, and reason. The current handler does not verify that a removal is less than the expected drawer; follow physical-control policy and recount afterward.",
        "Do not record sale cash or customer change through Add/Remove cash. Cash tenders and change are reflected in sale payment lines and summarized under Payments Collected/Payment Types. Duplicating them as a drawer movement will distort expected cash.",
        "Use Session Notes as working draft lines during the day. Add, edit, or remove lines as needed. They are local UI state and are copied into Closing Note when the Close Register dialog opens; they are not independently persisted as journal entries before closure.",
        "Review Internal Receipt Notes separately. These are sale-level internal notes attached to receipts in the session with author/time context. They do not automatically become the register closing note. Open the receipt for the complete transaction context.",
        "Review Payments Collected. It totals tender in this session and includes payments collected on existing layaways; expand a payment type to inspect contributing receipts. Do not compare this table directly to drawer base without adding the Cash tender total.",
        "Review A/R payments separately. Customer Account payments collected during the session remain outside register tender balancing by design. Confirm account receipts and Customer Account balances independently instead of forcing them into a payment-type count.",
        "Before closing, resolve open or unusual receipt buckets, returns/exchanges, layaways, account activity, internal notes, manual cash movements, payment-type totals, and uncertain processor transactions. For an uncertain card result, inspect CentriPay Transactions and settlement evidence before retrying or closing.",
        "Choose Close Register. The dialog resets its count fields each time it opens and requires review of every payment type. Use the check box only when the verified counted value equals Expected; it fills the expected amount. Otherwise enter the actual independently counted/verified amount.",
        "Cash must be entered manually even when expected is zero. Non-cash payment types with an expected zero initialize as verified 0.00. Counted fields allow signed currency formatting, but enter only valid verified values consistent with the tender’s reconciliation evidence.",
        "Read Totals Expected, Counted, and Difference. Payment-type mismatch uses a half-cent tolerance. A green Balanced result means the entered counts match system expected totals; it does not prove processor settlement, bank deposit, inventory, or accounting reconciliation.",
        "Review the Cash summary separately: Drawer base equals opening float plus pay-ins minus pay-outs; Cash tenders collected comes from session sale payments; Expected drawer cash is their sum; Cash difference is counted Cash minus expected drawer cash.",
        "Enter a Closing Note. Session Notes populate it when the dialog opens, but you can revise the final note. Explain every approved over/short, missing tender, processor issue, safe drop, exception, or follow-up in durable, professional language.",
        "Choose Close Register. If any payment type differs, Count Mismatch Detected names the mismatches and says management will be notified. Choose Go Back to recount/correct. Use Close Anyway only under approved authority with a complete closing-note justification.",
        "A successful close records closing user/time, counted tender values, closing cash, expected drawer cash, difference, and closing note; it clears the active-session cache and refreshes closure/report data. A background processor-reconciliation refresh is attempted afterward, but its failure does not roll back the already closed session.",
        "After Register closed appears, review the Last Report and full Register Report Summary: location/register/report number, open/close times, users, expected/count payment types, cash movements, expected cash, difference, and notes. Choose Print only after confirming the report and recipient.",
        "Use View in Reports to inspect the durable Register Report record and continue the full path for discrepancies: sale/payment row → register session → closure payment totals → processor transaction/deposit → QuickBooks sync row where applicable. Never repair production financial data from this screen alone.",
        "Open the next session only after the previous closure is visible and reconciled enough for business policy. Confirm the new opening float comes from actual physical cash and is not simply copied from the previous expected amount.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully loaded closed Session Control screen at 1440×900 with the actual Banknote navigation, opening-float form, optional note, and Open Register control. No float/note was entered, no session was opened, and no receipt, tender, customer, closure, or cash data is exposed."
      ],
      "controls": [
        {
          "name": "Banknote icon",
          "description": "Exact Register navigation icon for Session control."
        },
        {
          "name": "Register closed",
          "description": "No active session for the selected register."
        },
        {
          "name": "Last Report",
          "description": "Most recent closure’s time/user, expected cash, and difference."
        },
        {
          "name": "View in Reports",
          "description": "Opens the durable Register Reports record for the prior session."
        },
        {
          "name": "Opening float",
          "description": "Actual physical cash present before transaction activity; blank/invalid becomes 0."
        },
        {
          "name": "Opening note",
          "description": "Optional persisted context stored with the opening operation."
        },
        {
          "name": "Open Register",
          "description": "Creates the selected register session when the user has pos.register_open."
        },
        {
          "name": "OPEN badge",
          "description": "Confirms an active session for the displayed location/register."
        },
        {
          "name": "Drawer cash / drawer base",
          "description": "Opening float plus manual pay-ins minus pay-outs; excludes sale tenders."
        },
        {
          "name": "Receipt Activity",
          "description": "Session receipts grouped by operational/register status."
        },
        {
          "name": "Cash drawer movements",
          "description": "Opening float and manual Add/Remove cash only."
        },
        {
          "name": "Add cash",
          "description": "Immediate pay_in drawer movement requiring a positive amount."
        },
        {
          "name": "Remove cash",
          "description": "Immediate pay_out; current UI does not cap it at expected drawer cash."
        },
        {
          "name": "Session Notes",
          "description": "Local working lines copied into Closing Note when the close dialog opens."
        },
        {
          "name": "Internal Receipt Notes",
          "description": "Persisted sale-level notes displayed separately from closing notes."
        },
        {
          "name": "Payments Collected",
          "description": "Session tender totals including existing-layaway payments; expandable to receipts."
        },
        {
          "name": "A/R payments",
          "description": "Customer Account collections kept separate from register tender balancing."
        },
        {
          "name": "Close Register",
          "description": "Opens tender-count and cash-summary reconciliation."
        },
        {
          "name": "Expected",
          "description": "System-calculated tender amount."
        },
        {
          "name": "Counted",
          "description": "User-entered independently verified amount."
        },
        {
          "name": "Verification checkbox",
          "description": "Fills Counted with Expected; use only after verification."
        },
        {
          "name": "Expected drawer cash",
          "description": "Opening float + pay-ins − pay-outs + Cash sale tenders."
        },
        {
          "name": "Count mismatch warning",
          "description": "Explicit confirmation before closing with any mismatched tender."
        },
        {
          "name": "Close Anyway",
          "description": "Finalizes an approved mismatch; requires documentation and follow-up."
        },
        {
          "name": "Closing Note",
          "description": "Persisted closeout explanation; initially populated from Session Notes."
        },
        {
          "name": "Background processor refresh",
          "description": "Attempted after successful close and does not roll back the closed session if it fails."
        },
        {
          "name": "Register Report Summary",
          "description": "Printable last-closure evidence with tender, movement, difference, and note details."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant /register/session-control capture of the closed opening screen; no financial/customer data or state change."
        }
      ],
      "expectedResult": "The selected register shows an open session with the opening float and opening time recorded. Sell becomes available for that register, and new activity belongs to this session.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/register-session-control.png",
        "alt": "Harbor & Hearth Register Session Control showing the selected location, register, session status, and session actions in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sell-screen",
      "url": "https://platform.getcentri.com/centripos/sell-screen",
      "title": "Understand the Sell screen",
      "summary": "Orient yourself to operating context, product search and filters, Lightning layouts, responsive cart, customer and attribution, line/sale controls, saved-sale continuation, customer display, and the handoff to payment.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Register → Sell is live operational workspace state, not a disposable product browser. You need pos.sell permission plus a selected location/register; normal selling also depends on the correct open register session. Cart/customer/fulfillment/payment draft state can synchronize locally and to an active draft/customer display. Do not refresh, clear, switch context, or open another sale casually. The approved Harbor & Hearth Sell screenshot was rejected because the route retained a loading indicator, so this guide uses no invented image.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Confirm the signed-in user, business, location, register, and register-session state in the operating-context bar before touching the cart. If no location/register is selected, Sell shows Choose Location & Register. If Access restricted appears, an administrator must grant pos.sell; do not share another user’s account.",
        "Read the screen as two work areas. The product workspace contains search, filters, Product list/Lightning layout controls, and sellable products. The cart is docked on roomy desktop; condensed/tablet layouts use a right-side cart sheet; phone layouts use a bottom drawer. The floating cart button shows line count and total.",
        "Use product search for name, product/variant SKU, barcode, UPC, and configured product codes. An exact valid barcode can add the matching product/variant directly; ambiguous products can open variant/serial/lot or other required selection. Confirm the item that entered the cart—never rely only on the scanned digits.",
        "In Products view, filter by Brand, Category, Supplier, Tag, Variant value, or Target price ± range. Multiple filters narrow the sellable catalog. Clear/Clear all removes filters and search. Search/filter state is reflected in the route, but availability rules still exclude products not allowed at the active location/register.",
        "If your role can manage dynamic folders and filters are active, Save view can create a reusable Lightning/dynamic layout from those filters. It does not save the current cart or sale. Product-list and Lightning-layout icons are view switches, not navigation to the Admin layout editor.",
        "In Lightning layouts, choose the layout when more than one applies and navigate its folders/tiles. Dynamic folders resolve against current product data and active location/register availability. A tile can add an exact product, open variant choice, or navigate into another folder depending on its setup.",
        "Select a product tile/search result to add it. For variants, choose the exact enabled combination. Serialized merchandise prompts for enough unsold serials before completion; a sold-serial conflict offers the original receipt. Lot-controlled merchandise requires the intended available lot. A duplicate selection can increment or prompt according to product/cart rules.",
        "Open the cart and attach the customer early when customer pricing, tax exemption, account charge, delivery/shipping, history, source attribution, or financing depends on identity. Walk-in deliberately leaves the sale unattached. Detaching a customer also clears customer attribution fields; verify before doing it.",
        "Complete visible customer/source fields that the business requires: customer source and detail, buying reason, quote/card-given state, and sale note. These are operational/interaction evidence—not a substitute for item notes, fulfillment instructions, warranty details, or private payment information.",
        "Review every cart line: product/variant identity, quantity, unit price or authorized override, line discount, tax treatment, fulfillment, schedule/address/phone, serial/lot, notes, and extended total. Use the line editor rather than deleting/re-adding when preserving connected metadata matters.",
        "Review sale-level controls: percent/dollar discount, tax assignment/customer exemption, matched/applied promotions, and overall fulfillment. Sale fulfillment can include carry out, delivery, shipping, pickup, or supported alternatives; changing type clears incompatible shipping/address/pickup state. Add the configured fulfillment charge and schedule/method once, then reconcile it with line-level choices.",
        "For delivery/shipping, verify customer or custom address and phone, method, scheduled date/time intent, and any shipping configuration. For pickup, verify pickup location and method. An attached customer address can be updated through the supported flow, which changes the customer contact used by the cart; confirm authorization.",
        "Watch subtotal, discounts, tax, fulfillment charge, prior payment, total, payments, and balance due. A continued saved, layaway, or on-account sale can include prior-payment state; do not treat the full current total as newly due without reading the balance.",
        "Use Save Sale to preserve an unfinished opportunity. The Saved Sales control/count opens resumable saved sales excluding the currently open draft. When retrieving, CentriPOS checks editing ownership and current-cart conflicts; choose Cancel, Clear & Continue, or Save & Continue deliberately. Opening marks/claims the supported saved state and rebuilds customer, items, attribution, fulfillment, and prior payment context.",
        "If Sale Taken Over appears, this local cart is locked because the sale is live elsewhere. Use Receipts to investigate or Clear Local Cart only when the remote sale is authoritative. Do not attempt to defeat the lock with refresh or duplicate entry.",
        "Use Post cart/customer display/review-sign controls only for the intended customer session. The active register session can live-sync cart/contact state and receive customer signature or remote scan events. Verify the correct display/session before showing customer data; customer display is optional and failures should not be mistaken for sale completion.",
        "Before Pay, reconcile customer, items, quantities, identifiers, discounts, promotions, tax, fulfillment, prior payments, total, and balance. Pay opens the payment workflow; it does not itself guarantee a processor approval or completed receipt. Follow the Take payment guide and wait for the final receipt result.",
        "Other completion paths—Save Sale, layaway, Customer Accounts/on-account, posted customer cart, return review, or return/exchange—have different status, payment, signature, and follow-up behavior. Use their dedicated guides rather than treating them as Pay variants.",
        "After a successful completion, verify the receipt/status and expected cart reset. If an action overlay says it is saving/processing/completing, wait. Never refresh or resubmit while outcome is uncertain; reconcile the sale and external processor first."
      ],
      "controls": [
        {
          "name": "Choose Location & Register",
          "description": "Shown when Sell lacks required operating context."
        },
        {
          "name": "Access restricted",
          "description": "Current role lacks pos.sell and cannot create or continue sales."
        },
        {
          "name": "Search",
          "description": "Finds allowed products/variants by text and supported identifiers; an exact code may add directly."
        },
        {
          "name": "Product list icon",
          "description": "Shows searchable/filterable product grid."
        },
        {
          "name": "Lightning layouts icon",
          "description": "Shows assigned quick-pick layout; not the layout editor."
        },
        {
          "name": "Layout switcher",
          "description": "Chooses among multiple applicable Lightning layouts."
        },
        {
          "name": "Brand / Category / Supplier / Tag / Variant",
          "description": "Multi-value catalog filters."
        },
        {
          "name": "Target $",
          "description": "Filters products around a target price using the configured ± range."
        },
        {
          "name": "Save view",
          "description": "Authorized dynamic-layout action from active product filters; unrelated to Save Sale."
        },
        {
          "name": "Product tile/result",
          "description": "Adds the product or opens required variant/serial/lot choice."
        },
        {
          "name": "Availability scope",
          "description": "Only products allowed at the active tenant/location/register are sellable."
        },
        {
          "name": "Docked cart / cart sheet / bottom drawer",
          "description": "Same cart controls presented responsively by available space/device shell."
        },
        {
          "name": "Customer / Walk-in",
          "description": "Attaches an identified customer or deliberately keeps the sale unattached."
        },
        {
          "name": "Customer source / Buying reason / Quote or card given",
          "description": "Sale attribution and follow-up context."
        },
        {
          "name": "Cart line editor",
          "description": "Quantity, price, discounts, tax, fulfillment, schedule/address, serial/lot, notes, and connected line metadata."
        },
        {
          "name": "Sale discount / promotions",
          "description": "Sale-level adjustments; verify permissions and totals before checkout."
        },
        {
          "name": "Tax assignment / customer exemption",
          "description": "Effective sale tax treatment; product taxability and location tax still matter."
        },
        {
          "name": "Fulfillment",
          "description": "Sale/line carry-out, delivery, shipping, pickup and connected method/schedule/address/charge controls."
        },
        {
          "name": "Save Sale",
          "description": "Persists unfinished sale state; it is not the dynamic filter Save view."
        },
        {
          "name": "Saved Sales count/control",
          "description": "Opens resumable saved sales, excluding the active draft."
        },
        {
          "name": "Cart conflict dialog",
          "description": "Cancel, Clear & Continue, or Save & Continue before another sale is loaded."
        },
        {
          "name": "Sale Taken Over",
          "description": "Local lockout because another register/user owns the live sale."
        },
        {
          "name": "Customer display / Post cart / review-sign",
          "description": "Optional synchronized customer-facing cart/contact/signature workflow tied to active session."
        },
        {
          "name": "Pay",
          "description": "Opens payment allocation/processor workflow for the current balance; completion still requires successful finalization."
        },
        {
          "name": "Processing overlay",
          "description": "Blocks interaction while a named sale action is running; wait and reconcile before retry."
        },
        {
          "name": "No exact screenshot",
          "description": "The real Amelia Grant Harbor & Hearth /register/sell capture remained visibly loading and was rejected. No fabricated or wrong-account Sell image is published."
        }
      ],
      "expectedResult": "The cart contains the intended products, quantities, customer, discounts, taxes, and fulfillment choices, and Pay opens with the correct balance due.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "scan-products",
      "url": "https://platform.getcentri.com/centripos/scan-products",
      "title": "Scan barcodes and product labels",
      "summary": "Use the Sell search, camera capture, keyboard-style scanner, or connected display scanner to resolve the exact available product or variant before it enters the cart.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Scanning is part of Register → Sell, not a separate navigation screen. The Barcode icon marks the search/scanner affordance. A local camera or keyboard scan fills product search and still requires selection or Enter on the highlighted result; only a connected-display remote scan with one exact match adds directly. Never assume a beep means the intended item reached the cart.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Open Register → Sell and confirm the correct business, location, register, and open session. Clear unrelated product filters when the intended item is not available in the current search scope.",
        "For a USB or Bluetooth scanner configured as a keyboard, place focus in Search products or scan barcode… when necessary and scan once. The scanner types the printed value; CentriPOS ranks matching products and enabled variants in the result menu.",
        "Read the highlighted result before pressing Enter. An exact variant code should highlight that variant; selecting a master product with enabled variants opens the variant picker rather than guessing a variant. Click the intended product/variant or use Arrow Up, Arrow Down, and Enter.",
        "For the device camera, choose the Barcode icon beside product search when that interactive button is present. Allow camera access only on the trusted pos.getcentri.com app and point the rear camera at one code inside the scan box.",
        "If the camera cannot read the code, type the complete printed MFC, UPC, or barcode in the manual field and choose Capture code, or press Enter there. Camera recognition and Capture code close the scanner and place the decoded value into Sell search; they do not silently choose among ambiguous results.",
        "CentriPOS search can match product name, SKU, base barcode, active configured product codes, brand, category, tag, supplier, variant name, variant SKU, and variant attributes. Treat a broad text match as a search suggestion, not proof that the printed barcode belongs to that row.",
        "Barcode identity is exact and case-insensitive after surrounding spaces are trimmed. A product-level match can use the product barcode or an active product code without a variant assignment. A variant-level match can use the variant barcode or an active product code assigned to that exact variant.",
        "When a printed CentriPOS override label begins with LBL- and has the complete supported token, Sell checks the active label override for the current tenant. A valid unexpired label can add its product/variant with the printed price override or callout note.",
        "Read override feedback. Label added to register confirms the mapped item was added. Label override is unavailable means the code is missing, inactive, or expired. Label product is unavailable at this register means its mapped product or variant is not currently sellable in this operating context. Label scan failed reports a lookup error.",
        "For a connected customer display or supported remote scanner, the scan must belong to the same active register session. Checkout activity or another user’s live-sale lock pauses the scan. A remote scan adds directly only when one exact available product or variant is resolved; otherwise it reports No single matching product was found and tells the cashier to resolve it in register search.",
        "Availability still controls scanning. Product/category location or register restrictions and active Availability Rules can remove a catalog record from Sell even when its barcode is correct. Scanning does not bypass inactive products, disabled variants, operating-context restrictions, or a live-sale lock.",
        "After every scan, confirm the cart line’s product name, variant, quantity, unit price, label override/callout when applicable, tax, and fulfillment. Scanning the same item again can increase quantity through normal cart behavior; verify the displayed quantity rather than counting scanner beeps.",
        "If a scan produces no useful result, type or paste the complete printed value into Sell search and compare it with the product and variant’s saved Barcode and active product codes. Then search by product name to keep the sale moving without attaching an unrelated item.",
        "If more than one result appears for a supposedly unique barcode, stop and have an authorized catalog user resolve the duplicate product/variant codes. Do not choose whichever row appears first simply to complete the sale.",
        "For camera problems, confirm browser camera permission, close other apps using the camera, improve lighting and focus, or use the manual Capture code field. Cancel closes the camera without changing the cart.",
        "For hardware-scanner problems, test whether the device types the complete code once into a harmless text field, including any configured Enter suffix. Correct scanner pairing or prefix/suffix settings before retrying in a live cart.",
        "Before payment, compare the physical label with the final cart one more time. If the wrong row was selected, remove it and add the verified item; do not edit the description or price to disguise a mismatched catalog record."
      ],
      "controls": [
        {
          "name": "Barcode icon",
          "description": "Sell search indicator and, in the supported search-bar layout, the button that opens Scan Barcode with the device camera."
        },
        {
          "name": "Search products or scan barcode…",
          "description": "Product search field receiving typed text, keyboard-style scanner input, or a captured camera code."
        },
        {
          "name": "Result menu",
          "description": "Up to the ranked matching products and enabled variants available in the current Sell scope."
        },
        {
          "name": "Arrow Up / Arrow Down / Enter",
          "description": "Keyboard controls for reviewing and selecting the highlighted search result."
        },
        {
          "name": "Variant picker",
          "description": "Opens when a selected master product has enabled variants; a master barcode does not guess which variant is intended."
        },
        {
          "name": "Scan Barcode",
          "description": "Camera dialog using the environment-facing camera with a barcode scan region."
        },
        {
          "name": "Manual code field",
          "description": "Fallback for typing the complete MFC, UPC, or barcode when the camera cannot decode it."
        },
        {
          "name": "Capture code",
          "description": "Trims the manual value, sends it to Sell search, and closes the scanner; it does not bypass result review."
        },
        {
          "name": "Cancel",
          "description": "Stops and closes the camera without adding an item."
        },
        {
          "name": "Product barcode",
          "description": "Base barcode stored directly on the product."
        },
        {
          "name": "Active product code",
          "description": "Additional saved code; without a variant assignment it resolves at product level, and with a variant assignment it resolves only to that variant."
        },
        {
          "name": "Variant barcode",
          "description": "Barcode stored directly on an enabled variant."
        },
        {
          "name": "Exact barcode match",
          "description": "Case-insensitive equality after trimming; distinct from broad product-search ranking."
        },
        {
          "name": "LBL override code",
          "description": "Tenant-specific active, unexpired CentriPOS label token that can carry a mapped product/variant, printed price override, or callout note."
        },
        {
          "name": "Label added to register",
          "description": "Successful override-label confirmation."
        },
        {
          "name": "Label override is unavailable",
          "description": "The override row is missing, inactive, or expired."
        },
        {
          "name": "Label product is unavailable at this register",
          "description": "The override target is not in the current sellable product/variant set."
        },
        {
          "name": "Remote scan",
          "description": "Same-session scan broadcast from a connected customer-display or supported scanner surface."
        },
        {
          "name": "Remote scan paused",
          "description": "Checkout is busy or a live sale is locked by another user."
        },
        {
          "name": "Remote scan needs review",
          "description": "No single exact sellable match exists; resolve it in Register search."
        },
        {
          "name": "Availability enforcement",
          "description": "Product/category location/register restrictions and active rules still apply to scanner results."
        },
        {
          "name": "Cart verification",
          "description": "Required check of exact product, variant, quantity, price, tax, fulfillment, and any label override before payment."
        }
      ],
      "expectedResult": "The scanned code adds the correct product and variant once. If it does not match, no unrelated item should be left in the cart.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "build-edit-cart",
      "url": "https://platform.getcentri.com/centripos/build-edit-cart",
      "title": "Build and edit a cart",
      "summary": "Add catalog or custom items, attach the customer, edit quantities and prices, control tax and discounts, set line- or sale-level fulfillment, and reconcile the live totals before payment or saving.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Work in Register → Sell with the intended location and register selected. An open register is required for normal selling actions. The cart autosaves its current draft context, but an autosaved draft is not a completed receipt. Do not use an unrelated screenshot: the approved Amelia Grant / Harbor & Hearth Sell capture was rejected because the live route never finished loading.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Confirm the business, location, register, and cashier context before adding anything. If the register is closed, open the correct session through Session Control rather than building a sale in the wrong operational context.",
        "Find a catalog product through search, scan, or the visible product/quick-pick surface and tap it to add it. If the product has variants or serial requirements, make the prompted selection before checkout. Use Custom only for a legitimate noncatalog line and enter its real description, price, tax, and cost information as requested.",
        "Attach the customer as early as possible when pricing, tax exemption, delivery/shipping, account charging, customer history, or price-book rules depend on identity. Walk-in keeps the sale unattached; do not use it when the transaction belongs to a known customer.",
        "Read each cart card before editing: product and variant, fulfillment badge/address, line note, discount indicator, quantity, unit price, TAX state, and extended line total. Choose the product name or Details for product quick view when the item is a normal catalog product.",
        "Use minus, the quantity field, or plus to change quantity. The field does not accept zero. Removing the final positive unit through the decrement path crosses to a negative blind-return quantity, so use the trash control when the intent is simply to remove a normal sale line. Process linked returns from the supported return workflow instead of creating an accidental negative quantity.",
        "Edit the inline price carefully. A price below the catalog/variant base becomes a per-unit dollar discount; a price above base becomes a unit-price override and clears the line discount; restoring the base clears both. Invalid, blank, or negative entries revert to the displayed price.",
        "Toggle TAX on a line only when the sale’s tax treatment actually requires it. Turning tax off sets that line to zero tax; turning it back on restores the current default tax assignment. Confirm the customer’s exemption and destination/configuration rather than using the toggle as an informal discount.",
        "Open More… for a line to edit Discount, Note, and Fulfill. Choose dollar or percent discount and enter the value; the line shows its equivalent amount/percentage. Enter a line note only for information that should remain with that item.",
        "Set line fulfillment to Carry Out, Local Delivery, Pickup, or Shipping. Local Delivery and Shipping are disabled until a customer is attached. Changing fulfillment clears prior method, address, phone, pickup, date, and time selections so the new workflow can be completed cleanly.",
        "For Pickup, choose the pickup location, supported pickup method, date, and time when configured. The selling location becomes the default pickup/source location. For Delivery or Shipping, confirm the customer or custom address and phone, method, source location, schedule, and calculated or manual fulfillment charge.",
        "Use the sale-level Notes · Discount · Fulfillment tray when the setting applies to the whole cart. A sale discount is applied after line discounts and promotions, and the tax total is adjusted proportionally. If individual lines already have non-carry-out fulfillment, the sale-level controls reflect the grouped line fulfillment and offer Clear Fulfillments rather than silently overwriting those lines.",
        "Review promotion suggestions one by one. The check applies the displayed promotion and the X dismisses it; applied promotions appear separately and can be removed. Confirm the savings and eligible lines before continuing.",
        "Use Quote to calculate a delivery charge without silently committing the sale. Use Clear only when the entire active cart should be emptied; it is materially different from removing one line. Use Saved to locate unfinished sales, and Save Sale to intentionally retain the current cart for later work.",
        "Reconcile the totals area: merchandise Subtotal, fulfillment charge or credit, line discounts, promotions, sale discount, Tax, previously paid amount when resuming, and final Total/remaining balance. A fulfillment-only credit warning means the replacement method still needs to be selected and charged.",
        "Before Pay, verify every line’s identity, variant, quantity/sign, unit price or discount, tax state, note, source location, fulfillment method/address/date/time, and extended total. Verify the attached customer and sale-level notes/discount/fulfillment separately.",
        "Choose Pay only when the cart is ready for tender. The payment screen, signature policy, split payments, Charge to Account, layaway, and terminal actions are separate workflows; an edited cart alone has not taken payment, posted A/R, reduced inventory as a completed sale, or produced a receipt."
      ],
      "controls": [
        {
          "name": "Quote",
          "description": "Opens the delivery-pricing quote workflow."
        },
        {
          "name": "Walk-in",
          "description": "Uses an unattached customer context for a true walk-in sale."
        },
        {
          "name": "Custom",
          "description": "Adds a legitimate noncatalog item through the Custom Item dialog."
        },
        {
          "name": "Saved",
          "description": "Opens unfinished saved/parked sales; the count shows available items when nonzero."
        },
        {
          "name": "Clear",
          "description": "Immediately empties the active cart and closes/resets the Pay screen state; use it only when the whole cart should be discarded."
        },
        {
          "name": "Customer attachment",
          "description": "Drives customer history, price books, tax exemption, fulfillment identity, and account eligibility."
        },
        {
          "name": "Product name / Details",
          "description": "Opens quick product information for a normal catalog item."
        },
        {
          "name": "Minus / quantity / plus",
          "description": "Changes a nonreturn line quantity; zero is not retained as a normal quantity."
        },
        {
          "name": "Trash",
          "description": "Removes the selected normal sale line from the cart."
        },
        {
          "name": "Edit Price",
          "description": "Below base becomes a per-unit dollar discount; above base becomes an override; base clears both."
        },
        {
          "name": "TAX",
          "description": "Toggles the line between zero tax and the current default tax rate."
        },
        {
          "name": "More…",
          "description": "Opens the line editor for discount, note, and fulfillment."
        },
        {
          "name": "Line discount",
          "description": "Per-unit dollar or percentage reduction with an equivalent-value label."
        },
        {
          "name": "Line note",
          "description": "Text retained with the selected cart item."
        },
        {
          "name": "Line fulfillment",
          "description": "Carry Out, Local Delivery, Pickup, or Shipping plus supported address/source/schedule details."
        },
        {
          "name": "Source location",
          "description": "Inventory origin for a non-carry-out line; defaults to the selling location when appropriate."
        },
        {
          "name": "Notes · Discount · Fulfillment",
          "description": "Sale-level tray for whole-cart notes, discount, and fulfillment controls."
        },
        {
          "name": "Clear Fulfillments",
          "description": "Removes existing line-level fulfillment choices when the grouped cart uses them."
        },
        {
          "name": "Promotion suggestion",
          "description": "Explicit apply or dismiss decision showing the calculated savings."
        },
        {
          "name": "Fulfillment charge",
          "description": "Managed delivery/shipping fee with its own displayed price and tax state."
        },
        {
          "name": "Subtotal / discounts / tax / total",
          "description": "Live financial reconciliation before Pay."
        },
        {
          "name": "Save Sale",
          "description": "Intentionally retains unfinished work; it does not complete the transaction."
        },
        {
          "name": "Pay",
          "description": "Opens the separate payment workflow for the remaining balance."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest rejected /register/sell as rejected-loading, so this guide publishes no fabricated or screen-mismatched image."
        }
      ],
      "expectedResult": "Every cart line shows the intended quantity, authorized price or discount, fulfillment, and tax treatment, and the totals reconcile before payment.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "attach-customer",
      "url": "https://platform.getcentri.com/centripos/attach-customer",
      "title": "Find, create, attach, or remove the correct customer",
      "summary": "Search tenant customer records and enabled company bill-to associations, verify identity and alerts, create a genuinely new profile when needed, and attach the result so pricing, tax, fulfillment, accounts, and history use the intended customer.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Use Add customer in the Sell cart. Search starts after two characters, waits briefly while typing, ranks the best matches, and shows at most ten combined people/company bill-to results. Creating a customer from this control immediately attaches the new record. Removing the attachment does not delete the customer.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Choose Add customer in the cart. On phones the search opens full screen; on wider screens it opens a dropdown and closes when you click outside.",
        "Type at least two characters. The visible prompt supports name, customer code, email, and phone. The underlying lookup also matches company, contact role, address components, imported/source code, alternate phone lines, and enabled company bill-to names, then ranks the strongest matches.",
        "Wait for Searching… to finish and inspect every candidate. Results show name, All customers or Company bill-to, company, customer/customer-source code, phone, flags, and whether a company requester is required or optional. Similar names are not proof of identity.",
        "Select the exact customer only after comparing a stable identifier such as customer code, phone, email, company, or address. The selected customer chip replaces Add customer and displays its avatar/company icon, name, type, company, code, phone/source code, and alert indicators.",
        "Read the selected chip before continuing. A colored flag dot means a flagged customer note exists; a warning dot indicates pending duplicate candidates; an amber dot indicates internal notes; a saved-card badge reports vault cards. Open the profile instead of guessing what an indicator means.",
        "For an enabled Company bill-to result, choose Requested by when members are available. The selector states whether requester selection is required or optional. A required requester must be selected before an account invoice or company workflow that enforces it can continue.",
        "Click the attached customer chip to open the profile. Use the profile to review/edit contact details, addresses, notes/flags, duplicate matches, saved cards, groups/associations, sales/account activity, and saved sales according to permissions. Edits returned from the profile refresh the attached cart identity.",
        "If no existing record is correct, choose Add “query” as a new customer / Create new customer. The typed query seeds the Name field; correct it before saving. A name is required.",
        "Complete the new profile deliberately: primary email plus CC/BCC routing when needed, labeled primary and additional phone lines, company and contact role, address, tax-exempt status, active customer groups, and any configured accounting fields. Avoid entering temporary delivery-only information as permanent customer data unless the customer asked for it.",
        "Save the new customer. CentriPOS normalizes email routing and phone values, checks email/phone duplicates unless duplicate customers are allowed in tenant settings, assigns the customer ID/code, saves group memberships, reports Customer created, closes the creation panel, and attaches the new record to the cart.",
        "If a duplicate warning appears, stop and search again. Do not create a second record merely because two people share a name; compare email, phone, code, company, and address. Use the profile’s duplicate review/merge workflow when authorized.",
        "After attachment, verify any price-book changes, customer tax-exempt state, fulfillment options, account/layaway eligibility, and customer-facing contact/destination information. Attachment can change the effective cart price and tax context, so reconcile every line and the total again.",
        "To switch customers, remove the current attachment with the trash/remove control, then search and attach the correct record. Remove only detaches it from this active cart; it does not delete the customer profile. Recheck prices, tax, fulfillment, and account eligibility after removal or replacement.",
        "For a true walk-in, leave the cart unattached or use Walk-in. Do not detach a known customer merely to bypass an account limit, requester requirement, tax rule, or delivery contact requirement."
      ],
      "controls": [
        {
          "name": "Add customer",
          "description": "Opens customer lookup for the active cart."
        },
        {
          "name": "Search query",
          "description": "Requires at least two characters and debounces briefly before lookup."
        },
        {
          "name": "Search results",
          "description": "Ranked tenant matches from people plus enabled company bill-to associations."
        },
        {
          "name": "All customers",
          "description": "Normal customer/contact result."
        },
        {
          "name": "Company bill-to",
          "description": "Enabled association result that attaches its designated billing customer."
        },
        {
          "name": "Requested by",
          "description": "Company member selector labeled required or optional from association settings."
        },
        {
          "name": "Customer flag dot",
          "description": "Color-coded pinned flag note; open the profile for its content."
        },
        {
          "name": "Duplicate dot",
          "description": "Pending possible duplicate-record alert."
        },
        {
          "name": "Internal-note dot",
          "description": "Indicates at least one customer note exists."
        },
        {
          "name": "Saved-card badge",
          "description": "Count of vaulted cards; open the profile to review authorized card details."
        },
        {
          "name": "Customer code / Imported code",
          "description": "Stable identifiers useful when names collide."
        },
        {
          "name": "Create new customer",
          "description": "Opens the new profile form and seeds Name from the search query."
        },
        {
          "name": "Duplicate check",
          "description": "Blocks a new/edited profile matching existing email or phone unless tenant settings allow duplicates."
        },
        {
          "name": "Customer created",
          "description": "Successful creation outcome; the new profile is attached automatically."
        },
        {
          "name": "Customer profile",
          "description": "Details, addresses, notes/flags, history, accounts, groups/associations, duplicates, saved cards, and communications according to permissions."
        },
        {
          "name": "Remove attached customer",
          "description": "Detaches the record from the cart without deleting it."
        },
        {
          "name": "Walk-in",
          "description": "Keeps a true walk-in sale unattached."
        },
        {
          "name": "Cart recalculation",
          "description": "Customer attachment/removal can change price-book prices, tax exemption, fulfillment, and account actions."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant / Harbor & Hearth manifest rejected /register/sell as rejected-loading, so this guide publishes no fabricated or mismatched customer-cart image."
        }
      ],
      "expectedResult": "The correct customer name appears on the cart and the sale inherits only that customer’s intended addresses, account options, receipt destinations, and history context.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "discounts-taxes",
      "url": "https://platform.getcentri.com/centripos/discounts-taxes",
      "title": "Apply discounts and understand tax",
      "summary": "Use line, promotion, and sale discounts correctly; inspect the assigned tax source; and verify how taxable lines, exemptions, and fulfillment charges change the total.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Discount and tax controls are part of Register → Sell rather than a separate screen. CentriPOS does not ask for a discount reason in the current cart UI. Apply only discounts and tax overrides authorized by store policy, and verify every affected line before payment.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Open Register → Sell and confirm the business, location, register, and open session. Add the intended product or variant and set the correct quantity before calculating a discount.",
        "For a line discount, choose More… beneath that item. On desktop it expands Discount, notes, and fulfillment inline; on touch-mobile it opens the line-item editor sheet.",
        "Choose $ or % under Discount and enter the value. A percent discount applies to that line’s full gross amount. A fixed dollar line discount is per unit, so $10 on quantity 3 removes $30—not $10—from the line.",
        "Read the equivalent value shown beside the field: a fixed discount displays its percentage equivalent, while a percentage displays the dollar amount. Confirm the discounted line total and struck-through gross total.",
        "For a cart-wide discount, open the blue Notes · Discount · Fulfillment tray at the bottom of the cart. Under Sale Disc., choose $ or % and enter the value. A fixed Sale Discount applies once to the cart’s post-line-discount subtotal.",
        "When switching an existing Sale Discount between $ and %, CentriPOS converts the current value to an approximate equivalent based on the current raw subtotal. Recheck the displayed amount after switching and after changing cart items or quantities.",
        "Review suggested promotions above the cart. Apply only the intended promotion; applied promotions appear as a named Promo Discount and can be removed with X. Promotion eligibility and stacking come from the promotion configuration, not this manual discount control.",
        "Understand the calculation order. CentriPOS calculates each line’s gross amount, subtracts its line discount, calculates line tax on that net line, then subtracts applied promotion and sale discounts from the combined line subtotal. It reduces the already-calculated line tax proportionally by the same final-subtotal ratio.",
        "Read Line Discounts, Promo Discount, and Sale Discount as separate rows in the totals area. They are recorded separately enough to explain the cart; do not combine them mentally and then enter another manual discount.",
        "Read the TAX switch on each nonreturn item. On applies the current resolved default rate to that line; Off sets that line to zero tax. This is a manual line override, not a change to the saved product, location, register, or store tax settings.",
        "Use Add tax or Remove tax beside the Tax total to change all current cart lines at once. If every line is zero, Add tax restores the resolved default rate to every line; otherwise Remove tax sets every line to zero. Review mixed carts before using this shortcut.",
        "Choose the information icon beside Tax to open Assigned tax. It shows the tax-rate name, percentage, and source: Register, Location, or Store default, plus Taxed lines, No-tax lines, and the number of line overrides.",
        "Understand default precedence. A register default tax overrides a location default, which overrides the tenant/store default. If none exists, CentriPOS attempts to create a location default through ZIPTax when the location has usable address data; otherwise it shows No tax default configured at 0%.",
        "A register whose name matches Billed Account or Billed Accounts is intentionally resolved to a zero-tax register assignment. Verify that special operating context before assuming a missing tax configuration.",
        "When an attached customer is marked tax exempt, every line resolves to zero tax and Assigned tax states Attached customer is tax exempt. Detaching the customer or changing their tax-exempt status can recalculate the cart; confirm the customer record and exemption evidence first.",
        "Delivery and shipping charge lines follow the selected fulfillment method’s Apply tax setting. The method picker labels a priced method with • no tax when its charge is configured nontaxable. Do not toggle the fee line without confirming policy.",
        "Returns and exchanges can carry the exact original tax amount as a fixed negative override so the return offsets original tax rather than calculating today’s default rate. Do not replace that preserved return tax with a new manual toggle.",
        "Before payment, compare quantity × unit price, line discounts, promotion discount, sale discount, discounted subtotal, taxed/no-tax line counts, tax source and rate, fulfillment charges, Tax, and Total. Correct the cart once before starting a terminal payment.",
        "Complete one controlled sale and inspect the receipt detail. Each line stores its discount amount, discount type/input, tax amount, tax rate, and default tax-rate ID when applicable; the sale stores total discount and adjusted tax. The receipt totals must agree with the final cart.",
        "If the tax assignment says unconfigured, do not guess a tax rate. An authorized administrator should add a valid location address and sync ZIPTax or choose the approved tax rate in settings, then rebuild or carefully review the cart before payment."
      ],
      "controls": [
        {
          "name": "More…",
          "description": "Opens the line-item editor containing Discount, note, and fulfillment controls."
        },
        {
          "name": "Line $ discount",
          "description": "Fixed amount removed per unit on that line. Quantity multiplies the entered value."
        },
        {
          "name": "Line % discount",
          "description": "Percentage of the full absolute line gross removed from that line."
        },
        {
          "name": "Equivalent value",
          "description": "Shows the percentage equivalent of a fixed line discount or dollar equivalent of a percentage line discount."
        },
        {
          "name": "Sale Disc. $",
          "description": "One fixed discount applied to the combined post-line-discount subtotal, not once per item."
        },
        {
          "name": "Sale Disc. %",
          "description": "Percentage applied to the combined post-line-discount subtotal."
        },
        {
          "name": "Suggested promotion",
          "description": "Eligible configured promotion offered above the cart; applying it adds a named promotion discount."
        },
        {
          "name": "Applied promotion X",
          "description": "Removes that promotion from the cart without deleting the promotion configuration."
        },
        {
          "name": "Line Discounts",
          "description": "Total of manual discounts stored on individual cart lines. Returned discounts are shown as a positive offset when applicable."
        },
        {
          "name": "Promo Discount",
          "description": "Combined amount from applied configured promotions."
        },
        {
          "name": "Sale Discount",
          "description": "Manual cart-wide discount calculated after line discounts."
        },
        {
          "name": "Discount calculation order",
          "description": "Line gross → line discount → line tax; promotion and sale discounts then reduce subtotal and tax proportionally."
        },
        {
          "name": "TAX switch",
          "description": "Line-level toggle between zero and the resolved default tax rate for a nonreturn line."
        },
        {
          "name": "Add tax / Remove tax",
          "description": "All-current-lines shortcut: restore the default to all only when every line is zero, otherwise set every line to zero."
        },
        {
          "name": "Assigned tax",
          "description": "Popover showing tax name, rate, source, taxed/no-tax line counts, and override or customer-exemption context."
        },
        {
          "name": "Register tax source",
          "description": "Highest-precedence saved default for the current register."
        },
        {
          "name": "Location tax source",
          "description": "Used when the register has no valid saved tax default."
        },
        {
          "name": "Store default tax source",
          "description": "Tenant-wide default used when neither register nor location provides one."
        },
        {
          "name": "ZIPTax fallback",
          "description": "Attempts to create a location tax default from its address when no saved default exists."
        },
        {
          "name": "No tax default configured",
          "description": "Zero-rate state after no register, location, store, or successful ZIPTax assignment can be resolved."
        },
        {
          "name": "Billed Accounts 0% tax",
          "description": "Intentional zero-rate register assignment when the register name matches Billed Account(s)."
        },
        {
          "name": "Tax-exempt customer",
          "description": "Attached customer flag that forces every current line’s effective rate to zero."
        },
        {
          "name": "Fulfillment Apply tax",
          "description": "Configuration on a delivery or shipping method deciding whether its generated charge line uses the default rate or zero."
        },
        {
          "name": "Return tax override",
          "description": "Fixed negative tax preserved from an original sale line so a return offsets historical tax."
        },
        {
          "name": "Taxed lines / No-tax lines",
          "description": "Counts of current cart lines with an effective rate above zero or equal to zero."
        },
        {
          "name": "Tax total",
          "description": "Sum of line tax after proportional promotion and sale-discount adjustment."
        },
        {
          "name": "Receipt tax fields",
          "description": "Persisted line tax amount, rate, and applicable tax-rate reference supporting the completed receipt total."
        },
        {
          "name": "No discount reason field",
          "description": "The current Sell cart accepts discount type and value but does not ask for a reason; follow business authorization policy outside that nonexistent control."
        }
      ],
      "expectedResult": "Each intended discount appears exactly once at the correct line, promotion, or sale level; fixed line discounts multiply by quantity while fixed sale discounts do not; the assigned register → location → store/ZIPTax source, exemptions, line overrides, and fulfillment tax settings explain every taxed or zero-tax line; and the completed receipt’s persisted line and sale totals agree with the final cart.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "fulfillment-on-sale",
      "url": "https://platform.getcentri.com/centripos/fulfillment-on-sale",
      "title": "Set carry out, pickup, delivery, or shipping on a sale",
      "summary": "Choose whole-sale or per-line fulfillment, collect the correct destination and contact details, select location-scoped methods and schedules, and reconcile the generated fulfillment charge before saving or payment.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "Fulfillment lives under More… → Notes · Discount · Fulfillment in the Sell cart and under More… on each line. Carry Out and Pickup can be selected without an attached customer; Local Delivery and Shipping require one. The approved Harbor & Hearth Sell screenshot was rejected-loading, so this guide uses no substitute image.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Attach the correct customer before choosing Local Delivery or Shipping. Those options are disabled as customer required when no customer is attached. Pickup can remain unattached, but attaching the customer is still recommended for communication and history.",
        "Decide whether fulfillment applies to the whole sale or differs by item. Use the sale-level Fulfill selector when all merchandise follows one method. Open a line’s More… editor when only that item differs. Once any line has non-carry-out fulfillment, the sale-level tray reads Mixed by Line Item and does not silently overwrite the individual lines.",
        "Choose Carry Out for merchandise leaving with the customer now. Changing the whole-sale type resets the previous delivery/shipping method, pickup store/method, and related sub-method state; switching away also clears the sale delivery address.",
        "For Pickup, choose the pickup method when configured and select the store. The selling store becomes the default pickup/source location, but the searchable store control can change it. Pickup method selection currently does not add a price even if its label displays a configured base price, so verify policy and totals rather than promising a pickup fee.",
        "Choose a pickup date when required by the configured pickup schedule. After a date is selected, choose an available pickup time/window. A single configured pickup method may be selected automatically at line level; still verify it.",
        "For Local Delivery, first confirm Delivery Details. Choose Customer’s Phone or Different Phone and Customer’s Address or Different Address. A new phone/address entered under the customer option is saved to that profile; an explicit different contact/destination applies to this sale. Confirm requires a nonblank address.",
        "Choose the Local Delivery method shown for this location/register. Methods can be globally available or scoped to location/register; when an available exclusive scoped method exists, unscoped choices are hidden. A method marked no method price removes the managed delivery-charge line.",
        "Review the calculated delivery price and Pricing explanation. Distance pricing uses the configured active location/hub and destination geocoding, then applies the method’s base/location price, distance multiplier/adjustment, and rounding behavior. If a manager manually edits Price, the cart preserves that manual fulfillment charge for the selected method instead of immediately replacing it with recalculation.",
        "Choose a delivery date and time according to the configured delivery schedule. Past dates appear only for a delivery method explicitly configured to allow past fulfillment dates. Confirm the displayed address and phone before continuing.",
        "For Shipping, confirm the destination address and phone, choose a configured Shipping method, and review the automatic base charge plus its TAX or NO TAX state. Complete the additional Shipping options—such as the configured shipping workflow/destination—when that panel appears.",
        "Choose Ship on or Deliver by date only when the tenant’s shipping schedule is configured as scheduled. Open-ended shipping does not require the sale-level date control. Shipping does not use the delivery time picker.",
        "For per-line fulfillment, open More… on each product and choose Carry Out, Local Delivery, Pickup, or Shipping. Delivery and Shipping require the attached customer. Set the line’s source location, destination, date/time, pickup location/method, and method IDs as offered. The cart displays a fulfillment badge and address on each affected line.",
        "When line-level fulfillment exists, use Clear Fulfillments only if every line should return to Carry Out. It resets fulfillment type, delivery/shipping method, address/phone, pickup location, date, and time across the cart.",
        "Use Quote near the cart header for a delivery estimate before applying it. Enter/select the address and delivery method, choose Calculate, and review price plus calculation metadata. Apply to Sale requires a customer, a nonempty cart, and a calculated result; Save Address to Customer requires an attached customer and parsed street address.",
        "Inspect the managed fulfillment-charge line and totals. Confirm the selected method, price, TAX/NO TAX state, distance calculation where used, and any return/exchange fulfillment credit. A cart containing only a fulfillment credit warns that a replacement method still needs to be selected to charge the difference.",
        "Before Save Sale or Pay, verify every merchandise line’s fulfillment badge, source location, customer/destination contact, method, date/time, pickup store, and the receipt-level fulfillment summary. Saving or paying persists the selected fulfillment as pending work; it does not itself mark pickup, delivery, or shipment completed. Use Sales → Fulfillment for operational status afterward."
      ],
      "controls": [
        {
          "name": "Carry Out",
          "description": "Immediate customer possession; no scheduled fulfillment details."
        },
        {
          "name": "Pickup",
          "description": "Customer collection at a selected store with supported method/date/time."
        },
        {
          "name": "Local Delivery",
          "description": "Customer-required delivery workflow using configured location/register methods and destination details."
        },
        {
          "name": "Shipping",
          "description": "Customer-required shipment workflow using configured shipping methods and options."
        },
        {
          "name": "Mixed by Line Item",
          "description": "At least one merchandise line has non-carry-out fulfillment; sale-level type replacement is suppressed."
        },
        {
          "name": "Clear Fulfillments",
          "description": "Resets every line to Carry Out and clears method, destination, pickup, date, and time fields."
        },
        {
          "name": "Customer’s Phone / Address",
          "description": "Uses profile data; newly entered missing data under these options is saved to the profile."
        },
        {
          "name": "Different Phone / Address",
          "description": "Sale-specific destination/contact, including company and attention fields for a custom address."
        },
        {
          "name": "Local Delivery method",
          "description": "Enabled method filtered by location/register scope and exclusive availability rules."
        },
        {
          "name": "Shipping method",
          "description": "Enabled tenant method whose base price and tax flag create/update the managed charge."
        },
        {
          "name": "Pickup method",
          "description": "Configured pickup choice; current Sell code does not yet apply its displayed base price."
        },
        {
          "name": "Store",
          "description": "Pickup location; defaults to the selling location when available."
        },
        {
          "name": "Source location",
          "description": "Inventory origin retained for non-carry-out line fulfillment."
        },
        {
          "name": "Date / Ship on / Deliver by",
          "description": "Schedule field shown according to fulfillment type and tenant scheduling mode."
        },
        {
          "name": "Time preference",
          "description": "Configured pickup/delivery window available after selecting a required date."
        },
        {
          "name": "Price",
          "description": "Managed delivery/shipping charge; valid nonnegative manual edits become method-specific overrides."
        },
        {
          "name": "TAX / NO TAX",
          "description": "Tax treatment of the managed fulfillment charge."
        },
        {
          "name": "Quote",
          "description": "Standalone delivery calculation using address and method before Apply to Sale."
        },
        {
          "name": "Save Address to Customer",
          "description": "Writes the parsed quote destination to the attached customer profile."
        },
        {
          "name": "Apply to Sale",
          "description": "Applies the calculated delivery address, method, fulfillment type, metadata, and managed charge."
        },
        {
          "name": "Fulfillment badge",
          "description": "Per-line cart evidence of Delivery, Shipping, or Pickup and its destination/location."
        },
        {
          "name": "Pending fulfillment",
          "description": "Saved/completed-sale state that enters the Fulfillment Center; not proof of operational completion."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant / Harbor & Hearth manifest marks /register/sell rejected-loading, so no invented or mismatched image is published."
        }
      ],
      "expectedResult": "Every cart line carries the correct pickup, delivery, or shipping badge and the sale shows the intended location, date or window, address, instructions, and charge.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "take-payment",
      "url": "https://platform.getcentri.com/centripos/take-payment",
      "title": "Take payment and complete a sale",
      "summary": "Review the payable total, allocate one or more allowed tenders, complete cash, integrated-card, saved-card, account, layaway, or reference prompts, and verify the receipt closes exactly once.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Checkout",
      "introduction": "Payment methods come from enabled store configuration plus integrated CentriPay capabilities for the active context. Cash is always presented by the Pay screen; other manual types are channel-filtered, and integrated options depend on provider setup, device support, customer attachment, saved tokens, original-payment eligibility, and terminal assignment. Never refresh, clear the cart, switch context, or retry an uncertain processor request.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Before choosing Pay, verify the cart/customer, line quantities, discounts, tax, fulfillment, total, business/location/register, and open session. Resolve serial-number, customer, fulfillment, or authorization prompts before collecting money.",
        "Open Pay and read Total or Refund due, Balance, and any already-applied payment rows. The Amount to collect defaults to the full remaining balance; choose it to edit the draft amount before selecting a method when creating a split payment.",
        "Choose Cash for the configured cash workflow. Review Cash due, any cash-rounding discount/adjustment and adjusted total, enter Cash tendered, or choose Exact/configured denomination presets. When tendered meets the due amount, CentriPOS calculates Change Due; when it is smaller, only that partial cash amount is applied.",
        "Choose a configured manual payment type for check, external gateway, financing, gift/other tender, or the business-defined method. Enter an amount no greater than Remaining. When the type requires or offers a reference, enter the check number or external transaction ID exactly; a required blank reference prevents Apply.",
        "Expand Integrated Payments for available card paths. Tap to Pay appears only in the supported native iOS app. Charge Saved Card requires configured CentriPay, an attached customer, and a usable saved token. Payanywhere requires a paired terminal and can offer a picker when several devices exist.",
        "For a saved card, choose the exact masked card and expiration, enter the amount, and submit once. A decline does not add the payment. On a successful gateway or Cloud-vault charge, CentriPOS adds the integrated reference and applies only the requested amount.",
        "For Payanywhere, choose the terminal, amount, and Send once. Keep both screens visible through Sending and Waiting for customer card. An approved payment is added once and can auto-close the sale; a timeout is not proof of failure. Follow the dedicated terminal guide before any resend, manual completion, clear, or cancel.",
        "After each applied tender, review the payment row’s method/label, amount, and reference, then read Remaining. Remove an incorrect non-finalized allocation with its row control before collecting the next tender. Do not remove or recreate an already processed integrated charge to change its label.",
        "For split tender, repeat amount and method selection until Remaining reaches $0.00. The Pay screen prevents an amount above Remaining. Cash rounding is calculated for the cash portion and can adjust the final payable total when cash completes the balance.",
        "When Remaining is still positive, Save Sale can park the current sale with its applied payments when supported. Layaway and Charge to Account require an attached customer. Do not use either as a generic way to bypass a failed card or missing payment authorization.",
        "For Charge to Account, open Invoice details, complete configured account fields, and attach only documents belonging to that customer invoice. Confirm the customer’s terms, credit limit/policy, balance, invoice recipient, due information, and permissions before billing the remainder.",
        "When the allocation reaches zero, CentriPOS normally auto-completes the sale once using a fingerprint of the applied payments. The Completed state shows the total and number of payments. If a Complete Sale button remains, choose it once and wait while Completing sale… is shown.",
        "On the completed receipt, verify sale number, total, each tender and reference, cash tendered/change/rounding, processor approval details, account balance or remaining balance as applicable, customer, fulfillment, and receipt delivery. If payment succeeded but receipt closure failed, retry closing the receipt—not the payment.",
        "If you choose Cancel before completion, confirm whether any integrated processor charge or manual payment was already applied. Canceling the Pay panel is not a refund, reversal, or guarantee that an in-flight terminal request stopped. Reconcile first, then resume or safely correct the sale."
      ],
      "controls": [
        {
          "name": "Total / Refund due",
          "description": "Full amount represented by the current payment or refund flow."
        },
        {
          "name": "Balance / Remaining",
          "description": "Amount not yet allocated to a tender."
        },
        {
          "name": "Amount to collect",
          "description": "Draft tender amount, initially the full remaining balance and editable for split payment."
        },
        {
          "name": "Applied payment row",
          "description": "Method/label, optional underlying payment type, reference, and signed amount already allocated."
        },
        {
          "name": "Remove payment",
          "description": "Removes the local allocation row; it does not reverse a processor transaction."
        },
        {
          "name": "Cash",
          "description": "Built-in cash path with rounding, tendered amount, denomination presets, and change."
        },
        {
          "name": "Cash due",
          "description": "Cash amount after applicable configured rounding."
        },
        {
          "name": "Cash rounding discount / adjustment",
          "description": "Difference between base amount and cash-payable amount, carried into the completed sale when cash closes the balance."
        },
        {
          "name": "Cash tendered",
          "description": "Physical amount received from the customer."
        },
        {
          "name": "Change Due",
          "description": "Cash tendered above the rounded cash due."
        },
        {
          "name": "Manual payment type",
          "description": "Enabled, channel-appropriate non-integrated or externally recorded tender."
        },
        {
          "name": "Payment reference",
          "description": "Configured check number or external/gateway transaction identifier; can be required or optional by type."
        },
        {
          "name": "Integrated Payments",
          "description": "Expandable group for Tap to Pay, saved/original card, and Payanywhere terminal paths."
        },
        {
          "name": "Tap to Pay",
          "description": "Native iOS contactless payment plugin; unavailable in a normal unsupported browser shell."
        },
        {
          "name": "Charge Saved Card",
          "description": "Configured NMI/Cloud vault token charge requiring an attached customer and saved method."
        },
        {
          "name": "Original Card on File",
          "description": "Refund-only integrated original payment target when the source sale provides an eligible card."
        },
        {
          "name": "Payanywhere",
          "description": "CentriPay Cloud request sent to the selected paired terminal."
        },
        {
          "name": "Terminal picker",
          "description": "Appears when multiple location terminals are available; identifies the resolved default."
        },
        {
          "name": "Terminal status",
          "description": "Sending, awaiting customer, approved, declined, failed, or expired plus response/transaction evidence."
        },
        {
          "name": "Save Sale",
          "description": "Parks the remaining balance with current allocations when the workflow supports it."
        },
        {
          "name": "Layaway",
          "description": "Customer-required remaining-balance workflow; not a substitute for a failed tender."
        },
        {
          "name": "Charge to Account",
          "description": "Customer-required account invoice flow with configured fields and optional invoice attachments."
        },
        {
          "name": "Invoice details",
          "description": "Tenant-configured account fields and invoice documents collected before billing the balance."
        },
        {
          "name": "Completed",
          "description": "Remaining is zero and the payment allocation is ready/being used to close the sale."
        },
        {
          "name": "Auto-completion fingerprint",
          "description": "Prevents the same unchanged payment allocation from automatically closing the sale more than once."
        },
        {
          "name": "Complete Sale",
          "description": "Manual final closure control when still shown; disabled while completion is in flight."
        },
        {
          "name": "Cancel",
          "description": "Closes the payment UI; it does not reverse an applied or in-flight processor payment."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth capture set has no safe final-state Pay screen, so this guide uses no fabricated checkout image."
        }
      ],
      "expectedResult": "Remaining reaches $0.00, the sale completes once, and the receipt screen shows the successful tenders and final total.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "cash-payment",
      "url": "https://platform.getcentri.com/centripos/cash-payment",
      "title": "Accept cash and make change",
      "summary": "Record full or partial cash exactly as the customer tenders it, apply the configured rounding rule without hiding a split balance, and reconcile the resulting cash, change, receipt, and register session.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Checkout",
      "introduction": "Cash is a hardcoded checkout choice and resolves to the configured Cash payment type when available. Opening Cash Payment pre-fills Cash tendered with the rounded amount due. The recorded payment stores applied amount, physical tendered amount, and change given separately; only a cash payment that completes the remaining sale balance applies the final cart-level cash-rounding adjustment.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Before taking cash, confirm the business, location, register, open session, cashier, cart lines, tax, discounts, fulfillment charges, customer when required, and exact balance. Choose Pay only when the cart is ready to post.",
        "For a split payment, enter a positive payment amount before choosing Cash. The draft is capped to the current remaining balance. With no valid draft amount, Cash uses the whole remaining balance. Do not enter the total cash handed over in the split-amount field; that field sets how much of the sale Cash should apply.",
        "Choose Cash. Cash Payment opens and automatically pre-fills Cash tendered with Cash due, so Exact initially appears selected/disabled. Cash due is the requested cash allocation after the configured increment/direction is applied; it can differ from the unrounded draft or remaining balance.",
        "Read any rounding disclosure. For a partial cash allocation, CentriPOS rounds that allocation independently. For cash that completes the current balance, it searches for a valid rounded remaining amount and matching cart-level adjustment so the final adjusted total reconciles with earlier tenders.",
        "Cash rounding uses the Cash payment type’s increment. An invalid increment or one cent or less behaves as ordinary currency rounding. Direction down floors to the increment, up ceilings to it, and any other value uses nearest. The screen labels a negative adjustment as cash rounding discount and a positive one as cash rounding adjustment.",
        "Replace Cash tendered with the physical amount handed over, choose Exact, or choose a quick amount. The field accepts cents, requires a value greater than zero to enable the action, and Enter submits the same confirmation as the button. Recount the cash before submitting.",
        "Understand quick amounts. CentriPOS normalizes the tenant’s positive configured denominations, falls back to $5, $10, $20, $50, and $100 when none are usable, calculates the next higher multiple of each denomination above Cash due, removes duplicates, sorts ascending, and displays at most four. A quick amount is a tender suggestion, not cash already received.",
        "When Cash tendered is below Cash due, the action reads Apply $X Cash. CentriPOS applies the smaller of the tendered value and the unrounded draft allocation, records no change, returns to payment methods, and leaves the rest of the sale balance for another tender. Verify the remaining balance before continuing.",
        "When Cash tendered covers the requested Cash due but that allocation is still smaller than the whole remaining balance, the action reads Apply — Cash $X and can show Change $Y. It records the rounded requested cash allocation and the physical tender/change, then returns for the remaining balance.",
        "When the rounded Cash due covers the whole remaining balance, the action reads Complete — Cash $X and can show Change $Y. Change Due equals tendered minus rounded Cash due, never less than zero. Count the change independently, hand it over once, and choose Complete once.",
        "Use Back to return to payment methods and clear Cash tendered without recording a payment. Do this when the customer changes method or the amount is uncertain. Do not close, refresh, or switch registers while tender or completion state is uncertain.",
        "After confirmation, the payment row stores Cash amount applied, tendered, and changeGiven. The sale completes automatically only when the recomputed adjusted remaining balance is at or below zero; otherwise Cash Payment closes and the payment-method list returns.",
        "Open the completed receipt and verify sale total, any cash-rounding discount/adjustment, Cash applied, tendered amount, change given, other split tenders, remaining balance zero, cashier, register, and time. A success screen without the expected receipt/payment record is not reconciliation.",
        "At register close, customer cash tenders—including change reflected in sale payment lines—contribute to Payment Types. They do not create individual Cash drawer movement rows. Opening float and manual Add/Remove cash are separate movements; expected drawer cash combines those movement effects with the Cash payment total.",
        "For a shortage, overage, duplicate, wrong change, or uncertain completion, stop compensating transactions. Preserve the safe receipt/sale reference, register session, cashier, time, cart total, rounding rule, split allocations, applied Cash, tendered, change, and observed drawer evidence. Use the authorized correction/refund and closure workflows rather than rewriting history.",
        "No screenshot is published because the approved Amelia Grant Harbor & Hearth capture set contains no safe final-state Cash Payment dialog. The Sell capture was rejected for an unresolved loading state, so no generic checkout or invented cash screen is substituted."
      ],
      "controls": [
        {
          "name": "Cash",
          "description": "Hardcoded checkout option that resolves to the configured Cash payment-type ID when present."
        },
        {
          "name": "Draft payment amount",
          "description": "Requested cash allocation for a split; capped at the current remaining balance."
        },
        {
          "name": "Cash due",
          "description": "Rounded amount CentriPOS intends to apply for this cash allocation."
        },
        {
          "name": "Automatic exact prefill",
          "description": "Opening Cash Payment sets Cash tendered to Cash due."
        },
        {
          "name": "Cash tendered",
          "description": "Physical amount handed to the cashier; must parse to more than zero."
        },
        {
          "name": "Exact",
          "description": "Restores Cash tendered to Cash due and is disabled while already exact."
        },
        {
          "name": "Quick amounts",
          "description": "Up to four next-higher denomination multiples above Cash due."
        },
        {
          "name": "Default denominations",
          "description": "$5, $10, $20, $50, and $100 when configured values are absent/invalid."
        },
        {
          "name": "Cash rounding increment",
          "description": "Configured increment greater than one cent; otherwise normal cent rounding."
        },
        {
          "name": "Down / Up / Nearest",
          "description": "Floor, ceiling, or ordinary nearest-increment direction."
        },
        {
          "name": "Cash rounding discount",
          "description": "Negative adjustment disclosed when the rounded amount lowers the applicable total."
        },
        {
          "name": "Cash rounding adjustment",
          "description": "Positive adjustment disclosed when the rounded amount raises the applicable total."
        },
        {
          "name": "Apply $X Cash",
          "description": "Tender is below Cash due; applies a partial amount with zero change."
        },
        {
          "name": "Apply — Cash $X",
          "description": "Requested cash allocation is covered but another sale balance remains."
        },
        {
          "name": "Complete — Cash $X",
          "description": "Cash covers the final rounded remaining balance and posts completion."
        },
        {
          "name": "Change Due",
          "description": "Maximum of zero and tendered minus rounded Cash due."
        },
        {
          "name": "Enter key",
          "description": "Runs the same cash confirmation handler as the primary action."
        },
        {
          "name": "Back",
          "description": "Clears the cash entry and returns without recording it."
        },
        {
          "name": "Recorded amount",
          "description": "Cash applied toward the sale, separate from physical tender."
        },
        {
          "name": "tendered / changeGiven",
          "description": "Stored physical cash-in and cash-out evidence on the payment row."
        },
        {
          "name": "Register Payment Types",
          "description": "Session cash tender total used at close; individual sales are not manual cash-movement rows."
        },
        {
          "name": "No exact screenshot",
          "description": "The real demo cash dialog did not reach an approved safe final state."
        }
      ],
      "expectedResult": "The cash tender is recorded in the active register session, the displayed change matches cash received minus the balance, and the completed receipt shows cash payment.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "card-terminal",
      "url": "https://platform.getcentri.com/centripos/card-terminal",
      "title": "Take a card payment with a terminal",
      "summary": "Send an exact sale or refund amount to the correct Payanywhere terminal, follow the live CentriPay status, and close the receipt without duplicating an approved request.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Checkout",
      "introduction": "A terminal payment is an integrated CentriPay Cloud intent plus a device transaction, not a manual card notation. Keep the Pay screen and physical terminal visible until CentriPOS reaches a confirmed final state. Never refresh, clear the cart, close the register, remove the allocation, or send again while the first result is uncertain.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "On the completed cart, choose Pay and verify Total, Balance, customer when attached, business/location/register, and open session. Expand Integrated Payments if needed.",
        "Choose Payanywhere. If it says No terminals paired — add in Admin → Locations, stop and have an administrator configure the current context. Do not substitute a manual payment type just to finish the receipt.",
        "When multiple devices appear, choose the intended terminal from the picker and verify its physical name. The resolved assignment is labeled default. Confirm the customer-facing amount before sending.",
        "Enter or keep the amount, which cannot exceed Remaining. Choose Send [amount] to CentriPay Cloud once. CentriPOS first creates a payment intent, then sends it to the terminal and displays Sending request to terminal.",
        "When the terminal acknowledges the request, CentriPOS shows Waiting for customer card and a Terminal transaction reference. Wake a sleeping PAX, then ask the customer to follow the device prompts for dip, tap, swipe, or keyed entry on the terminal.",
        "Wait while CentriPOS polls and listens for realtime updates. Do not use Complete manually during its initial 10-second safety delay. The terminal and CentriPOS can update at slightly different moments.",
        "On Approved, CentriPOS records a single CentriPay Cloud allocation with the processor or terminal reference. When that allocation reaches the full total, the sale normally closes automatically. If the screen says payment approved but the receipt did not finish closing, review and tap Pay to retry receipt closure only.",
        "On Declined or Failed, read the response code/message. No successful allocation is added. Resolve the card, customer, device, or provider issue, then choose another tender or send a genuinely new request only after the first is conclusively failed.",
        "On timeout/Expired or lost response, do not assume the card was not charged. Check the physical terminal and CentriPay/Payanywhere transaction history using amount, time, terminal transaction, and payment-intent reference. Follow Fix a payment terminal problem before clearing, stopping, manually completing, or resending.",
        "Use Complete manually only when the physical terminal clearly shows the exact amount approved and the POS is still waiting. CentriPOS checks status once more, then if still unresolved records payment pending processor confirmation. Verify later processor detail on the receipt.",
        "After the receipt closes, verify sale number, card brand/last four when returned, approval/response, terminal and processor references, amount, other split tenders, balance, and receipt delivery. A successful terminal screen alone is not the final bookkeeping check."
      ],
      "controls": [
        {
          "name": "Integrated Payments",
          "description": "Expandable Pay area containing supported Tap to Pay, saved/original card, and Payanywhere paths."
        },
        {
          "name": "Payanywhere",
          "description": "Terminal path using a CentriPay Cloud payment intent and paired device."
        },
        {
          "name": "No terminals paired",
          "description": "No device is usable in the active context; configure under Admin → Locations."
        },
        {
          "name": "Terminal picker",
          "description": "Device selector shown with multiple location terminals; the resolved assignment can be labeled default."
        },
        {
          "name": "Amount",
          "description": "Requested integrated payment amount, capped at the remaining balance."
        },
        {
          "name": "Send to CentriPay Cloud",
          "description": "Creates the intent and sends it to the selected terminal once."
        },
        {
          "name": "Sending request to terminal",
          "description": "Request creation/delivery is in progress; do not submit again."
        },
        {
          "name": "Waiting for customer card",
          "description": "Device acknowledged the request and awaits/works the customer card interaction."
        },
        {
          "name": "Terminal transaction",
          "description": "Reference used for status, reconciliation, and safe support evidence."
        },
        {
          "name": "Approved",
          "description": "Confirmed success added once to the payment allocation."
        },
        {
          "name": "Approved but receipt not closed",
          "description": "Retry receipt closure through Pay; never send another card request."
        },
        {
          "name": "Declined / Failed",
          "description": "Confirmed unsuccessful result with response evidence; no successful payment allocation."
        },
        {
          "name": "Expired / timeout",
          "description": "POS wait ended after a final lookup, but processor reconciliation may still be required."
        },
        {
          "name": "Complete manually",
          "description": "Delayed recovery for a payment visibly approved on the terminal while POS confirmation is still missing."
        },
        {
          "name": "Pending processor confirmation",
          "description": "Manually recorded paid state whose detailed processor result should arrive later and must be reconciled."
        },
        {
          "name": "Split tender",
          "description": "Terminal allocation can cover part of Remaining, after which another method completes the sale."
        },
        {
          "name": "Final receipt verification",
          "description": "Confirms one payment, correct amount, references, card metadata, other tenders, and zero/expected balance."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest has no safe exact terminal checkout capture, so this article has no substituted image."
        }
      ],
      "expectedResult": "The terminal and CentriPOS agree on Approved, Declined, or Canceled. Only an approved transaction is attached to the completed sale.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "park-resume-sale",
      "url": "https://platform.getcentri.com/centripos/park-resume-sale",
      "title": "Save, find, and continue an unfinished sale",
      "summary": "Intentionally save an active cart as a resumable sale, find it from the current register or Receipts, safely resolve cart/register locks, and continue editing the same receipt instead of creating duplicate work.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Sell",
      "introduction": "The current cart action is Save Sale, not a naming dialog. It requires at least one cart item and uses the existing cart note, customer, attribution, payments, prices, tax, fulfillment, and receipt identity. A saved sale is potential business, not a completed receipt or Customer Accounts debt.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Build and verify the cart, then attach the customer and enter a useful sale note when known. The current Save Sale action does not prompt for a separate saved-sale name, so the receipt number, customer, note, time, items, status, and total are the recognition details staff will see later.",
        "Choose Save Sale only when the register is open and the cart contains at least one item. CentriPOS writes or updates the same sale as parked, records the parked time, totals, customer/context, fulfillment, any recorded payments/balance, line details, and a saved-sale mirror, then treats the outcome as saved rather than completed.",
        "Confirm the active cart clears and the sale appears once in Saved Sales or Sales → Receipts / Continue sale. Do not resave repeatedly to manufacture duplicates; reopening and resaving should continue the same sale/receipt identity.",
        "From Sell, choose Saved. The sheet excludes the sale already active in the cart and shows resumable sales available to the current register, including receipt number or No receipt #, customer when attached, Saved/Incomplete/In Progress badge, total, note, relative and exact time, total positive item quantity, and up to three item previews.",
        "Choose Continue Sale on the exact record. An open register session is required. If the sale is already live on another register, the Sell workflow blocks it and instructs staff to have that user complete, save, or move it; use Receipts when an authorized intentional takeover is required.",
        "If another cart or draft is already active, resolve Current sale in progress carefully: Cancel keeps the current cart; Clear & Continue discards the current unsaved draft before opening the selected sale; Save & Continue first saves the current cart, then opens the selected sale. Clear & Continue cannot be undone for a new draft.",
        "When the saved sale loads, CentriPOS clears the prior cart, restores the same sale/receipt number, customer, note, prior paid amount, customer source/detail, buying reason, quote/card flag, receipt-level fulfillment/date/time/address/phone, and its line quantities, variants, prices, discounts, notes, source locations, and line-level fulfillment. It also marks the saved-sale helper record retrieved and claims the active editing state.",
        "Compare the restored cart with the Saved Sales preview and original intent. Confirm the customer, receipt number, every line, prior paid amount, remaining balance, fulfillment, tax, promotions, attribution, and notes before editing. Applied promotions are recalculated rather than blindly restored as selected UI state, so verify discounts again.",
        "Continue editing and then choose Pay, Save Sale again, layaway, or Charge to Account as appropriate. Saving again returns the same receipt to the parked workflow; completing payment advances it through the actual completion workflow.",
        "For broader search, use Sales → Receipts and the Continue sale view. If the selected register is closed, the screen offers Open register to continue with opening float and optional note. If a sale is actively locked elsewhere, an authorized Take Over Sale moves the editing lock to this register and the other cart receives a Sale Taken Over lockout.",
        "Close an unwanted saved sale from its receipt detail using the explicit saved-sale abandonment/void workflow and configured reason. Do not call Clear on an active restored cart expecting that to classify the opportunity as abandoned."
      ],
      "controls": [
        {
          "name": "Save Sale",
          "description": "Persists the nonempty cart as a parked/resumable sale; it does not complete payment."
        },
        {
          "name": "Saved",
          "description": "Opens the current-register Saved Sales sheet; a count appears when resumable records exist."
        },
        {
          "name": "Saved / Incomplete / In Progress",
          "description": "Lifecycle badges derived from the saved sale’s current state."
        },
        {
          "name": "Continue Sale",
          "description": "Claims the saved sale and restores it to Sell under the same receipt identity."
        },
        {
          "name": "Cancel",
          "description": "Leaves the current cart in place when a continue conflict appears."
        },
        {
          "name": "Clear & Continue",
          "description": "Discards the current new draft/cart, then loads the selected saved sale; use only when loss is intended."
        },
        {
          "name": "Save & Continue",
          "description": "Saves the current nonempty cart first, then loads the selected sale."
        },
        {
          "name": "Active editing lock",
          "description": "Prevents two registers from silently editing the same sale at once."
        },
        {
          "name": "Take Over Sale",
          "description": "Authorized Receipts action that intentionally moves the editing lock to the current register."
        },
        {
          "name": "Sale Taken Over",
          "description": "Lockout shown to the prior register after another register takes control."
        },
        {
          "name": "Open register to continue",
          "description": "Receipts workflow for starting the selected register session with opening float and optional note."
        },
        {
          "name": "Prior paid amount",
          "description": "Payment already stored on the saved sale and carried into remaining-balance calculations."
        },
        {
          "name": "Saved sale mirror",
          "description": "Register-oriented helper record kept in sync with the underlying sale and its saved items."
        },
        {
          "name": "Same receipt identity",
          "description": "Continuing and resaving updates the original sale rather than intentionally creating a second receipt."
        },
        {
          "name": "Abandonment / void reason",
          "description": "Explicit receipt-detail classification for a lost opportunity versus genuine mistake/cancel cleanup."
        },
        {
          "name": "Not Customer Accounts",
          "description": "Saved value is resumable potential, not an open A/R balance."
        },
        {
          "name": "No separate saved-sale name",
          "description": "The current Save Sale control does not request a name; use the customer and sale note for recognition."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest rejected /register/sell as rejected-loading and contains no privacy-safe saved sale with customer data, so this guide uses no fabricated image."
        }
      ],
      "expectedResult": "The unfinished cart appears once in the saved-sales view with its customer, owner, reason or note, value, and status, and Resume restores the same cart.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "completed-receipt",
      "url": "https://platform.getcentri.com/centripos/completed-receipt",
      "title": "Use the completed sale receipt screen",
      "summary": "Verify the posted result, print the assigned standard receipt, send a customer-safe receipt or link, request a review when eligible, log the interaction when configured, and deliberately start the next cart.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "After the sale",
      "introduction": "This dialog is the handoff after a completed sale, return, exchange, layaway, account transaction, or saved sale. It cannot be dismissed with Escape or an outside click. Do not choose New Sale until the receipt number, status, total, paid amount, and required customer delivery have been checked. The current screen has View Link—not a direct Download button. Customers can download a PDF from the public receipt view.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Read the dialog title first. It can show Sale Complete, Return Complete, Exchange Complete, Layaway Saved, Account Balance Open, Account Paid, or Sale Saved based on the posted status.",
        "Verify the receipt heading and financial summary. The heading uses the sale number, or the first eight characters of the sale ID when a number is unavailable, plus the normalized status. Compare Receipt total with Paid; they can differ for an account balance or other non-fully-paid state.",
        "Choose Print for the standard receipt. The current direct action uses the original register’s assigned receipt template when available, otherwise the default/fallback storefront template. It includes the selected storefront/register policy source and an expected or captured signature block when configured. If the print window does not open, allow popups for pos.getcentri.com and retry once.",
        "On supported Apple mobile devices, Star PassPRNT appears as a separate print destination. It requires the PassPRNT app and sends the same standard automatic-template receipt path; an installed app or iPad alone does not guarantee the Star action will succeed.",
        "Choose Email for a full customer-ready email. Review To, CC, BCC, Subject, optional Message, receipt variant, Store policies source, and Receipt template. To requires at least one address; lists accept comma, semicolon, or new-line separation. The saved customer email and configured CC/BCC values prefill when available, and an unfinished draft is kept for this sale in the current browser session.",
        "For Email, choose Standard receipt, Gift receipt, or Delivery sheet. A gift receipt hides prices; a delivery sheet produces a fuller fulfillment page. Standard can use the selected named receipt template. Choose Storefront, Register, or None for policies, then Send receipt and wait for the success or error result.",
        "Choose Text to create or reuse the branded public receipt link and open Receipt Link. Review the URL, receipt total, phone number, and editable customer notice. The link and STOP opt-out text are appended automatically. Confirm the customer agreed to transactional texts, keep the notice within its displayed segment limit, and choose Send once.",
        "Receipt Link also offers Copy, a QR code, Open link in new tab, and Email Link. Email Link sends a short message leading to the public receipt view; it is different from the main Email action that renders a selected receipt variant/template. The public view lets the customer review items and download the receipt PDF.",
        "Choose View Link when you need to inspect the customer-facing receipt yourself. CentriPOS generates the branded https://pos.getcentri.com receipt URL when needed and opens it in a new tab. Verify the customer-safe view rather than sharing an internal sale or database URL.",
        "For a completed status only, Request review appears when CentriReviews Pro can resolve the receipt location to an active mapping. Confirm customer permission and the correct text/email destination, then verify Sent or Opened; a review request is separate from delivering the receipt.",
        "Log Interaction appears only when the business’s receipt-prompt settings, location/register scope, status, and callback allow it. Use it to record the customer touchpoint when prompted; do not assume every receipt displays the button as enabled.",
        "Choose Open in Receipts when available to continue in Sales → Receipts with this sale open. Opening the detail must not change the surrounding receipt list’s saved filters, register/session scope, or location scope.",
        "Choose New Sale only after the required print/send/review/log work is complete. The button runs the register’s completion callback and clears the finished-sale handoff for the next cart; wait while it is loading and do not double-click."
      ],
      "controls": [
        {
          "name": "Dialog title",
          "description": "Sale Complete, Return Complete, Exchange Complete, Layaway Saved, Account Balance Open, Account Paid, or Sale Saved according to the recorded status."
        },
        {
          "name": "Receipt heading",
          "description": "Sale number or eight-character fallback ID followed by the normalized status."
        },
        {
          "name": "Receipt total",
          "description": "Recorded total for the sale or related transaction."
        },
        {
          "name": "Paid",
          "description": "Recorded amount paid from sale data or summed payment rows; it can be below total for an open balance."
        },
        {
          "name": "Print",
          "description": "Direct standard-receipt action using the assigned/default automatic template and current policy source."
        },
        {
          "name": "Automatic template order",
          "description": "Original register assignment, storefront default, CentriPOS Default, POS Default, then first available template."
        },
        {
          "name": "Popup requirement",
          "description": "Browser print uses a new print window; blocked popups prevent the action from starting."
        },
        {
          "name": "Star PassPRNT",
          "description": "Apple-mobile-only alternate destination requiring the supported Star PassPRNT app."
        },
        {
          "name": "Email",
          "description": "Full receipt-email composer with recipients, subject, message, variant, policies, and template selection."
        },
        {
          "name": "To / CC / BCC",
          "description": "Recipient lists split on commas, semicolons, or new lines; To requires at least one address."
        },
        {
          "name": "Email draft",
          "description": "Per-sale composer values kept in session storage until a successful send removes the draft."
        },
        {
          "name": "Standard receipt",
          "description": "Normal priced receipt using the selected receipt template."
        },
        {
          "name": "Gift receipt",
          "description": "Customer receipt variant that hides prices."
        },
        {
          "name": "Delivery sheet",
          "description": "Fuller page intended for delivery or fulfillment teams."
        },
        {
          "name": "Store policies",
          "description": "Storefront policy, original register policy, or None."
        },
        {
          "name": "Text",
          "description": "Opens the public Receipt Link sharing dialog with SMS selected."
        },
        {
          "name": "Customer notice",
          "description": "Editable SMS text; the receipt link and Reply STOP opt-out language are added automatically."
        },
        {
          "name": "Transactional-text consent",
          "description": "Required checkbox confirming the customer agreed to receive the CentriPOS text on the business’s behalf."
        },
        {
          "name": "Receipt Link",
          "description": "Public customer-safe pos.getcentri.com view with items and receipt-PDF download."
        },
        {
          "name": "Email Link",
          "description": "Short link-delivery email from Receipt Link; distinct from the full templated Email receipt."
        },
        {
          "name": "Copy / QR / Open",
          "description": "Alternate ways to hand off or inspect the same public receipt URL."
        },
        {
          "name": "View Link",
          "description": "Generates or opens the public receipt URL; it is not a direct file-download control."
        },
        {
          "name": "Request review",
          "description": "Completed-sale-only CentriReviews Pro action using the receipt’s exact location mapping and customer consent."
        },
        {
          "name": "Log Interaction",
          "description": "Conditionally enabled post-sale communication prompt based on configured status and location/register rules."
        },
        {
          "name": "Open in Receipts",
          "description": "Moves to the sale detail in receipt history without authorizing receipt-list scope changes."
        },
        {
          "name": "New Sale",
          "description": "Required completion action that exits the locked handoff and prepares the register for the next cart."
        },
        {
          "name": "Error panel",
          "description": "Shows sale-loading, template-loading, or missing-template problems; resolve the underlying sale/register/template context before retrying."
        }
      ],
      "expectedResult": "The heading, status, total, and paid amount match the posted transaction; the chosen standard print, full receipt email, or public receipt-link action reaches the intended customer-safe destination; any review or interaction prompt is handled separately; and New Sale clears the handoff only once for the next cart.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "return-exchange",
      "url": "https://platform.getcentri.com/centripos/return-exchange",
      "title": "Process a return or exchange",
      "summary": "Open the original eligible receipt, select only remaining returnable quantities and serials, choose the correct credit/pricing/inventory treatment, then complete the negative Sell workflow as a refund or exchange.",
      "collection": {
        "id": "register",
        "title": "Register & checkout"
      },
      "section": "Returns",
      "introduction": "Process Return does not issue money immediately. It validates the original receipt and current register, then opens Sell with negative return lines. Add replacement products there for an exchange or choose Pay to allocate the negative balance to an authorized refund method. Company policy and pos.refund permission still apply. Never start from a prior return receipt when the remaining items belong to the original sale.",
      "beforeYouBegin": "Confirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.",
      "steps": [
        "Go to Sales → Receipts, find the original completed sale, and open its detail panel without changing the list scope. Verify customer, sale number/date, location/register, items, payments, fulfillment, prior returns, and current eligibility before choosing Process Return.",
        "If the receipt says it cannot be returned again, open the original sale receipt. Return/child receipts, certain source/system states, voided records, and other ineligible lifecycle states cannot be used as a new return source.",
        "CentriPOS requires a selected register and an open register session. If none is selected, choose Select Location & Register. If the register is closed, enter the authorized opening float/note or change context. When multiple registers exist, Switch Register is available.",
        "Read the source-versus-current context warning. A return can be recorded on the current register even when the original sale came from a different location/register. Confirm that policy and reporting scope before proceeding.",
        "Select each item or fulfillment-fee line to credit. Qty returnable equals original quantity minus quantities linked to non-voided return sales. Refund-only credits consume dollar capacity separately without consuming inventory quantity. Fully returned lines show Already returned and cannot be selected.",
        "Set the return quantity with minus/plus, never above the remaining returnable quantity. For serialized products, select exactly one sold serial row for each unit being returned; CentriPOS blocks continuation until selected serial count matches quantity.",
        "Expand return-credit details when pricing needs review. Original mode uses the original net line amount and original unit tax. Sale-date retail can restore the sale-date retail basis and original discount treatment. Current mode uses current product/variant retail and recalculates supported tax using the original rate. Review the displayed line credit and tax refund before proceeding.",
        "For a partial dollar credit, enter a Partial refund amount greater than $0 and within the remaining refundable subtotal cap. Clear the field for the full selected line credit. This can create a proportional unit-price/discount override; it is not the same as changing quantity.",
        "Choose No inventory return only when the customer keeps the product and the business is intentionally issuing a refund-only credit. That negative line is recorded without restocking or consuming returnable quantity, but its credited dollars reduce the remaining refundable amount.",
        "For a delivery or shipping fee, the return line preserves the fulfillment-fee descriptor, connected item/method context, and a generated note. When an open fulfillment exists, choose whether to cancel the original fulfillment. Leave it active only when delivery/shipping will still be completed at no charge.",
        "Review the summary totals for selected credit and Tax refund. In fulfillment-adjustment mode, the dialog preselects remaining fulfillment-fee lines and explains that replacement fulfillment is chosen later in Sell.",
        "Confirm the Sell workspace is not locked by another tab/window on this device. Choose Start Return / Continue. CentriPOS navigates to Sell with negative line items, linked original line IDs, selected serials, refund-only flags, price/tax overrides, fulfillment notes, and the source receipt context.",
        "For a refund, do not add replacement merchandise. Review the negative cart and choose Pay; select an authorized refund path such as eligible Original Card on File, Payanywhere refund to a new card, cash, store/account treatment, or other configured method consistent with original payment and company policy.",
        "For an exchange, add replacement products to the same Sell cart. The negative return credit offsets the positive replacement lines. Collect a positive remaining balance from the customer or issue a refund for a negative balance. A zero balance still must close into a new receipt.",
        "Wait for the new return/exchange receipt to close. Verify its link to the original sale, negative returned lines, replacement lines, quantities/serials, inventory movement or refund-only behavior, tax/discount/fee credit, fulfillment change, refund/payment references, and final balance. Provide the appropriate receipt.",
        "Reopen the original receipt and new return receipt. Confirm already-returned quantities and credited-dollar caps updated, voided prior returns are excluded correctly, inventory/serial state matches physical custody, the processor result is reconciled, and no second refund or duplicate exchange was created."
      ],
      "controls": [
        {
          "name": "Original sale receipt",
          "description": "Authoritative source receipt containing the remaining returnable lines and payments."
        },
        {
          "name": "Return eligibility",
          "description": "Lifecycle/source relationship check that prevents a return from being started from an ineligible child/return record."
        },
        {
          "name": "Open register required",
          "description": "A selected register with an active session is required to open the negative Sell workflow."
        },
        {
          "name": "Switch Register",
          "description": "Changes the current operating register when multiple active registers exist."
        },
        {
          "name": "Source/current context warning",
          "description": "Shows that the return will post on the current register even if the original sale used another context."
        },
        {
          "name": "Qty returnable",
          "description": "Original quantity minus quantities on linked non-voided return sales."
        },
        {
          "name": "Already returned",
          "description": "Line with no remaining returnable quantity."
        },
        {
          "name": "Refund-only credit consumed",
          "description": "Prior dollar-only credits reduce remaining refundable subtotal without consuming physical quantity."
        },
        {
          "name": "Return quantity",
          "description": "Selected units, capped at remaining returnable quantity."
        },
        {
          "name": "Returned serials",
          "description": "Exact sold serial-number rows required for serialized return units."
        },
        {
          "name": "Original credit",
          "description": "Uses the original net line/tax amounts represented by the sale."
        },
        {
          "name": "Sale-date retail",
          "description": "Uses retail basis captured for the sale date with the original discount treatment."
        },
        {
          "name": "Current price",
          "description": "Uses current catalog retail with supported tax recalculation from the original rate."
        },
        {
          "name": "Partial refund amount",
          "description": "Positive dollar credit within the selected line’s remaining refundable cap."
        },
        {
          "name": "No inventory return",
          "description": "Refund-only credit where the customer keeps the product and inventory/returnable quantity are not restored."
        },
        {
          "name": "Fulfillment fee line",
          "description": "Delivery/shipping charge represented as a normal negative return line with connected context."
        },
        {
          "name": "Cancel original fulfillment",
          "description": "Clears supported pending/open fulfillment when fee return means service will not occur."
        },
        {
          "name": "Tax refund",
          "description": "Calculated negative tax amount for selected return lines and price mode."
        },
        {
          "name": "Selected credit",
          "description": "Total negative merchandise/fee credit prepared for Sell."
        },
        {
          "name": "Sell workspace lock",
          "description": "Prevents opening the same register sale workspace in competing tabs/windows on one device."
        },
        {
          "name": "Negative return lines",
          "description": "New Sell cart lines linked back to original sale-line IDs with return metadata."
        },
        {
          "name": "Refund",
          "description": "Negative cart completed through an authorized refund tender."
        },
        {
          "name": "Exchange",
          "description": "Negative return lines plus positive replacement items completed on one new sale."
        },
        {
          "name": "Original Card on File",
          "description": "Refund-only integrated option when the original sale exposes an eligible card reference."
        },
        {
          "name": "New return receipt",
          "description": "Auditable sale linked to the original through sale_returns and line return references."
        },
        {
          "name": "Post-return verification",
          "description": "Original/return linkage, quantities, dollars, serials, inventory, tax, fulfillment, processor reference, and balance all reconcile."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest contains no privacy-safe exact return-selection dialog, so this guide uses no invented image."
        }
      ],
      "expectedResult": "The original sale shows the returned quantity and refund or exchange activity, inventory follows the configured disposition, and the customer receives the return receipt.",
      "troubleshooting": [
        "Confirm the active location, register, and register-session status before repeating the action.",
        "Do not refresh or retry while a card terminal shows a payment in progress.",
        "If totals differ, review every cart line, discount, fulfillment charge, and tax before payment."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "receipts",
      "url": "https://platform.getcentri.com/centripos/receipts",
      "title": "Find and use Receipts",
      "summary": "Search and scope sales, preserve reusable views, open receipt details in place, trace customer/fulfillment/payment/accounting context, and use only the actions permitted for that receipt.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "Open Sales → Receipts in the retail workspace or Money → Receipts in the service workspace. Both use the same receipt-history and receipt-detail screen; Money retains its own navigation and direct receipt route. Opening a receipt is detail UI state: CentriPOS stores it as openSaleId and keeps the receipt list’s search, date, customer/association, location, register, user, status, report receipt-set, and saved-view scope intact. Do not confuse openSaleId with saleId; saleId filters the list to a receipt set. Receipt surfaces contain private customer and financial data, so the Harbor & Hearth capture was intentionally rejected rather than published.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Open Receipts from Sales or, in a Money workspace, Money → Receipts. Confirm the business, location, register, user, and any active receipt-status filter before interpreting results. Roles can limit records to permitted sales and operating scopes.",
        "Start with All sales, Continue sale, or a pinned/saved receipt view. Continue sale is a workflow view for saved sales that can be resumed; it is not a second copy of completed receipt history. Opening a saved view reapplies its stored filters to current data.",
        "Use the receipt search for supported receipt text, amount, customer, and other indexed sale values. Apply Status, date/time range, user, location, register, customer, household/company association scope, or report-provided receipt set as needed. More filters moves the full filter set into a compact sheet on smaller layouts.",
        "Read active filter chips and the refined-search label before concluding a receipt is missing. Clear only the suspect filter first. Clear all filters returns to the default receipt scope but does not grant broader permissions or reveal records outside role/location/register restrictions.",
        "Use Views to create a Personal or Shared saved filter configuration. Shared view management requires its permission. A user can update a personal view they created; shared edits require shared-view authority. Names must be unique within the applicable scope, and only the configured maximum number of views can be pinned for quick access.",
        "Select a receipt row/card. CentriPOS adds openSaleId to the URL and expands the receipt details where you are without changing the underlying list query. Closing the panel removes only openSaleId. Changing the receipt search intentionally closes the previously open detail because the result set changed.",
        "Read the receipt header, lifecycle/status badges, receipt number/date, location/register, selling user, customer, total, balance, fulfillment, communications, and payment/accounting indicators before using an action. An authorized or pending payment is not settled cash; inspect the payment status and source record. Use related customer, fulfillment, external order, or QuickBooks links only when present.",
        "Review every receipt line including quantity, product/variant, price, discounts, tax, fulfillment method/status/date, returned quantities, connected purchase order, and notes. Then reconcile subtotal, discount, tax, payment/tender rows, refunds/returns, account balance, and total rather than trusting a single headline.",
        "Use fulfillment status/date controls only when the receipt and permissions allow it. A row can link into Fulfillment Center, identify unscheduled open fulfillment, or show completed/other lifecycle state. Updating fulfillment is an operational change, not a receipt-note edit.",
        "Use Continue sale only for an eligible saved sale. CentriPOS checks the original register/location, register session, active editing window, and the single Sell-workspace lock on this device. It may require switching context or opening a closed register with an opening float/note. Do not bypass a lock by duplicating tabs.",
        "Use Process return or the refund control only when the receipt is eligible and the effective user has pos.refund. Review original quantities, prior returns, payment path, and refund destination before confirming. An uncertain processor result must be traced before retrying.",
        "Use Edit sale only with pos.edit_sale and only for fields the edit dialog supports. Use Void only when lifecycle rules and pos.void permit it; saved-sale abandonment/cancel flows can require a disposition, configured reason, notes, and a decision about reactivating fulfillment. These are auditable changes, not ways to hide a mistaken receipt.",
        "Use Email receipt to review To, optional CC/BCC, subject, message, Receipt style, Store policies, and Receipt template. Standard receipt, gift receipt, and delivery-sheet output have different disclosure. Never add an address that should not receive the customer’s receipt.",
        "Use Print to choose Print style, supported Paper size, Store policies, and Receipt template, then inspect the browser/system destination before printing. Use the separate Star PassPRNT option only on the supported iPad/iPhone path. Print one safe test before a batch.",
        "Use Log interaction or open a submitted interaction only when communications tracking applies. Invoice attachments can be viewed/downloaded or managed according to permission; do not upload or expose files unrelated to the customer account invoice.",
        "For QuickBooks, distinguish a linked invoice, Send to QuickBooks for an eligible account receipt, match/relink controls, and More actions. Never repair an accounting link merely because the button exists; verify tenant, customer, receipt/invoice, amount, QBO target, and the complete sync path first.",
        "When more rows exist, use Load more rather than changing filters mid-investigation. After any return, void, edit, fulfillment update, email, print, interaction, attachment, processor, or accounting action, refresh the receipt detail and verify the intended state plus its activity/audit evidence."
      ],
      "controls": [
        {
          "name": "All sales",
          "description": "Default receipt-history view using the active filters and permissions."
        },
        {
          "name": "Continue sale",
          "description": "Saved-sale workflow view for receipts eligible to resume in Sell."
        },
        {
          "name": "Views",
          "description": "Personal and shared saved receipt-filter configurations."
        },
        {
          "name": "Pinned view",
          "description": "Quick-access saved view; pinned count is capped by the sales-view configuration."
        },
        {
          "name": "Modified saved view",
          "description": "Active filters differ from the saved configuration and can be saved as a new view or updated when authorized."
        },
        {
          "name": "Receipt search",
          "description": "Searches supported receipt text, amount, customer, and indexed sale fields."
        },
        {
          "name": "Status",
          "description": "Lifecycle filter such as completed, saved, voided, returned, or account state as supported by the current model."
        },
        {
          "name": "Date / time range",
          "description": "Preset or custom receipt period serialized into the URL."
        },
        {
          "name": "User",
          "description": "Selling-user filter; own-sales-only permission can further restrict results."
        },
        {
          "name": "Location / register",
          "description": "One or more operating scopes, still subject to user and restricted-register permissions."
        },
        {
          "name": "Customer / association scope",
          "description": "Specific customer IDs or household/company association receipt scope."
        },
        {
          "name": "Receipt set / saleId",
          "description": "Report- or URL-provided set that filters which receipts belong in the list."
        },
        {
          "name": "openSaleId",
          "description": "Selected detail-panel state only; it must not rerun the list against a different receipt set."
        },
        {
          "name": "Refined search label",
          "description": "Human-readable description of a report/refined result scope."
        },
        {
          "name": "Clear all filters",
          "description": "Returns to default filters without changing permissions."
        },
        {
          "name": "Receipt row/card",
          "description": "Summary with lifecycle, date, customer, location/register, amount, fulfillment, interaction, attachment, integration, and closeout indicators when available."
        },
        {
          "name": "Detail panel",
          "description": "Expanded receipt inspection kept in place within the current list."
        },
        {
          "name": "Close sale details",
          "description": "Removes openSaleId and collapses the selected detail without clearing the list."
        },
        {
          "name": "Customer profile",
          "description": "Opens the linked customer when the receipt has a customer ID."
        },
        {
          "name": "Fulfillment Center",
          "description": "Opens related fulfillment work for eligible receipt lines."
        },
        {
          "name": "WooCommerce order",
          "description": "External order link when the receipt carries the connection."
        },
        {
          "name": "Items and totals",
          "description": "Line quantity/product/variant/price/discount/tax/fulfillment/return context plus reconciled receipt totals."
        },
        {
          "name": "Payments / balance due",
          "description": "Tender, account, refund, and remaining-balance evidence; verify against processor and A/R records when applicable."
        },
        {
          "name": "Continue sale lock",
          "description": "Prevents simultaneous Sell editing on the same device and enforces session/context checks."
        },
        {
          "name": "Process return / refund",
          "description": "Permission- and lifecycle-gated return/refund workflow."
        },
        {
          "name": "Edit sale",
          "description": "pos.edit_sale-gated dialog for supported receipt changes."
        },
        {
          "name": "Void / saved-sale disposition",
          "description": "Permission- and lifecycle-gated cancellation or abandonment decision with reason/note and possible fulfillment handling."
        },
        {
          "name": "Email receipt",
          "description": "Recipient, subject/message, style, policies, and template workflow."
        },
        {
          "name": "Print",
          "description": "Receipt/gift/delivery style, paper, policies, template, and browser/system destination."
        },
        {
          "name": "Log interaction",
          "description": "Creates or opens communication evidence connected to the receipt."
        },
        {
          "name": "Invoice attachments",
          "description": "Customer account-invoice files with controlled download/actions."
        },
        {
          "name": "QuickBooks controls",
          "description": "Linked invoice, send, match/relink, or more actions shown only for supported accounting state."
        },
        {
          "name": "Load more",
          "description": "Fetches the next receipt page without changing active filters."
        },
        {
          "name": "Activity / audit evidence",
          "description": "Post-action verification for receipt lifecycle, communication, fulfillment, payment, and accounting changes."
        },
        {
          "name": "No public screenshot",
          "description": "The Harbor & Hearth receipts capture exposed customer, receipt, phone, amount, date, location, and status data and was rejected; this guide intentionally has no invented replacement."
        }
      ],
      "expectedResult": "The selected receipt opens in place without changing the receipt list’s date, location, register, status, search, or saved-view scope.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "receipt-filters-saved-views",
      "url": "https://platform.getcentri.com/centripos/receipt-filters-saved-views",
      "title": "Filter receipts and save a view",
      "summary": "Build personal or company receipt shortcuts from the exact supported filter set, pin up to three per profile, and update or copy them without changing the underlying sales records.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "Saved receipt views store filters only. They do not store table columns, manual sorting, receipt snapshots, or an opened receipt. They live in the Views menu on Sales → Receipts—not in Intelligence—and always query current sales data when reopened.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Open Receipts from Sales or, in a Money workspace, Money → Receipts. Both use the receipt-history view. Use All sales to reset the filters or Continue sale for eligible unfinished account, layaway, or saved work.",
        "Set at least one meaningful filter. Supported saved fields are Status; Date From/To; Time range; one customer or a household/company/association customer group; receipt/note search; location IDs or register IDs; focused sale IDs and refined-search label; and User.",
        "For Status, choose All Sales or a state under Open sales, Completed sales, or Adjusted & closed. Place uses either selected locations or selected registers: choosing locations clears register IDs, and choosing registers clears location IDs.",
        "Use More filters for Customer, Place, User, and Time. Users restricted to their own sales see My sales instead of a freely editable User filter. Clear all resets to status All Sales and removes the other filters.",
        "Choose Save view. Name it, choose Just me or Shared with company, and decide whether to Pin this view. Only owners and super admins can create or manage shared views; other users can save personal copies and personally pin shared views.",
        "Use a unique name in the chosen scope. Personal-name conflicts are checked among views created by your profile; shared-name conflicts are company-wide. Up to three views can be pinned to the shortcut row for each profile.",
        "Reopen a view from the Views menu or its pinned chip. The app applies its stored filters, writes them to the receipt URL, and marks the active mode as saved:<view ID>. The result is current data, not the rows that existed when the view was saved.",
        "Change a filter while a saved view is active. Modified appears because the current normalized filters differ from the stored filters. If you own the personal view—or are an owner/super admin for a shared view—choose Review changes to update it, or Save as new to preserve the original.",
        "When saving as new from a shared view without shared-view permission, CentriPOS defaults the copy to personal. Updating cannot change a view’s Personal/Shared scope; use Save as new when the audience must change.",
        "Use the pin control in Views to pin or unpin personally. Deleting a permitted view marks it inactive and removes every pin for that view; the current interface performs this without a confirmation dialog.",
        "Open a receipt from the filtered list. The selected receipt is represented by openSaleId and should remain detail UI state; it must not replace the list’s saved filters or turn into a saleId list filter. Changing receipt search intentionally drops an openSaleId that could now point outside the new search."
      ],
      "controls": [
        {
          "name": "All sales",
          "description": "Built-in view that resets to the default filter set: status All Sales."
        },
        {
          "name": "Continue sale",
          "description": "Built-in work view for receipts that can still be continued; it is not a saved custom view."
        },
        {
          "name": "Stored filters",
          "description": "Status, dates, time range, customer/customer group, receipt or note search, location IDs, register IDs, sale IDs/refined-search label, and user."
        },
        {
          "name": "Not stored",
          "description": "Table columns, table sorting, expanded/open receipt state, and a snapshot of matching rows."
        },
        {
          "name": "Personal view",
          "description": "Visible for the user’s profile; only its creator can update or delete it."
        },
        {
          "name": "Shared view",
          "description": "Visible company-wide; only owners and super admins can create, update, or delete it. Other users can pin or copy it."
        },
        {
          "name": "Pinned view",
          "description": "Personal shortcut above the filters. Each profile can pin up to three saved views."
        },
        {
          "name": "Modified",
          "description": "Current filters no longer exactly match the active view’s serialized stored filters."
        },
        {
          "name": "Update saved view",
          "description": "Overwrites the active editable view’s name and filter payload while preserving its scope."
        },
        {
          "name": "Save as new",
          "description": "Creates a separate view, useful for a personal copy or a different audience."
        },
        {
          "name": "Unique name",
          "description": "Case-insensitive, whitespace-normalized uniqueness within the applicable personal or shared scope."
        },
        {
          "name": "Delete view",
          "description": "Soft-deactivates the view and removes all pins; no confirmation dialog is shown in the current UI."
        },
        {
          "name": "Filter URL",
          "description": "The active filter values are serialized into receipt-page query parameters for stable navigation."
        },
        {
          "name": "openSaleId",
          "description": "The expanded receipt detail state. It does not narrow the saved receipt list like saleId or receiptSet filters do."
        },
        {
          "name": "Current data",
          "description": "Reopening reruns the receipt query against live records using the stored filters."
        }
      ],
      "expectedResult": "The named view reopens with its saved receipt filters against current permitted data. Opening or closing a receipt keeps that list scope intact; the view does not preserve columns, manual sorting, receipt snapshots, or the previously opened receipt.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "order-intake",
      "url": "https://platform.getcentri.com/centripos/order-intake",
      "title": "Review requests in Order Intake",
      "summary": "Inspect price-book form submissions, record their review state, copy a human-readable intake summary, and deliberately rebuild an approved request in Sell.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "Order Intake currently reads submissions created by CentriPOS public price-book order forms. The page description mentions ecommerce and future channels, but this queue is backed by price_book_order_submissions; do not assume every online-store or WooCommerce order appears here. Most importantly, Review sale does not yet copy the customer or requested items into the Sell cart and does not convert the request to a sale. It marks the request Reviewing and opens Sell, where staff must verify and enter the transaction through the normal workflow.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Go to Sales → Order Intake. The navigation item and page heading use the Clipboard List icon. Work in the intended business; the query is tenant-scoped and newest submissions appear first.",
        "Read the four summary cards across the full tenant queue. Open requests excludes Converted to sale, Fulfilled, and Cancelled. Needs approval counts only that status. Converted / fulfilled combines those two states. Submitted value adds every stored submission subtotal, including hidden-price, cancelled, and other statuses; it is not a filtered sales, payment, or revenue total.",
        "Use Search customer, source, item… to search the customer snapshot label, price-book name, source-template name, captured field labels/values, SKU, product, or variant. Search does not include the submission ID or status label.",
        "Use the status filter. Open requests is the default; All statuses includes terminal states; the exact choices are Submitted, Reviewing, Needs approval, Approved, Converted to sale, Fulfilled, and Cancelled. “No intake requests match this view” means the current tenant, filter, and search produced no rows.",
        "For each request, confirm the customer/company label, Submitted time and timezone, line count, total units, price-book badge, Source form badge, submitter email, requested copy recipients, and pricing state. Pricing hidden means staff should not treat the stored subtotal as a customer-approved displayed quote.",
        "Review Requested items. The card shows at most the first eight lines, with quantity, SKU/product/variant, and line total when the source template includes prices; a +N more message means the copied summary or source record must be checked for the remaining lines.",
        "Review Fields & approvals. Submitter email and copy recipients are shown separately; other captured custom fields and typed signature/approval values are listed here, up to eight displayed entries. “No additional fields captured” does not mean the customer approved terms that were never collected.",
        "Choose Copy intake to place a plain-text summary on the clipboard. It includes source price list/form, customer label, submitted time, current status, item quantities and identities, optional prices/subtotal, other order fields, and typed approvals. Review the text and recipient before pasting it because it can contain customer and order data.",
        "Choose Source price list to open the exact Customer Pricing record behind the request. Use it to verify the source catalog and form; do not change the source merely to make an old submitted snapshot look current.",
        "When clarification or authorization is still needed, choose Needs approval or select that status. This changes only the intake status and shows a confirmation toast; the button does not send an email, text, approval link, or notification despite its Mail icon. Contact the customer through an approved communication workflow and document the response separately.",
        "Use the status selector deliberately. A status change writes immediately—there is no separate Save or confirmation dialog—and refreshes the intake and price-book queries. Submitted, Reviewing, Needs approval, Approved, Converted to sale, Fulfilled, and Cancelled are tracking labels; changing one does not itself create, pay, fulfill, cancel, or edit a sale.",
        "Choose Review sale only when ready to work the request. Current behavior first updates its status to Reviewing and then opens /register/sell with the submission, price book, and customer IDs in navigation state. The current Sell implementation does not consume that state to load a cart or customer automatically.",
        "In Sell, confirm the active location, register, session, customer, current source price, tax, fulfillment, notes, approvals, inventory, and payment terms. Manually add and verify the approved items and quantities through the normal sale workflow. Do not promise the customer the submitted estimate until staff has validated it.",
        "Complete or save the transaction only through the applicable Sell workflow. Then return to Order Intake and set Converted to sale only after a matching sale actually exists, or Fulfilled only after the downstream fulfillment is truly complete. The intake record currently has no visible linked-sale ID, receipt link, conversion audit, or automatic status reconciliation.",
        "Use Cancelled only for a request the business has actually declined or withdrawn under its policy. Because status changes are immediate and the screen has no history/undo panel, verify the request before changing a terminal label and use operational records for any required reason or customer communication."
      ],
      "controls": [
        {
          "name": "Clipboard List icon",
          "description": "Exact CentriPOS navigation/page icon for Order Intake."
        },
        {
          "name": "Open requests",
          "description": "Count/filter excluding Converted to sale, Fulfilled, and Cancelled; Approved remains open."
        },
        {
          "name": "Needs approval",
          "description": "Count and status for requests awaiting clarification or authorization. It does not send a message."
        },
        {
          "name": "Converted / fulfilled",
          "description": "Combined count of requests whose manually tracked status is Converted to sale or Fulfilled."
        },
        {
          "name": "Submitted value",
          "description": "Sum of stored subtotals for the entire loaded tenant queue, not the visible filter and not booked revenue or collected payment."
        },
        {
          "name": "Search customer, source, item…",
          "description": "Matches customer label, price book, source form, captured fields, SKU, product, and variant."
        },
        {
          "name": "Status filter",
          "description": "Open requests, All statuses, or one exact tracking status."
        },
        {
          "name": "Customer / company label",
          "description": "Uses captured company, then name, email, phone, or Online customer fallback."
        },
        {
          "name": "Price list badge",
          "description": "Price book associated with the public submission."
        },
        {
          "name": "Source badge",
          "description": "Public form template that produced the request."
        },
        {
          "name": "Pricing hidden",
          "description": "The source template did not display prices; item prices and subtotal are suppressed in the queue summary."
        },
        {
          "name": "Requested items",
          "description": "First eight captured lines with quantity and identity, plus price when the source included it."
        },
        {
          "name": "Fields & approvals",
          "description": "Up to eight non-contact custom fields and typed approval/signature values captured by the form."
        },
        {
          "name": "Copy intake",
          "description": "Copies customer/order content to the clipboard; verify privacy and destination before sharing."
        },
        {
          "name": "Source price list",
          "description": "Opens the originating Customer Pricing record."
        },
        {
          "name": "Needs approval button",
          "description": "Immediately changes the tracking status to Needs approval; despite its Mail icon, it sends no customer communication."
        },
        {
          "name": "Status selector",
          "description": "Immediately saves one of seven tracking states without a separate Save button."
        },
        {
          "name": "Review sale",
          "description": "Marks Reviewing and navigates to Sell with context only. It does not hydrate the cart/customer or create a sale."
        },
        {
          "name": "Converted to sale",
          "description": "Manual tracking label to use only after a matching sale was actually created."
        },
        {
          "name": "Fulfilled",
          "description": "Manual tracking label to use only after the downstream work was actually fulfilled."
        },
        {
          "name": "Cancelled",
          "description": "Manual intake label; it does not void or cancel a separate sale."
        },
        {
          "name": "No automatic linkage",
          "description": "The current intake UI shows no sale/receipt ID, automatic conversion, fulfillment reconciliation, status history, or undo."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /sales/order-intake in a fully rendered zero-request state. It accurately shows the Clipboard List icon, summary cards, search, filter, and empty queue without exposing customer data."
        }
      ],
      "expectedResult": "The incoming order is matched or flagged accurately and continues into the correct CentriPOS payment and fulfillment workflow without being duplicated.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/sales-order-intake.png",
        "alt": "Harbor & Hearth Order Intake screen showing request status totals, search, status filtering, and the fully rendered empty intake queue in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-accounts",
      "url": "https://platform.getcentri.com/centripos/customer-accounts",
      "title": "Use Invoicing and Customer Accounts",
      "summary": "Review customer balances and invoice lifecycle, prepare location statements, send reviewed documents, and collect or record payments through the enabled workflow.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "Use Sales → Invoicing in the retail workspace or Money → Invoices in the service workspace. Money opens the same accounts-receivable suite in a simplified layout, initially on Open invoices; it retains the specific invoice/customer context in its detail route. Sales → Customer Accounts is CentriPOS’s accounts-receivable workspace. Its operating model can be CentriPOS-led, QuickBooks Online-led, or mirrored according to the tenant’s A/R workflow. A customer attachment, displayed permission, status, and accounting mode determine which creation, posting, reminder, payment, portal, and QuickBooks actions are actually available.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Open the invoicing workspace for your operating mode and confirm the business, location/date filters and selected customer. Money → Invoices starts on Open invoices in a simplified layout; use only the tabs and actions actually offered. An old Sales → Invoicing link in a service business opens this Money workspace.",
        "To charge a sale to an account, start at Register → Sell and attach the exact customer. Choose Pay, then Charge to Account. The action remains unavailable without an attached customer because the resulting receivable must belong to a saved customer account.",
        "Complete Invoice details using only fields required by the retailer. Review purchase order/reference, terms or due date, billing contact, notes, and supported invoice attachments. Attachments can include the displayed image, PDF, CSV, Microsoft Office, or OpenDocument types, up to 10 MB each and the on-screen file-count limit; never attach payment credentials or unrelated customer records.",
        "Review the customer, receipt lines, totals, prior payments, balance, and invoice information, then confirm once. A Customer Accounts transaction creates a real receivable. Save Sale/parked carts remain resumable sales potential and must not be counted as debt until completed through the account workflow.",
        "Open Invoicing from Sales or Money → Invoices in a Money workspace. Confirm business, customer, role and the current accounting/collection settings. Follow the actions actually enabled for the account; a configured workflow or permission can restrict collection or invoice editing.",
        "Use Overview for the current aggregate position: open account sales, completed account sales, invoice balance, active customer balances, and access to Create invoice, Review open accounts, Review completed accounts, Review balances, Craft statements, or Configure account fields. Confirm the displayed totals’ definitions before reconciling them.",
        "Use the invoice list and its visible document/status filters to find the intended obligation. Open invoices, paid invoices, drafts, proposals and on-account work have different meanings. A saved or on-account document that has not been issued must not be treated as an emailed, payable invoice.",
        "Use paid history and source receipt links to trace completed work. Verify paid amount and current balance rather than relying on a tab name. Avoid counting a receipt and its linked A/R invoice as two obligations.",
        "Use Balances for active ledgers. Owed includes balances over one cent; Store credit includes positive store-credit balances; All active includes either. Search matches customer/company name, email, phone, customer code, or source code. Totals above the table separately sum money owed and store credit.",
        "In a balance row, read customer/contact identity, email, phone, count of current open sales plus unpaid/partial invoices, stored balance, store credit, and credit limit. Choose Account for the itemized A/R view, Profile for customer account settings, Sales for customer-scoped receipts, or Portal to send customer access.",
        "Inside the A/R account view, confirm the account identity and contact. First recorded activity is the earliest sale or invoice in the full ledger. Open balance is the stored customer balance; Traced from visible open items sums unmirrored open sales plus open invoice rows. Paid completed balance combines completed account sales and paid invoices, while Store credit remains separate.",
        "Compare Open items making up the balance with the stored Open balance. Invoice-linked sales are removed from the unmirrored-sale portion to avoid counting the same obligation twice. Open invoices exclude Paid and Void and require a positive balance. If traced items and stored balance differ, use the itemized rows as evidence and investigate instead of silently overwriting either figure.",
        "For an unmirrored open receipt, choose its receipt number to inspect the source sale or Invoice to create/open its A/R mirror. For an invoice row, review invoice number, status, issue/due dates, total, and balance. Use Open invoice for details. Opening a receipt detail must not change the surrounding receipt list’s saved scope.",
        "Use Profile to inspect or manage the customer’s Account tab and Store credit separately. A credit limit can constrain supported account charging, while store credit is value owed to the customer; neither should be added to outstanding receivables. Receipts opens a customer-filtered receipt list and preserves the customer scope.",
        "Choose Email portal only after confirming the saved customer email. CentriPOS asks the customer-portal service to create/send tenant-scoped access and confirms Customer portal sent to the exact address. The portal is described in its own guide; a send success proves dispatch, not opening, identity verification, or payment.",
        "Choose Statement or Craft statement for the selected customer. Review the saved To, CC, BCC and phone details, choose Open Item, Balance Forward, or Transaction Statement, and select valid statement dates. Nothing is sent while you prepare a statement.",
        "Choose Prepare statement. Review every separate location statement, its location balance and any displayed whole-account balance. Use View statement, Download PDF, or Copy link to inspect the same type/date/detail settings. The new Customer statements guide explains the as-of and current-payment distinction.",
        "To deliver a prepared statement, choose Send statement and review its enabled Email/Text route and location sender. For email, inspect recipients, Reply-To, message and selected attachments, then Review email before Send statement. Check the original sending status after any uncertain response instead of creating a duplicate send.",
        "Use Invoices to search the current document list. The filter includes All documents, Drafts · unfinished orders, proposal states (all, awaiting acceptance, not opened, viewed, accepted), All open, Unpaid, Partial, Paid and Void. Drafts and proposals are separate from issued receivables; a proposal-view or acceptance status is not proof of payment. New Invoice or proposal creation can be locked by the current accounting workflow.",
        "Open the exact invoice and inspect its customer, connected order/receipt, total, balance, terms source/start, due date, issuance, sending, collection and accounting state. Save on account accepts an order for fulfillment without issuing it. Confirmed sending or an authorized Mark as sent establishes issuance. Edit invoice and billing-date/terms controls appear only for the permitted role, enabled business settings, eligible balance/status and any connected-accounting conditions; do not assume every invoice is editable.",
        "Use the invoice’s Send action to review the enabled Email or Text route, exact recipient, message and selected documents. Review email is preparation only; use the explicit Send invoice action after review. Text requires the displayed customer-consent confirmation. If sending is uncertain, use Check sending status for the original request rather than sending another notice.",
        "Use the available QuickBooks action to inspect the connected accounting copy. CentriPOS remains the operational source for the invoice; compare document identity, customer, amount, terms/due date, payments and sync state. A linked badge, opened QuickBooks page or successful local save does not prove a current accounting sync or bank settlement.",
        "Record Payment only when the current workflow and invoice allow collection. Choose Already received only for money actually received. Enter a positive amount no greater than the balance, an enabled location/POS payment type, the required method reference, the actual nonfuture receipt date and a safe note, then confirm the money has already been received. This records the incoming money; it does not charge a card, withdraw from a bank or apply store credit.",
        "Use Saved card / bank for a new authorized collection. Select the exact supported saved customer method and review the server-approved invoice amount and eligibility. A supported bank account requires its one-time authorization review. If an earlier received-payment or saved-method attempt is uncertain, preserve it and use Check original payment; do not charge again or record a separate payment.",
        "Review the register-session message before recording an account collection. Today’s payment can belong to the current open session, while a historical collection is recorded outside that session; cash requires today’s open register. After a confirmed result, trace the same payment through invoice and receipt, register/closure evidence, processor or bank settlement and the connected accounting copy. Keep Paid, deposit pending and sync needs attention distinct.",
        "Use invoice and account settings only through their actual supported controls. Example rows or informational setup messages in a legacy workspace do not prove that a field or rule was saved. Verify the persisted setting after reopening, and use Admin → Invoices for the supported invoice configuration.",
        "Use enabled invoice payment actions for actual collection and recording. A payment-tools setup card, disabled preview, or informational toast does not collect money or establish ACH settlement. Follow the current processor/gateway and accounting restrictions for this business.",
        "After any charge, invoice post, statement, reminder, portal send, or payment, reopen the exact account. Verify customer, receipt/invoice identity, status, total, paid, balance, due date, itemized open rows, stored balance, communication activity, accounting link, and portal/statement recipient before considering the workflow complete."
      ],
      "controls": [
        {
          "name": "Customer Accounts",
          "description": "Sales A/R workspace covering open/completed account sales, balances, invoices, statements, and currently scaffolded account/payment tools."
        },
        {
          "name": "A/R workflow banner",
          "description": "Current CentriPOS-led or QBO-led mode plus receipt-link, payment-collection, and manual-invoice permissions."
        },
        {
          "name": "Overview",
          "description": "Aggregate open sales, completed sales, invoice balance, active customer balances, and workflow shortcuts."
        },
        {
          "name": "Account Balance Open",
          "description": "Sales with status on_account that still need collection, statement inclusion, or invoice follow-up."
        },
        {
          "name": "Completed",
          "description": "Sales with status bill_to_account; the tab name does not prove every related invoice is paid."
        },
        {
          "name": "Balances",
          "description": "Active customers with money owed and/or positive store credit."
        },
        {
          "name": "Owed / Store credit / All active",
          "description": "Balance-ledger filters using positive values above one cent."
        },
        {
          "name": "Balance search",
          "description": "Matches customer/company identity, email, phone, customer code, or source code."
        },
        {
          "name": "Open items count",
          "description": "Open account sales plus invoices that are not Paid/Void and have a positive balance."
        },
        {
          "name": "Stored open balance",
          "description": "Balance on the customer ledger row."
        },
        {
          "name": "Traced open items",
          "description": "Unmirrored open sales plus positive open invoices, with invoice-linked sales excluded to avoid duplication."
        },
        {
          "name": "First recorded activity",
          "description": "Earliest dated sale or invoice in the full customer ledger."
        },
        {
          "name": "Paid completed balance",
          "description": "Completed account-sale totals plus Paid invoice totals; not the current amount owed."
        },
        {
          "name": "Store credit",
          "description": "Separate value owed to the customer; never add it to receivables."
        },
        {
          "name": "Credit limit",
          "description": "Configured ceiling for supported account charging; blank is displayed without inventing a limit."
        },
        {
          "name": "Account",
          "description": "Customer-specific A/R summary with open items, invoices, activity, profile, portal, receipts, QBO link, and statement action."
        },
        {
          "name": "Profile",
          "description": "Customer profile panel, including Account and Store credit tabs."
        },
        {
          "name": "Receipts / Sales",
          "description": "Customer-filtered receipt view, optionally opening one sale without replacing the list scope."
        },
        {
          "name": "Email portal / Portal",
          "description": "Sends customer-portal access to the saved email through the tenant-scoped service."
        },
        {
          "name": "Craft statement / Prepare",
          "description": "Selects the customer and opens the statement workspace."
        },
        {
          "name": "Statement range",
          "description": "Last 30, 60, 90 days, or all available activity."
        },
        {
          "name": "Email statement PDF",
          "description": "Live statement generation and email action with balance forward, transaction/payment rows, aging, and amount due."
        },
        {
          "name": "Batch export",
          "description": "Informational placeholder only; no batch file or send currently occurs."
        },
        {
          "name": "Invoices",
          "description": "Searchable/filterable A/R documents with Draft, Quote, Unpaid, Partial, Paid, and Void states."
        },
        {
          "name": "Outstanding total",
          "description": "Invoice balance excluding Paid, Void, Draft, and Quote."
        },
        {
          "name": "New Invoice",
          "description": "Manual document creation; locked when QBO-led workflow disallows CentriPOS invoices."
        },
        {
          "name": "Invoice mirror",
          "description": "A/R invoice created or opened for an on-account sale so the obligation is not double-counted as an unmirrored receipt."
        },
        {
          "name": "Post invoice / Accept quote & post",
          "description": "Turns a Draft or accepted Quote into a posted customer-account obligation."
        },
        {
          "name": "Send reminder",
          "description": "Creates a branded receipt reminder link for a posted open invoice linked to a sale."
        },
        {
          "name": "Record Payment",
          "description": "Live invoice collection/recording action when allowed by workflow, status, payment type, location, amount, and reference policy."
        },
        {
          "name": "Saved payment method",
          "description": "Authorized CentriPay vault card collection followed by an invoice payment record."
        },
        {
          "name": "QBO linked / View on QuickBooks Online",
          "description": "Evidence of an external accounting association and destination; verify sync status separately."
        },
        {
          "name": "Invoice attachments",
          "description": "Authorized documents stored with the invoice and opened through a short-lived branded proxy path."
        },
        {
          "name": "Account fields",
          "description": "In-memory UI scaffold; current Add field does not persist schema or customer values."
        },
        {
          "name": "Payment tools",
          "description": "Informational scaffolds for card links, ACH, and application rules; their buttons do not configure or execute those workflows."
        },
        {
          "name": "True open vs stored balance",
          "description": "Reconciliation boundary requiring investigation when the itemized open obligation and stored customer balance differ."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest has no safe Customer Accounts or invoice capture, so this guide intentionally uses no substituted image."
        }
      ],
      "expectedResult": "The selected customer or invoice shows the correct open balance, due dates, payments, credits, files, and chronological account activity.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sales-intelligence-saved",
      "url": "https://platform.getcentri.com/centripos/sales-intelligence-saved",
      "title": "Use Intelligence + Saved Sales",
      "summary": "Analyze submitted interactions, customer loss reasons, currently saved and abandoned sales, conversion/recovery, associate performance, and follow-up opportunities without changing receipt history.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "This is an analytics and follow-up center, not the Sell saved-cart picker. It does not contain a Resume, close, abandon, owner-change, or status-update action. Filters are in-memory against the loaded tenant data: sales dates use sale created_at, interactions use occurred_at, locations/registers/users use different source fields described below, and the Interaction Log renders only the first 80 matching rows even though its badge can be larger.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Go to Sales → Intelligence + Saved Sales and confirm the intended business. Wait for the sales data to finish loading. The page opens on Intelligence and also contains Saved Sales and Interaction Log tabs.",
        "Set Date range if needed. Quick choices include Today, Yesterday, This/Last week, This/Last month, This/Last quarter, This year, Last 30 days, and Last 90 days. Custom From/To dates are interpreted as full local calendar days. Sale filtering uses created_at, while interaction filtering uses occurred_at; a saved sale completed later can still fall under its original created date.",
        "Choose one or more Locations. Sales match either current location_id or origin_location_id. Interactions match their location_id. Changing locations clears any selected registers because the available register choices are rebuilt for the chosen locations.",
        "Choose one or more Registers. Sales match origin_register_id; interactions match metadata.register_id. A record missing those origin/metadata fields is excluded when a register filter is active.",
        "Choose one or more Users. Sales match cashier_id or origin_associate_id. Interactions match owner_id. This means a single user filter is not necessarily the same business role across the sales and interaction datasets.",
        "Use Interaction outcome only for interaction rows and interaction KPIs: Purchased, No purchase, Saved quote, Follow up, Lost, or Converted. The implementation compares the stored outcome, falling back to status, so labels that look related can remain distinct.",
        "Use Loss reason carefully. The choices combine saved-sale abandonment reasons with submitted interaction no-purchase reasons. On interactions it keeps only no-purchase rows with that exact normalized display reason. On saved opportunities it keeps only abandoned sales with that exact reason and excludes currently open saved sales. Clear all returns every filter to its initial state.",
        "In Intelligence, read Interactions, No-purchase Interactions, Saved/Future Interest, and Interaction Conversion. Conversion equals purchased interaction rows divided by all filtered interaction rows; it is not receipt conversion and does not include uncaptured store traffic.",
        "Review Source Intelligence and Associate Intelligence. Each lists up to eight buckets ranked by interaction count, then purchases. Bought/lost counts are derived from submitted interaction outcome/status. Uncaptured source and Unknown associate indicate incomplete attribution rather than a zero-performance channel or person.",
        "Review Loss Reasons. Selecting a reason applies it as the shared Loss reason filter. Then read Currently Saved, Revenue on Reserve, Saved Abandoned, and Opportunity Lost, which come from sale statuses and totals—not from submitted interaction cards.",
        "Open Saved Sales. Currently Saved is status parked; Abandoned is status parked_abandoned; Completed from Saved uses completed_from_parked; One-time Completes are completed sales without that flag. Save Rate is open + abandoned + completed-from-saved divided by all filtered sales. Saved conversion is completed-from-saved divided by those three saved-history groups.",
        "Treat revenue cards as opportunity analysis. Revenue on Reserve sums totals on currently parked sales, Opportunity Lost sums parked_abandoned totals, Recovered Revenue sums completed-from-saved totals, and One-time Revenue sums other completed totals. They are not cash, deposits, tender, tax, margin, or recognized-revenue reports.",
        "Review By Associate. Saved/open/abandoned/completed-from-saved credit prefers origin associate and falls back to cashier; one-time completed credit uses cashier. Unknown/unattributed sales are not added to an associate row.",
        "Review Abandonment Reasons. Reasons come from signature metadata saved_sale_abandonment.reason, then void_reason, otherwise Unspecified. Counts and totals represent abandoned saved sales only.",
        "In Open & Abandoned Saved Sales, read sale number/date, origin associate/location, abandonment reason, total, age, and Saved/Abandoned badge. Age is calculated from sale created_at, not necessarily parked_at. Choose Follow up only when a customer is attached; it opens the customer profile. The external-link button opens the sale in Sales → Receipts. Neither action resumes the cart from this report.",
        "To actually continue an open saved sale, use the approved Register → Sell saved-sales picker/workflow with the intended location/register and an open register session. Check cart conflicts and editing ownership there. Do not infer that opening the receipt here claims or restores the Sell workspace.",
        "Open Interaction Log to review submitted cards. The badge reports all filtered matching interaction rows, while the list displays only the first 80. Each row shows receipt/customer, interaction type, outcome/status, customer/source/loss context, associate, location, occurred date, and whether it is submitted/openable.",
        "Owners and Super Admins can choose Open card and edit the submitted interaction through the dialog; other roles see Submitted and the row is noninteractive. After an authorized save, the page refetches interaction activity. Editing the card can change intelligence results, so document corrections and verify the updated filters/KPIs.",
        "Use this page for coaching and opportunity follow-up, then confirm operational truth in the customer, receipt, saved Sell workspace, and appropriate financial reports before acting. If a count looks wrong, capture the active filters, tab, date/time zone, record identifiers, stored statuses/outcomes, and origin fields rather than repeatedly changing the sale."
      ],
      "controls": [
        {
          "name": "Intelligence tab",
          "description": "Combines submitted-interaction KPIs/buckets with saved-sale opportunity overlays."
        },
        {
          "name": "Saved Sales tab",
          "description": "Sale-status conversion, revenue-opportunity, associate, abandonment, and open/abandoned opportunity analysis."
        },
        {
          "name": "Interaction Log tab",
          "description": "Filtered submitted interaction rows; badge can exceed the 80 rows rendered."
        },
        {
          "name": "Date range",
          "description": "Filters sales by created_at and interactions by occurred_at using full local days."
        },
        {
          "name": "Locations",
          "description": "Sales use location_id/origin_location_id; interactions use location_id."
        },
        {
          "name": "Registers",
          "description": "Sales use origin_register_id; interactions use metadata.register_id."
        },
        {
          "name": "Users",
          "description": "Sales use cashier_id/origin_associate_id; interactions use owner_id."
        },
        {
          "name": "Interaction outcome",
          "description": "Filters only interaction data using outcome with status fallback."
        },
        {
          "name": "Loss reason",
          "description": "Shared exact-label filter; for saved sales it retains matching abandoned records and excludes open parked records."
        },
        {
          "name": "Clear all",
          "description": "Clears date, location, register, user, interaction outcome, and loss-reason filters."
        },
        {
          "name": "Interaction Conversion",
          "description": "Purchased submitted interactions divided by all filtered submitted interactions."
        },
        {
          "name": "Source / Associate Intelligence",
          "description": "Top eight interaction buckets ranked by volume, showing bought and lost counts."
        },
        {
          "name": "Currently Saved",
          "description": "Count of filtered sales with status parked."
        },
        {
          "name": "Saved Abandoned",
          "description": "Count of filtered sales with status parked_abandoned."
        },
        {
          "name": "Save Rate",
          "description": "Open + abandoned + completed-from-saved count divided by all filtered sales."
        },
        {
          "name": "Saved conversion rate",
          "description": "Completed-from-saved divided by open + abandoned + completed-from-saved."
        },
        {
          "name": "Revenue on Reserve / Opportunity Lost",
          "description": "Sum of sale totals for parked / parked_abandoned statuses; not collected or recognized revenue."
        },
        {
          "name": "Abandoned → Completed",
          "description": "Completed-from-saved sales whose completed/created date is more than 30 days after parked_at."
        },
        {
          "name": "Follow up",
          "description": "Opens attached customer profile; appears only when customer_id exists."
        },
        {
          "name": "Receipt external link",
          "description": "Opens the saved/abandoned sale in Sales → Receipts; does not resume it."
        },
        {
          "name": "Open card",
          "description": "Owner/Super Admin action to inspect/edit a submitted interaction."
        },
        {
          "name": "80-row display limit",
          "description": "Interaction query can load up to 5,000, but the visible Interaction Log slices matching rows to 80."
        },
        {
          "name": "No exact screenshot",
          "description": "The real Amelia Grant Harbor & Hearth /sales/parked-report capture was rejected because the route redirected to the intelligence view and remained loading. No mismatched or fabricated screenshot is used."
        }
      ],
      "expectedResult": "The saved sale remains distinct from completed receipt history and shows the intended owner, reason, status, value, follow-up activity, and resume behavior.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "create-account-invoice",
      "url": "https://platform.getcentri.com/centripos/create-account-invoice",
      "title": "Create an invoice or save an unfinished draft",
      "summary": "Choose the customer, location, register, prices, fulfillment and terms, then save a draft, accept the order on account, or explicitly issue and send the invoice.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Customer Accounts",
      "introduction": "Creating an order, issuing its invoice, sending a notice and collecting payment are separate steps. Save as draft keeps unfinished work. Save on account accepts the order for fulfillment and records its open balance, but does not issue or send it to the customer. Save & send opens a recipient review; Save & mark as sent records that the invoice was already provided without sending a notice.",
      "beforeYouBegin": "Confirm the intended business, authorized customer, order location and register. Review the customer agreement, fulfillment requirements and payment terms. Use only the actions available to your role and business; do not work around an unavailable creation, sending or payment control.",
      "steps": [
        "Open Invoicing from Sales or Money → Invoices and choose New Invoice. If document creation is locked by the connected accounting workflow, ask the authorized administrator to review that workflow instead of creating a second obligation elsewhere.",
        "Attach the exact Customer account. Confirm the billing identity and any selected requester. Wait for the contact terms to finish loading; a contact-terms error blocks saving so the invoice does not silently use an unverified default.",
        "Choose Location and Register. Defaults can come from Invoice Settings or the current operating context. If a register choice is required, choose the intended register or explicitly choose No register. Changing the location can change available products, prices, tax and fulfillment options.",
        "Review Terms and where they came from: the contact profile, Invoice Settings, or an override for this invoice. Choose Payment terms start: When the invoice is issued, When delivery is completed, or When the order is created. A manually entered Due date overrides that calculated date. Delivery-based terms use actual completed delivery, not a requested delivery date.",
        "Add each catalog product or type a custom item. Review the selected variant, customer price, quantity, price and tax before continuing. Use Add line for another item and remove unwanted lines. An unavailable catalog selection or unfinished pricing/tax calculation must be corrected before saving.",
        "Use the line’s Notes, discount & fulfillment controls and the order fulfillment controls to review customer-facing notes, discounts, pickup, delivery or shipping details, destination, method, dates and fees where applicable. Review the complete order summary and total. Save to custom products is a separate catalog action available only with the required catalog access.",
        "Add the invoice memo and review Customer acceptance when offered. Requiring acceptance asks the customer to confirm the displayed terms; it does not itself mean the customer accepted, the invoice was sent, or money was collected. Proposals and estimates use their own review-and-accept workflow.",
        "Under collection options, choose Take no payment now, Customer pays, Charge now, or Charge on due date deliberately. These are different instructions. Review the enabled invoice payment option where offered; the saved-method collection flow retains its supported saved-method provider rather than moving an existing saved method to another processor.",
        "For Charge now or Charge on due date, choose the exact supported saved card or bank account and confirm the customer authorized that specific immediate or scheduled collection. A bank account can require a separate one-time authorization review on the original receipt after creation. Do not assume selecting a saved method completed the charge or established settlement.",
        "To stop with unfinished work, choose Save as draft. Success says Draft saved and directs you to continue it from Drafts. The draft is not billed or sent. Reopen that draft to continue; do not create another document merely because you closed the editor.",
        "To accept the reviewed order without issuing it, leave When saving set to Save on account. The result is saved on account and ready for fulfillment, with its open balance recorded. It remains On account · not issued until the first confirmed invoice send or an authorized Mark as sent action.",
        "To send the invoice, choose Save & send under When saving. After the order is saved, review the recipient, delivery route, message and selected documents in the Send composer. Use the explicit Send invoice action only after that review. Closing the composer leaves the saved order unsent. Preparing or previewing an email does not send it.",
        "Choose Save & mark as sent only when the invoice has already been provided to the customer outside this sending flow. This records issuance without sending a notice. Check the resulting issued date and terms-start basis; the action must not be used simply to make an unsent invoice look delivered.",
        "If immediate payment was requested and the result is uncertain, open the original receipt or account activity. Preserve the original attempt and check its status. Do not create another invoice, charge again, or record an additional received payment to resolve an uncertain outcome. If the bank path asks for one-time authorization, finish that review on the original receipt.",
        "After the save or send completes, reopen the exact invoice and linked receipt. Verify customer, location/register, lines, fulfillment, total, open balance, payment result, terms source/start, due date, issuance and sending state. Check the connected accounting copy and settlement separately when relevant; a local save, send or payment message does not prove either one."
      ],
      "controls": [
        {
          "name": "Customer account",
          "description": "Required billing identity; contact terms must be verified before saving."
        },
        {
          "name": "Location / Register",
          "description": "Order origin used for the invoice; choose No register explicitly when appropriate."
        },
        {
          "name": "Terms",
          "description": "Payment terms from the contact profile, business settings or an invoice override."
        },
        {
          "name": "Payment terms start",
          "description": "Issued, actual completed delivery, or order creation; separate from a requested fulfillment date."
        },
        {
          "name": "Due date",
          "description": "Explicit date override for this invoice when entered."
        },
        {
          "name": "Product or custom item",
          "description": "Catalog/variant selection or a custom description with quantity, price and tax."
        },
        {
          "name": "Notes, discount & fulfillment",
          "description": "Line and order details integrated with the normal order-entry controls."
        },
        {
          "name": "Save as draft",
          "description": "Retains unfinished work without billing or sending it."
        },
        {
          "name": "Save on account",
          "description": "Accepts the order for fulfillment and records its open balance without issuance or sending."
        },
        {
          "name": "Save & send",
          "description": "Saves first, then opens recipient and document review for an explicit send."
        },
        {
          "name": "Save & mark as sent",
          "description": "Records that the invoice was already provided; sends no notice."
        },
        {
          "name": "Take no payment now",
          "description": "Creates the order without collecting payment."
        },
        {
          "name": "Customer pays",
          "description": "Uses a customer payment request with explicit send review."
        },
        {
          "name": "Charge now",
          "description": "Attempts an authorized supported saved-method payment; recovery stays tied to the original invoice."
        },
        {
          "name": "Charge on due date",
          "description": "Sets up the selected authorized saved method for the displayed schedule; issuance and eligibility still matter."
        },
        {
          "name": "Customer acceptance",
          "description": "Separate agreement evidence; not a sending or payment result."
        },
        {
          "name": "On account · not issued",
          "description": "Accepted order with open balance, not yet issued for customer payment."
        },
        {
          "name": "Draft / proposal / invoice",
          "description": "Different document lifecycles; a proposal acceptance is not inferred from saving an invoice."
        }
      ],
      "expectedResult": "One intended draft or account order exists with the reviewed customer, origin, lines, fulfillment and total. Its issuance, sending and payment states match only the actions actually completed, and the original receipt/account record provides the next safe step.",
      "troubleshooting": [
        "If location, registers, contact terms, pricing or tax cannot be verified, correct that error before saving. Do not substitute another business or register merely to bypass a blocked control.",
        "If an order was saved but sending failed or was cancelled, reopen that existing invoice and use its Send tools. Do not create the same obligation again.",
        "If payment status is uncertain, use the original receipt and retained payment check. Do not retry a charge under a new invoice or record money as received without evidence.",
        "If the available controls differ from this workflow, confirm your role, business settings and enabled release with support. Include a safe document reference and the exact message; exclude private payment credentials."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "fulfillment-center",
      "url": "https://platform.getcentri.com/centripos/fulfillment-center",
      "title": "Run the Fulfillment Center",
      "summary": "Find, schedule, source, prepare, route, hand off, and complete pickup, local-delivery, and shipping work while preserving the related receipt and payment state.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Sales",
      "introduction": "Sales → Fulfillment uses the Truck icon. It works at sale-line-item level and groups related items for execution; status changes write immediately. Completing or signing is blocked when the sale itself is not completed unless an owner, store owner, super admin, or manager intentionally overrides the exception. A balance-due warning is informational, while a non-completed sale status is the completion gate. Verify the receipt and customer handoff before every terminal status.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Go to Sales → Fulfillment, identified by the Truck icon. The default view is Open work across All types and All locations. The selected type and status persist for the browser session; URL filters can also open a specific receipt, sale, location, or unscheduled set.",
        "Read the header counts. Open includes every status except completed, cancelled, and none. Ready counts ready line items. No date appears for open items without a fulfillment date, and Paid online identifies E-cart work that needs fulfillment action after customer payment.",
        "Use Find receipt with a receipt number such as S-80483. Entering receipt search removes any saleId URL filter so the result is driven by the receipt text. Clear the field to return to the current broader filter set.",
        "Choose All types, Local Delivery, Pickup, or Shipping; then choose Open work, All statuses, Pending, Needs sourcing, Ordered, Awaiting receipt, Received, Ready, Picked, Loaded, Scheduled, In Progress, Completed, or Cancelled. Status filtering is operational state—not payment or sale status.",
        "Choose All locations or one active location. Counts beside locations summarize open work for the current type/status/search/schedule filters before the location is applied. Use No date to isolate open work with no scheduled fulfillment date.",
        "Use the summary cards as filter shortcuts, then choose Queue for grouped execution or Calendar for date planning. The filters apply to both views. An empty queue after filtering is a completed state; clear receipt, type, status, location, and No date before concluding work is missing.",
        "In Queue, review the fulfillment type, operational status, customer/contact, sold-at and source locations, receipt status, balance due, method, date/time preference, sold-by user, line items, quantities, and any linked purchase order before acting. Choose the receipt number or Receipt to inspect the sale without changing the queue’s filter scope.",
        "If E-cart paid - fulfillment needs action appears, read the customer notice channel/recipient/time and choose Open receipt when payment or sale context needs confirmation. Do not charge again from this banner.",
        "Advance an individual line only to the state that matches physical reality. The guided sequence can move Pending → Ready; Needs sourcing → Ordered → Awaiting receipt → Received → Ready; local-delivery Ready → Picked → Loaded → In Progress → Completed; Scheduled → In Progress; and pickup/shipping Ready or In Progress → Completed.",
        "Use a linked purchase-order control to open sourcing evidence when present. Do not mark sourced merchandise Received or Ready merely because a PO exists; confirm actual receipt and item identity.",
        "Choose Mark ready to update all currently open items in the group to Ready. Choose Picked up for pickup, Shipped for shipping, or Completed for local delivery only after the customer or carrier handoff actually occurred. Each item update is saved separately, so verify the whole group after a multi-item action.",
        "If the sale is not completed, the handoff action opens Sale is not completed instead of completing. Choose Open receipt to fix/confirm the sale. Only an owner, store owner, super admin, or manager sees Override and complete; use it solely for an approved exception such as a Customer Accounts release and document the business reason.",
        "A balance due greater than one cent displays Payment / sale status check. The code blocks completion based on non-completed sale status, not the balance warning alone; follow the business’s account-release policy and confirm the receipt rather than interpreting the warning as automatic authorization.",
        "For pickup or local delivery, choose Sign to capture the customer acknowledgment. Saving the signature stores its time, staff identity, customer label, type, line-item IDs, receipt number, capture mode/device, and signature image, then marks every group item Completed. Shipping has no Sign button. Re-sign replaces the fulfillment acknowledgment metadata.",
        "Choose Print slip or Print <n> items for an internal/customer fulfillment document. It assembles grouped items plus available delivery address, sale note, selling location, printed-by identity, and saved signature. Inspect the print preview and recipient before printing.",
        "Choose SMS / email to create a new branded pos.getcentri.com public fulfillment-slip link and open delivery controls. Confirm the customer phone/email and message; each invocation creates a new token. Treat the link as customer-accessible and do not paste internal notes or unrelated receipt data into messages.",
        "Choose Schedule or Change date. The dialog applies the fulfillment date/time preference to every item in the group, advances pending line items to the scheduled workflow, and may update a pending sale to scheduled. Use the method-appropriate pickup, shipping, or delivery availability configured by Admin.",
        "In Calendar, move between months and select a date. Each day shows work count, type/status summaries, configured availability, full-capacity indication, or blackout state. The No date scheduled list shows at most the first ten unscheduled items in its compact panel; use the No date filter for the complete filtered result.",
        "Calendar availability and capacity come from the selected type: Pickup uses pickup schedules/overrides, Shipping uses shipping schedules/overrides, and All types defaults the calendar schedule model to Delivery. Filter to the intended type before interpreting availability or capacity.",
        "For Delivery calendar dates, authorized manager-level users can Black out date and add an internal note. The blackout prevents new delivery scheduling but does not move existing work already on that date. Reopen date removes the delivery override; verify existing commitments before either action.",
        "When a selected date contains local deliveries, switch between Items and Route. Items shows the normal fulfillment groups. Route groups delivery stops and supports operational stages Ready to Pick, Picked, Loaded, Out, and Delivered.",
        "In Route, confirm the saved primary delivery hub and usable hub/customer addresses. Drag stops only when route-management access permits, use Preview route for one routable stop or Optimize for multiple stops, review miles/time, then choose Save Route. Optimization depends on configured Mapbox geocoding/routing and does not save until Save Route.",
        "Use Route sequence and external map directions to validate source pickups, hub, and customer order. Open route follows the computed waypoint sequence. A missing/un-geocodable address can exclude a stop from optimization; never assume displayed sequence proves every delivery is routable.",
        "If available, create temporary driver route access and securely provide its branded link and PIN only to the assigned driver. Treat both as credentials, do not publish them in the knowledge base, and revoke/replace access according to operational policy. DispatchTrack connection is an optional external layer, not proof that the CentriPOS route was dispatched.",
        "After status, date, blackout, route, print, link, or signature action, re-open the group and receipt. Confirm line-item states, sale/payment state, scheduled date, customer/address, fulfillment document, signature, inventory/source work, and downstream receipt/Customer Account behavior before closing the task.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully loaded empty Fulfillment Center at 1440×900. It exposes the real filters, counts, summary cards, Queue/Calendar navigation, and Truck icon, but zero fulfillment items—so it contains no receipt, customer, address, route, payment, or signature data and no state was changed."
      ],
      "controls": [
        {
          "name": "Truck icon",
          "description": "Exact Sales navigation icon for Fulfillment."
        },
        {
          "name": "Open count",
          "description": "Every line item not completed, cancelled, or none under the active filters."
        },
        {
          "name": "Ready count",
          "description": "Line items currently at Ready."
        },
        {
          "name": "No date count/filter",
          "description": "Open items without fulfillment_date; toggle isolates them."
        },
        {
          "name": "Paid online",
          "description": "E-cart payment completed and fulfillment now needs operational action."
        },
        {
          "name": "Receipt search",
          "description": "Searches by receipt and clears a saleId URL filter when changed."
        },
        {
          "name": "Type filter",
          "description": "All, Local Delivery, Pickup, or Shipping."
        },
        {
          "name": "Status filter",
          "description": "Open work, all, or one of twelve explicit operational statuses."
        },
        {
          "name": "Location filter",
          "description": "Uses active locations and displays open counts under the other active filters."
        },
        {
          "name": "Summary cards",
          "description": "Clickable type/status shortcuts derived from the filtered item set."
        },
        {
          "name": "Queue",
          "description": "Grouped line-item execution view."
        },
        {
          "name": "Calendar",
          "description": "Date, schedule, capacity, blackout, items, and delivery-route planning view."
        },
        {
          "name": "Receipt link",
          "description": "Opens the related receipt; fulfillment UI state remains distinct from receipt-list filtering."
        },
        {
          "name": "Linked purchase order",
          "description": "Sourcing reference for an individual sale line."
        },
        {
          "name": "Mark ready",
          "description": "Immediately marks all currently open group items Ready."
        },
        {
          "name": "Picked up / Shipped / Completed",
          "description": "Type-specific group completion action."
        },
        {
          "name": "Sale completion gate",
          "description": "Non-completed sale status blocks completion and signature by default."
        },
        {
          "name": "Manager override",
          "description": "Owner/store owner/super admin/manager exception to complete before sale completion."
        },
        {
          "name": "Balance-due warning",
          "description": "Operational warning; not the code’s sale-status completion gate and not automatic release authorization."
        },
        {
          "name": "Sign / Re-sign",
          "description": "Pickup/delivery acknowledgment stored on the sale; saving also completes all group items."
        },
        {
          "name": "Print slip",
          "description": "Builds a fulfillment document with group items and available operational/customer details."
        },
        {
          "name": "SMS / email",
          "description": "Creates a new branded public fulfillment-slip token and opens send controls."
        },
        {
          "name": "Schedule / Change date",
          "description": "Applies date/preference across the group and advances pending scheduling state."
        },
        {
          "name": "No date scheduled list",
          "description": "Compact calendar panel limited to ten displayed unscheduled items."
        },
        {
          "name": "Availability source",
          "description": "Calendar schedule/overrides follow the selected type; All types uses Delivery schedule semantics."
        },
        {
          "name": "Delivery blackout",
          "description": "Prevents new scheduling only; does not move existing work."
        },
        {
          "name": "Items / Route",
          "description": "Selected-date delivery detail or route-management board."
        },
        {
          "name": "Route stages",
          "description": "Ready to Pick, Picked, Loaded, Out, Delivered."
        },
        {
          "name": "Optimize / Preview route",
          "description": "Mapbox-based ordering from the configured hub and routable customer addresses."
        },
        {
          "name": "Save Route",
          "description": "Persists the current stop order; optimization alone is a draft."
        },
        {
          "name": "Temporary driver access",
          "description": "Credentialed link plus PIN for the driver view."
        },
        {
          "name": "Sync receipt",
          "description": "Reapplies Completed to a completed group so receipt-linked state can be synchronized."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant /sales/fulfillment capture in a fully loaded zero-item state; no customer or transaction data is exposed."
        }
      ],
      "expectedResult": "The fulfillment record shows the current operational status, schedule, assignment, customer-safe destination, items, and completion history.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/sales-fulfillment.png",
        "alt": "Harbor & Hearth Fulfillment Center showing receipt search, type, status, location, date, queue, and calendar controls in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "dispatch-delivery",
      "url": "https://platform.getcentri.com/centripos/dispatch-delivery",
      "title": "Plan a delivery route and use the driver workflow",
      "summary": "Build the selected day’s local-delivery route, prepare each stop, share temporary driver access, update real fulfillment states, and capture the supported delivery acknowledgement.",
      "collection": {
        "id": "sales",
        "title": "Sales & fulfillment"
      },
      "section": "Fulfillment",
      "introduction": "Use Sales → Fulfillment and select the delivery date. Route ordering, optimization, adding stops, saving, and creating a Driver link are limited to managers, owners, and super admins. DispatchTrack controls appear only when that integration is connected. The current native workflow captures a customer signature; it does not offer a delivery-photo or free-form exception control on this route screen.",
      "beforeYouBegin": "Confirm the customer-safe sale or order reference, its location, and its current fulfillment status before making a change.",
      "steps": [
        "Open Sales → Fulfillment, choose the date, and focus the Local Delivery route. A stop groups line items from the same sale, date, time preference, and address.",
        "Review the route hub, its address, source locations, each customer address and phone, time preference, delivery method, receipt number, item quantities/SKUs, source location, balance due, and existing Signed indicator. Correct the sale or fulfillment record before routing if any of these are wrong.",
        "Managers can use Add to pull an open delivery from another or unscheduled date into the selected day. This changes the line and sale fulfillment date; use Optimize again afterward.",
        "Check each prepared item. An unchecked ready line becomes Picked when checked and returns to Ready when unchecked. Mark loaded remains disabled until every item in the stop is picked.",
        "Drag stops into a manual order on desktop when authorized, then choose Save Route. Driver-mode users can work stops but cannot save route ordering.",
        "Choose Preview route for one routable customer stop or Optimize for multiple stops. Optimization requires a configured Mapbox key, a saved hub address, and at least one customer delivery address. It geocodes the hub, source pickups, and customer stops, then shows estimated miles and minutes. Review the order and choose Save Route; optimization alone leaves the route dirty and unsaved.",
        "Use Open route or a stop’s Directions action to open external turn-by-turn directions. A missing address disables stop directions and prevents that stop from being routed.",
        "Choose Driver link to create temporary route access. CentriPOS displays and copies the branded route URL plus a six-character PIN. Share both securely with the intended driver. The link does not create a POS account; an unavailable link requires a fresh one from the fulfillment manager.",
        "In the driver page, enter the PIN if required. The page shows today’s stops, next stop, address, phone, method/time, stop status, and item list. Use Navigate, Loaded, On the way, and Delivered to record the actual state.",
        "On the way starts foreground device-location reporting when the browser grants geolocation permission. The page labels this Foreground GPS and shows the last device-location time; do not promise background tracking after the page/browser is suspended.",
        "In the manager route, the equivalent controls are Mark loaded, Out, and Signature. Signature records the acknowledgement “Customer acknowledges receipt of delivered merchandise,” capture mode/device metadata, delivered time/user, receipt, and line IDs, then marks the stop completed.",
        "The driver’s Delivered action marks the stop completed without collecting a signature in that driver page. If the business requires signed acknowledgement, capture Signature from the fulfillment route and verify the Signed indicator/receipt data rather than treating Delivered alone as signed proof.",
        "When DispatchTrack is connected, use the per-stop DispatchTrack button to export that sale. The connection banner means external planning can be layered over the native route; verify the export result in the connected workflow instead of assuming every route or later status synchronized.",
        "After completion, confirm every line has the intended fulfillment status, the stop is in the completed stage, and any required signature is visible. Reconcile remaining balance separately; route completion does not prove customer payment."
      ],
      "controls": [
        {
          "name": "Delivery date",
          "description": "Controls which local-delivery stops appear on the route board."
        },
        {
          "name": "Route hub",
          "description": "Configured delivery location and starting address required for optimization."
        },
        {
          "name": "Source pickup",
          "description": "Non-hub inventory location inserted before the customer stops that need its items."
        },
        {
          "name": "Stop",
          "description": "Grouped delivery for one sale/date/time preference/address."
        },
        {
          "name": "Item checkbox",
          "description": "Moves a ready line to Picked, or a picked line back to Ready."
        },
        {
          "name": "Mark loaded / Loaded",
          "description": "Moves all stop items to loaded after preparation."
        },
        {
          "name": "Out / On the way",
          "description": "Moves the stop to in progress; the driver page also starts foreground GPS when permitted."
        },
        {
          "name": "Delivered",
          "description": "Driver-page completion action; it does not itself capture a signature."
        },
        {
          "name": "Signature",
          "description": "Manager-route acknowledgement capture that stores delivery metadata and completes the stop."
        },
        {
          "name": "Directions / Navigate",
          "description": "Opens external directions for a saved customer address."
        },
        {
          "name": "Preview route / Optimize",
          "description": "Mapbox-backed route calculation requiring a key, hub address, and customer address."
        },
        {
          "name": "Save Route",
          "description": "Persists the authorized manual or optimized ordering."
        },
        {
          "name": "Driver link",
          "description": "Temporary branded route URL paired with a six-character PIN; it is not a Centri Account."
        },
        {
          "name": "Foreground GPS",
          "description": "Location updates while the route page remains active and browser permission is granted."
        },
        {
          "name": "DispatchTrack",
          "description": "Optional per-sale export shown only for a connected DispatchTrack setup."
        },
        {
          "name": "Balance",
          "description": "Amount still due on the sale; delivery status does not settle it."
        },
        {
          "name": "No delivery photos",
          "description": "The current route and driver screens do not provide a photo-proof control."
        },
        {
          "name": "No free-form exception control",
          "description": "Record failed/changed delivery outcomes only through an actual available status or the business’s separate support/notes workflow."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest contains no privacy-safe delivery route with real stops, so this guide uses no fabricated image."
        }
      ],
      "expectedResult": "The delivery moves through assignment and dispatch once, the driver records the supported completion evidence, and CentriPOS reflects the final outcome.",
      "troubleshooting": [
        "Keep the current receipt or order filters in place while opening details.",
        "Check the record status and activity before repeating a send, return, or fulfillment action.",
        "Use a safe receipt or order reference when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "live-inventory",
      "url": "https://platform.getcentri.com/centripos/live-inventory",
      "title": "Read Live Inventory",
      "summary": "Read current tracked on-hand and reserved quantities by product, variant, and location; understand the exact stock-tab and reorder calculations; and follow real catalog, transfer, and variant evidence without inventing accounting-period or export controls.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Inventory → Live Inventory uses the Layers icon. This screen has no accounting-period date, opening/closing balance, Summary/Replenishment/Performance/Dusty views, Inventory by location dashboard, View movements action, or Export control. It reads the currently loaded active tracked products and URL-backed filters. For variable products, variant-location stock is authoritative for displayed totals, but the Below Reorder calculation still reads parent product location_stock reorder fields; validate variant reorder evidence separately. Cost-visible Value is base product supply_price multiplied by displayed on-hand, not a supplier price-book, FIFO, landed-cost, or accounting valuation.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Live Inventory, identified by the Layers icon. Confirm the active business and the current app location context before reading quantities. Wait for the product loader to finish.",
        "Start with the URL state. Search is `q`; one location is `loc`; stock view is `tab`; expanded product/variant are `expand` and `expandVariant`; Brand/Category/Tag/Supplier/Type filters are comma-separated IDs. A shared URL preserves the view but does not grant inventory/cost permission.",
        "Read the stock tabs that actually exist: In Stock, Below Reorder, Zero Stock, Negative, and All. The default is In Stock unless an `expand` product is supplied, in which case an absent tab defaults to All. There are no Summary, Performance, Out of Stock, or Dusty tabs on this component.",
        "Use Location to choose All or one visible location. Although the shared dropdown supports multiple IDs, this screen keeps only the first selected ID when more than one is returned. Confirm the trigger’s final single location; do not represent the results as a multi-location subset unless it says All.",
        "Search matches only the parent product name or parent SKU by simple lowercase substring. It does not search barcode, variant name/SKU, supplier code, or attribute values. Expand a variable product or use Products search when variant identity is required.",
        "Use Brand, Category, Supplier, Tag, and Type. Supplier membership comes from product_suppliers rows loaded separately; a fetch error is not surfaced here and can make a supplier filter return no products. Type derives Variable from any variants, Composite from stored type, and Standard from non-composite products without variants.",
        "Understand filter logic. Multiple IDs within Brand, Category, Supplier, or Tag use any-match. Different groups all must pass. Product type passes when any chosen type rule matches. Clear removes search and these five attribute filters, but it does not reset Location, stock Tab, or expanded product/variant.",
        "Read tab counts after search, attributes, type, supplier mapping, and selected location, but before applying the active stock tab. Only products with track_inventory true participate. In Stock is on-hand >0; Zero equals 0; Negative is <0; All includes all tracked matches.",
        "For standard products, on-hand is the product location_stock quantity at one location or the sum across all location rows. For variable products, on-hand is the sum of every variant_location_stock quantity in scope; parent location_stock is not added to the headline. Untracked products are excluded entirely rather than shown as infinity.",
        "Below Reorder counts a product only when a parent location_stock row has a non-null reorder_point and on-hand is greater than zero but below the point. With one location it checks that row; with All it checks whether any parent row qualifies. Zero and negative quantities are deliberately not Below Reorder.",
        "For variable products, the displayed/tab on-hand comes from variant rows while Below Reorder still checks parent product location_stock. A variable item can therefore show variant units that do not align with its below-reorder classification/detail. Inspect each variant’s reorder point and correct source data through the authorized product/inventory workflow.",
        "Read the stats carefully. Tracked always shows the total number of loaded track_inventory products and ignores search/location/tab filters. Total Units and Value sum only the currently displayed `filtered` rows after the active tab. Below Reorder uses the pre-tab filtered count. These four cards do not necessarily share one scope.",
        "Cost-visible Value is product.supply_price × displayed on-hand for each row. For a variable product it multiplies the parent base supply price by summed variant units rather than using each variant cost. Negative stock reduces total value. Cost-hidden users see bullets and no row/expanded cost values. Use finance/inventory reports for accounting valuation.",
        "Choose Stats/Hide to manually collapse or expand the cards. Scrolling the product list downward past 50 pixels auto-collapses them; returning within 10 pixels of the top auto-expands unless the user manually collapsed at the top. On mobile stats begin collapsed and show a compact tracked/units/value line.",
        "When In Stock is active and any Below Reorder match exists, use the warning banner’s View action to switch to Below Reorder. The banner count follows parent reorder logic, not the separate visual low-stock fallback of positive quantity below 10.",
        "Read a row’s product name, parent SKU, optional brand, variant count, count of locations with stock rows, held-transfer badges, on-hand, and cost-visible base value. Row color treats negative as destructive, zero muted, below-reorder or any positive quantity below 10 as warning, otherwise success. The below-10 warning is visual only and does not add the product to Below Reorder.",
        "A held-transfer Lock badge comes from location_transfer_items with is_held true and a transfer not Received or Cancelled. It shows quantity_requested and links to Location Transfers. It does not subtract from the displayed on-hand here, identify source/destination in the badge, or prove dispatch/receipt. Open the transfer.",
        "Expand a product for Stock by Location and Open in Catalog. Every configured location is shown. Standard products use parent stock/reserved; variable products sum variant stock/reserved. Available equals on-hand minus reserved and is shown only when reserved is positive.",
        "For variable products, a nonzero parent location_stock alongside variant-authoritative stock displays Unassigned parent. This is a reconciliation warning: those parent units are not included in the variable product headline/variant sum. Investigate movements and product conversion history before adjusting.",
        "Location cards show reorder point/quantity from parent location_stock even for variable products. Low styling requires positive on-hand below reorder; negative has destructive styling; zero is muted. The card’s cost-visible amount is still parent product supply_price × location on-hand.",
        "For a standard/nonvariable product, expansion also loads supplier price-list entries and can show their supporting price/cost evidence in the expanded panel. That fetch ignores errors and is not performed for variable products here. An absent price list is not proof none exists.",
        "For a variable product, use Variant Inventory by SKU. The variant-location filter starts from the main single Location or All and then supports its own multi-location selection. This nested filter changes only the expanded variant table/summary, not the main list or headline row.",
        "Expand a variant to see one row per selected configured location with on-hand, reserved, available, reorder point/quantity, and cost-visible variant supply price where data exists. No stock recorded instructs staff to use Product Settings → Variant → Inventory; do not invent a zero row when no record exists.",
        "The expanded variant ID remains in the URL and scrolls to the variant after render. Collapsing/changing the parent clears expandVariant. Confirm both product and variant IDs in a shared link before acting.",
        "Below Reorder detail with All locations lists qualifying positive parent location rows and can show On Hand, Reorder at, Order Qty, and “Need” calculated as reorder quantity minus on-hand. With one location, Need uses reorder quantity when present, otherwise reorder point, minus on-hand. Negative/zero exceptions belong in their own tabs.",
        "No tracked inventory products found means no tracked product survived the current search/attribute/location/tab logic. Clear search/attributes, choose All location and All tab, and confirm product tracking before concluding inventory is absent.",
        "For a discrepancy, open the exact product in Catalog, then use Inventory Movements, Transfers, Receiving, Counts, or Adjustments as appropriate. Record product/variant IDs, selected location, URL filters, parent versus variant stock, reserved, unassigned parent amount, reorder fields, held transfer ID, and cost-visibility state.",
        "Use the real Amelia Grant Harbor & Hearth screenshot for orientation. It is the approved loaded `/inventory/live` capture at 1440×900. It shows actual stock totals, filters, and product quantities; no inventory change, transfer, count, customer, cost export, or transaction mutation was performed."
      ],
      "controls": [
        {
          "name": "Layers icon",
          "description": "Exact CentriPOS Inventory navigation icon for Live Inventory."
        },
        {
          "name": "Tracked product boundary",
          "description": "Only loaded products with track_inventory true appear."
        },
        {
          "name": "In Stock",
          "description": "Scoped on-hand greater than zero."
        },
        {
          "name": "Below Reorder",
          "description": "Positive parent location_stock below non-null reorder_point; zero/negative excluded."
        },
        {
          "name": "Zero Stock",
          "description": "Scoped on-hand exactly zero."
        },
        {
          "name": "Negative",
          "description": "Scoped on-hand below zero."
        },
        {
          "name": "All",
          "description": "All tracked products surviving search/attribute/type filters."
        },
        {
          "name": "Location",
          "description": "One location or All; multiple dropdown IDs collapse to the first."
        },
        {
          "name": "Search",
          "description": "Parent product name or SKU only."
        },
        {
          "name": "Brand / Category / Supplier / Tag",
          "description": "Any-match within each filter; all groups must pass."
        },
        {
          "name": "Type",
          "description": "Derived Standard, Variable, or Composite rules."
        },
        {
          "name": "Clear",
          "description": "Resets search and product filters only—not tab, location, or expansion."
        },
        {
          "name": "Tracked stat",
          "description": "All loaded tracked products, regardless of current filters/tab."
        },
        {
          "name": "Total Units",
          "description": "Sum of rows in the active filtered stock tab."
        },
        {
          "name": "Below Reorder stat",
          "description": "Pre-tab count after search/attributes/location using parent reorder rows."
        },
        {
          "name": "Value",
          "description": "Base parent supply_price × current filtered on-hand; not accounting valuation."
        },
        {
          "name": "Stats auto-collapse",
          "description": "Scroll-down and mobile behavior with manual override."
        },
        {
          "name": "Below-reorder banner",
          "description": "Switches In Stock to Below Reorder."
        },
        {
          "name": "Below-10 styling",
          "description": "Visual row warning only; not the Below Reorder rule."
        },
        {
          "name": "Standard stock",
          "description": "Parent product location_stock in one location or summed All."
        },
        {
          "name": "Variable stock",
          "description": "Sum of variant_location_stock; parent stock excluded."
        },
        {
          "name": "Held Lock badge",
          "description": "Open held transfer quantity_requested; does not change displayed on-hand."
        },
        {
          "name": "Reserved",
          "description": "Committed quantity displayed in expansion when positive."
        },
        {
          "name": "Available",
          "description": "On-hand minus reserved, shown when reserved is positive."
        },
        {
          "name": "Unassigned parent",
          "description": "Parent stock on a variable product excluded from authoritative variant total."
        },
        {
          "name": "Stock by Location",
          "description": "Every configured location, regardless of main list location filter."
        },
        {
          "name": "Open in Catalog",
          "description": "Working product editor/details route."
        },
        {
          "name": "Variant Inventory by SKU",
          "description": "Nested variant/location evidence with its own multi-location filter."
        },
        {
          "name": "Variant expansion",
          "description": "Location rows, on-hand, reserved, available, reorder, and variant cost."
        },
        {
          "name": "No stock recorded",
          "description": "No variant stock rows; not necessarily an explicit zero record."
        },
        {
          "name": "Need",
          "description": "Reorder target/quantity minus on-hand when positive."
        },
        {
          "name": "No export/accounting-period control",
          "description": "This component has neither an export nor accounting date/balance workflow."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real approved loaded Live Inventory capture with no mutation."
        }
      ],
      "expectedResult": "The exact tenant, single location or All, stock tab, search, URL filters, product, variant, and expansion scope are confirmed; parent versus variant on-hand, reserved, available, unassigned parent stock, reorder fields, held transfers, and source movements explain the result; card/stat scope differences and base-cost value limitations are understood; and no absent accounting-period/export control is invented.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/inventory-live.png",
        "alt": "Harbor & Hearth Live Inventory screen showing stock totals, locations, replenishment filters, and product quantities in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "receive-inventory",
      "url": "https://platform.getcentri.com/centripos/receive-inventory",
      "title": "Receive inventory",
      "summary": "Receive a supplier shipment directly or count it against an existing purchase order without confusing the two posting paths.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Receive Stock uses the exact PackagePlus navigation icon and opens the direct-receipt history at /inventory/receive. That screen is specifically for product received without a purchase order. A delivery that belongs to a PO must be received from the saved purchase order instead so ordered, previously received, remaining, landed-cost, status, and short-shipment records stay connected. Both paths change inventory immediately and perform several writes; verify the result before retrying after any error.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Count the physical delivery and identify whether it belongs to a CentriPOS purchase order. Use Inventory → Receive Stock only when it does not. For a PO delivery, use Inventory → Purchase Orders, open the exact PO, confirm its receiving location and lines, and choose Receive.",
        "On Receive Stock, read the newest-first history before posting. Desktop shows Date, Supplier, Location, Reference, Items, and Total Cost; mobile cards show the same essentials. Items is the number of receipt line rows, not the sum of all received units. The first 30 records load initially and Load more reveals 30 more.",
        "A history row is not an editable receipt-detail view: this screen has no row-open, search, filter, export, delete, recall, or correction action. View QBO Bill appears only when a later accounting link exists and opens that external bill; creating a direct receipt here does not itself present or guarantee a QBO posting.",
        "Choose New Receive. Location is required and starts from the active operating location. Supplier is optional. Reference # and Notes are optional, but use the supplier invoice or delivery-note number and a concise exception note when they are available. Verify the location before adding lines; all lines in this direct receipt post there.",
        "Search for the exact product or variant. Adding the same product-and-variant combination again increments its quantity by one; a different variant creates a separate line. Review product and variant names carefully because the editable line does not display its saved SKU.",
        "Enter a whole-number Qty and Unit Cost for every line. The browser controls suggest Qty 1 or greater and Unit Cost 0 or greater, but the current form does not provide a final validation summary. Decimal quantities are truncated, an empty or zero quantity becomes 1, and manually typed negative values are not reliably rejected by application logic. Stop and correct every value before posting.",
        "Use the trash icon to remove an unsaved direct-receipt line. Confirm the line count, total units manually, extended cost for each line, optional supplier/reference, and required location. Choose Receive Stock once; the button shows a spinner while saving.",
        "A direct receipt first creates its header and total cost, then its item rows, then applies one stock movement per line using movement type PO receive and source type stock receive. These operations are not one database transaction. The item-row insert error is not checked, and a later line can fail after earlier stock movements succeeded. If an error appears, do not submit again until history, live stock, and Inventory Movements are compared line by line.",
        "For a PO delivery, the Receive Stock dialog starts every still-receivable line at 0 and shows product/variant, SKU, Ordered, Prev, Remaining, planned location distributions, pack details when present, and a quantity field. It does not automatically assume that the remaining quantity arrived.",
        "Choose Count Sheet to print expected ordered/remaining information, or Blind Count to omit expected quantities. Both exclude costs. Scan Barcode opens the continuous camera scanner: a product barcode adds one, a configured case-pack barcode adds its units-per-pack, an unknown code shows an error, repeat scans within two seconds are ignored, and quantities are capped at Remaining. Choose Done Scanning when finished.",
        "Enter or scan the physical quantity for each line. Zero means not delivered. A value is clamped from 0 through Remaining and decimal text is parsed as a whole number. The footer totals units being received; Next remains unavailable until at least one unit is above zero.",
        "When any line is short, choose one of the three exact outcomes. Back-order remaining keeps the PO Partially Received for later. Close and create continuation PO closes this PO on received/payable quantities and creates a linked continuation PO for the remainder. Close PO as-is closes it on received/payable quantities and stops tracking the missing units on this PO. Review the listed short lines before continuing.",
        "On Receive Summary, verify PO number, supplier when present, receiving location, total units, every positive line, short badges, and the chosen remainder outcome. This summary does not display the expected date, fee calculation, or line costs. Enter the receiver’s full name, select the physical-verification attestation, and choose Confirm Receive once.",
        "PO receiving updates each positive line and applies its movement sequentially, updates average/last cost, then updates or closes the PO and may create continuation/distribution records. This is not a single all-or-nothing transaction; several update calls are not error-checked and auto-created distribution-transfer item errors can be silent. A success toast alone is insufficient for a material receipt.",
        "After either path, verify exact product/variant on-hand at the receiving location and source-linked rows in Inventory Movements. For a PO, also reopen the PO to verify received quantities, payable totals, receiver, status, continuation PO, and any requested distribution transfers. If anything differs or the save reported an error, preserve the reference and contact an authorized inventory owner before retrying. A received PO has a reason-required Recall receive workflow that deducts received stock, resets line quantities, records the recall, and permits re-receiving; the direct Receive Stock history has no equivalent recall control.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth direct-receipt history exposed supplier names, internal references, locations, item counts, and vendor cost totals, so the exact capture was rejected instead of being published, substituted, or fabricated."
      ],
      "controls": [
        {
          "name": "PackagePlus icon",
          "description": "Exact CentriPOS navigation icon for Receive Stock."
        },
        {
          "name": "Receive Stock route",
          "description": "Direct supplier receiving without a PO at /inventory/receive."
        },
        {
          "name": "Newest-first history",
          "description": "Date, optional supplier, location, optional reference, receipt-line count, and total cost; 30 records per batch."
        },
        {
          "name": "Items",
          "description": "Number of receipt line rows, not total units."
        },
        {
          "name": "View QBO Bill",
          "description": "External link shown only when an accounting bill URL is already attached."
        },
        {
          "name": "New Receive",
          "description": "Resets and opens a direct receipt."
        },
        {
          "name": "Supplier (optional)",
          "description": "Optional vendor relationship on the direct receipt."
        },
        {
          "name": "Location *",
          "description": "Required destination for every direct-receipt line; initialized from active location."
        },
        {
          "name": "Reference # / Notes",
          "description": "Optional source-document identity and internal context."
        },
        {
          "name": "Products",
          "description": "Exact product/variant search; selecting an identical combination again adds one unit."
        },
        {
          "name": "Qty / Unit Cost",
          "description": "Editable direct-receipt values with limited application-level validation; review before posting."
        },
        {
          "name": "Direct-receipt save boundary",
          "description": "Header, unchecked item-row insertion, and sequential movements are not one atomic operation."
        },
        {
          "name": "PO Receive Stock",
          "description": "Saved-PO workflow for remaining ordered lines."
        },
        {
          "name": "Ordered / Prev / Remaining",
          "description": "Original quantity, earlier received quantity, and amount still receivable."
        },
        {
          "name": "Count Sheet",
          "description": "Prints expected quantities without costs."
        },
        {
          "name": "Blind Count",
          "description": "Omits expected quantities and costs."
        },
        {
          "name": "Scan Barcode",
          "description": "Continuous camera scan for product or configured case-pack barcodes, capped at Remaining."
        },
        {
          "name": "Back-order remaining",
          "description": "Leaves the PO Partially Received."
        },
        {
          "name": "Close and create continuation PO",
          "description": "Closes on received/payable quantities and creates a linked remainder PO."
        },
        {
          "name": "Close PO as-is",
          "description": "Closes on received/payable quantities without tracking the missing units on this PO."
        },
        {
          "name": "Receiving attestation",
          "description": "Full name plus physical-verification checkbox required before confirmation."
        },
        {
          "name": "Recall receive",
          "description": "Reason-required received-PO correction that reverses stock and resets received quantities; unavailable on direct-receipt history."
        },
        {
          "name": "No public screenshot",
          "description": "Exact Harbor & Hearth history was rejected as private financial content; no substitute is used."
        }
      ],
      "expectedResult": "The exact direct-receipt or purchase-order path, destination location, product/variant lines, whole-unit quantities, costs, source reference, receiver, and short-shipment outcome are verified; on-hand and source-linked movement rows reconcile line by line; PO received/payable totals, status, continuation, and distribution transfers reconcile when applicable; and an uncertain or partial multi-write result is investigated before any retry.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "inventory-counts",
      "url": "https://platform.getcentri.com/centripos/inventory-counts",
      "title": "Create and complete an inventory count",
      "summary": "Schedule or start a location-specific count, control its catalog scope, record physical quantities, submit it for review, and post an audited stock snapshot.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Open Inventory → Counts with the Clipboard Check icon. Posting is irreversible: blank lines become zero, the chosen effective timestamp is treated as the physical snapshot, and later supported stock movements are replayed before live quantity changes. Only the assigned reviewer, an owner, or a super admin can perform final review and posting.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Counts. Use the count-list status filter for Active counts, Inactive counts, All counts, Scheduled, Counting, Review, Posted, or Cancelled; then optionally filter by location or search the count name, location, responsible person, status, or dates.",
        "Choose New Count. Enter a Name, select the exact Location, and assign a Responsible manager. The manager list contains active staff with access to that location plus owners and super admins.",
        "Choose Product status: Active, Inactive, or All status. Changing this selection clears current include and exclusion chips so filters from the previous status cannot silently remain.",
        "Choose Full catalog for all tracked items allowed at the location minus exclusions, or Partial count to require at least one included product, SKU, category, brand, supplier, or tag. Add optional exclusions using those same six filter types. Exclusions remove matches from either scope.",
        "Remember that countable lines also honor product/category location availability and active Location-scoped Availability Rules. Register-scoped Availability Rules do not affect a location count. The preview states how many products and product/variant items are ready.",
        "If this scope will be reused, name it under Saved count filters and choose Save. A saved filter retains product status, includes, and exclusions; it does not preserve old expected quantities.",
        "Set Scheduled date, Complete by, and count instructions as needed. Choose Schedule to create a Scheduled count, or Start Count to create it in Counting status immediately. Name, location, responsible manager, and at least one countable line are required.",
        "Open the count. Read its location, responsible person, status, counted/total progress, Differences, and Uncounted. Use Print Sheet for a physical worksheet. Use Search count items, Advanced filters, and Group by category, supplier, product, or no grouping to organize the lines without changing their scope.",
        "For each physical item, enter Counted directly or use plus/minus. System is the captured expected quantity; Diff is Counted minus System. A blank is uncounted and is not the same as an intentional zero.",
        "Choose Save Progress whenever unsaved changes are shown. Review remains disabled until at least one item is counted and every draft change is saved. Counted Entries distinguishes Draft from Saved and can reset one entry; the row Trash control, category reset, or More → Reset whole count clears counted values back to blank after confirmation without changing system quantities.",
        "Use Edit Scope only when the active count is eligible to be rescoped. Rescoping rebuilds its sheet from the current filters and should be avoided after physical counting begins unless the team deliberately reconciles the changed rows. Duplicate copies the saved filter into a different location and recalculates expected quantities there.",
        "When counting is ready for another person, choose Review, read Counted items, Current differences, and Uncounted if posted, add a useful submission note, and choose Submit for Review. An authorized reviewer can choose Back to Counting when corrections are needed.",
        "Before posting, the reviewer must resolve every blank deliberately. The Post Inventory Count summary states Uncounted to 0 because every uncounted line will post as zero. Review matched lines, differences, total absolute difference, and the submission note before continuing.",
        "Set Effective count date. Use Today only if the physical count represents now; use Count start or another accurate past timestamp when it represents an earlier snapshot. CentriPOS previews supported later sales, transfers, returns, fulfillments, and bundle-component movement and replays them into the posted live quantity. Posting date remains the actual time the reviewer posts.",
        "Resolve every bundle SKU mapping exception shown in the posting dialog. Post Count stays disabled while the movement preview is loading or exceptions remain. Add posting notes, then choose Post Count once.",
        "After posting, print the Count Report if needed and verify Live Inventory and Movements for the counted location. Posted counts can hide zero lines until Show all is enabled. A posted count cannot be undone; make any correction through a new inventory count or the authorized adjustment workflow, preserving the original audit record."
      ],
      "controls": [
        {
          "name": "Clipboard Check icon",
          "description": "The exact CentriPOS navigation icon for Inventory → Counts."
        },
        {
          "name": "New Count",
          "description": "Opens the location-specific count setup and scope builder."
        },
        {
          "name": "Status filter",
          "description": "Active, Inactive, All, Scheduled, Counting, Review, Posted, or Cancelled count lists."
        },
        {
          "name": "Responsible manager",
          "description": "Active location-authorized staff member assigned to receive and perform final review; owners and super admins are also eligible."
        },
        {
          "name": "Product status",
          "description": "Active, Inactive, or All catalog records. Changing it clears include and exclusion selections."
        },
        {
          "name": "Full catalog",
          "description": "All tracked and location-allowed countable items after exclusions."
        },
        {
          "name": "Partial count",
          "description": "Requires at least one included product, SKU, category, brand, supplier, or tag, then applies exclusions."
        },
        {
          "name": "Saved count filters",
          "description": "Reusable product-status/include/exclusion setup; expected quantities are recalculated when a count is created."
        },
        {
          "name": "Countable-item preview",
          "description": "Number of distinct products and product/variant lines that will be captured for the selected location and rules."
        },
        {
          "name": "Schedule",
          "description": "Creates the count in Scheduled status."
        },
        {
          "name": "Start Count / Start",
          "description": "Creates or moves a count into Counting status."
        },
        {
          "name": "Print Sheet",
          "description": "Printable physical-count worksheet for the captured count lines."
        },
        {
          "name": "System",
          "description": "Expected quantity captured for the line when the count sheet was built."
        },
        {
          "name": "Counted",
          "description": "Physical quantity entered for the line; blank means uncounted, while 0 is an intentional zero."
        },
        {
          "name": "Diff",
          "description": "Counted minus System; positive adds and negative removes stock when the count is posted, subject to effective-time movement replay."
        },
        {
          "name": "Save Progress",
          "description": "Persists current draft count entries; its badge states how many remain unsaved."
        },
        {
          "name": "Counted Entries",
          "description": "History menu showing saved and draft values and allowing an eligible entry reset."
        },
        {
          "name": "Trash / reset controls",
          "description": "Clear selected, category, or whole-count entries back to blank after confirmation; expected quantities stay intact."
        },
        {
          "name": "Advanced",
          "description": "Filters displayed count lines by product, size, category, supplier, and count state and supports tiered sorting."
        },
        {
          "name": "Group by",
          "description": "Organizes visible rows by category, supplier, product, or no grouping without changing the count sheet."
        },
        {
          "name": "Edit Scope",
          "description": "Rebuilds an eligible active count from changed filters; use cautiously after physical work begins."
        },
        {
          "name": "Duplicate",
          "description": "Copies the scope/filter into another location and recalculates that destination’s expected quantities."
        },
        {
          "name": "Review",
          "description": "Submits saved progress, differences, uncounted count, note, submitter, and assigned reviewer for approval."
        },
        {
          "name": "Back to Counting",
          "description": "Returns a review-stage count for corrections when the current user is authorized to review it."
        },
        {
          "name": "Effective count date",
          "description": "Timestamp represented by the physical snapshot; supported later movements are replayed after it."
        },
        {
          "name": "Uncounted to 0",
          "description": "Posting rule that converts every blank line in the captured count sheet to zero."
        },
        {
          "name": "Post-count movement rows",
          "description": "Supported stock movements after the effective timestamp that are incorporated into final live quantity."
        },
        {
          "name": "Bundle SKU mapping exception",
          "description": "Posting blocker requiring catalog mapping correction before replay and posting can be trusted."
        },
        {
          "name": "Post Count",
          "description": "Irreversible authorized action that posts the snapshot and movement replay to live stock."
        },
        {
          "name": "Print Report",
          "description": "Available on a Posted count for its final audit report."
        },
        {
          "name": "Show all",
          "description": "On a Posted count, reveals zero-quantity rows hidden by the default compact result."
        }
      ],
      "expectedResult": "The count closes with every counted line resolved, approved variances post once, and resulting quantities and adjustment activity appear at the counted location.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "stock-adjustments",
      "url": "https://platform.getcentri.com/centripos/stock-adjustments",
      "title": "Create and Audit Inventory Adjustments",
      "summary": "Correct a known stock variance at one location with controlled reasons, variant-aware quantities, optional supplier cost basis, and movement evidence—without substituting a manual correction for receiving, counts, transfers, sales, or returns.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Inventory → Adjustments uses the Arrow Up Down icon. Posting changes stock immediately and can drive quantity below zero because the adjustment operation does not enable negative-stock prevention. Reason Increase/Decrease is descriptive and does not enforce the entered quantity sign. Multi-line posting runs sequentially rather than as one transaction, so earlier lines can succeed before a later error. Count first, make the smallest supported correction, and verify every line.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Adjustments, identified by the Arrow Up Down icon. Start by reviewing history for the intended period and location so you do not duplicate an earlier correction.",
        "Choose 14 days, 30 days, 90 days, or 1 year. Custom uses its range only after both Start date and End date are selected; until then it falls back to 14 days. The timestamps sent to the query use the browser’s start/end of day converted to ISO.",
        "Use Search everything to filter the already loaded result by product name/SKU, variant name, reason, performer, performer role, notes, location, or quantity text. The history query loads at most 500 newest matching rows, so the displayed count is not proof that no older matching records exist.",
        "Use the Location filter carefully. Exactly one selected location is sent to the server query. Zero or multiple selected locations currently omit the location condition and therefore show all locations; do not interpret a multi-selection as an intersection/union limited to those choices.",
        "Expand an adjustment to inspect Stock before, Stock after, performer, captured role, reason and direction arrow, exact timestamp, product SKU, location, and notes. The adjustment_id URL parameter can deep-link the expanded row but does not change the underlying date/location query.",
        "Choose Reasons before posting. Create a stable required name and classify it as Decrease or Increase. The type labels audit intent and appears with the history record; the posting form does not force a negative quantity for Decrease or positive quantity for Increase.",
        "Rename a reason with Pencil and confirm it. Renaming changes the shared reason label displayed for historical adjustment references. Turn its switch off to hide it from new-adjustment selection while preserving existing records; there is no hard-delete control in this manager.",
        "Choose New Adjustment. Confirm the Location first. It defaults to the currently selected location when available; changing it refreshes each added line’s displayed stock for the new location. Recheck every line after a location change.",
        "Search by name or SKU and add the exact product. For a variable product, select one or more exact variants. Variant starting stock comes only from variant_location_stock and deliberately does not fall back to the product rollup; a missing row appears as zero.",
        "Do not add the same variant twice in one dialog; already-added variant IDs are disabled in the variant picker. Non-variant products use product_location_stock. Confirm name, variant, SKU, and current stock before entering a change.",
        "Enter Qty Change as a signed whole-unit delta: positive adds units and negative removes units. The code uses parseInt, so decimal input is truncated rather than treated as a fractional inventory quantity. Zero/blank/invalid lines are excluded from posting and shown in the ready count.",
        "Read the live Stock current → projected value. The operation permits a projected negative quantity because preventNegative is false. Do not post below zero unless the approved correction explicitly requires negative stock and downstream Sell/replenishment/reporting effects have been reviewed.",
        "Choose one required Reason for the entire adjustment batch. Make its direction match every line’s sign manually; the UI does not validate the match and one batch cannot accurately explain mixed positive and negative causes. Split different causes/directions into separate adjustments.",
        "If supplier price lists are available, choose the Cost basis for each applicable line. The first supplier price list becomes the initial unit cost even when no explicit selectedPriceListId is stored; selecting a list also attempts to update that list-specific stock after the main movement. Confirm valuation policy before choosing.",
        "Enter one Notes value for the entire batch. Blank notes are persisted as “No additional context given.” Use a clear, approved explanation with count/evidence reference; there is no effective per-line note editor despite the internal line shape having a notes field.",
        "Read “<n> of <m> items ready.” Only ready nonzero integer-parsed lines post. Remove unintended lines before submission; invalid/zero lines remain visible but are silently omitted from the posted count.",
        "Choose Apply <n> Adjustments once. Lines are processed one by one through the inventory movement operation, which updates location/variant stock and writes movement plus adjustment evidence. The batch is not atomic: if line 3 fails, lines 1–2 are not automatically rolled back.",
        "For a selected supplier price list, a separate product/variant price-list stock upsert follows the main movement. The current caller does not inspect the returned upsert error, so the dialog can continue without surfacing a failed price-list-stock alignment. Verify both general stock and the selected price-list stock.",
        "Wait for the success or error message. A success count reflects valid lines processed by the loop; after any error, inspect history and Movement Ledger line by line before retrying because partial prior success is possible. Never repost the entire batch blindly.",
        "Verify each posted row in Adjustments: exact product/variant, location, signed quantity, before/after, user/role, reason, and notes. Then verify Inventory current stock and Inventory → Movements adjustment evidence.",
        "Use Purchase Orders/Receiving for supplier receipts, Supplier returns for return-to-vendor work, Transfers for location movement, Counts for physical count reconciliation, Sell/Returns for customer transactions, and opening imports for approved migration. A manual adjustment should explain a variance, not erase the workflow that created it.",
        "If a correction itself was wrong, do not edit/delete the audit row—the screen has no such action. Perform an approved equal-and-opposite adjustment with a new note referencing the mistaken record, then verify the net movement and accounting/valuation effects.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully rendered /inventory/adjustments empty state at 1440×900 for the selected date range. It exposes the actual Arrow Up Down icon, Reasons/New Adjustment controls, date/search/location filters, and zero results; no adjustment, product, cost, user, customer, or stock data was changed or exposed."
      ],
      "controls": [
        {
          "name": "Arrow Up Down icon",
          "description": "Exact Inventory navigation and empty-state icon for Adjustments."
        },
        {
          "name": "Date presets",
          "description": "14 days, 30 days, 90 days, 1 year, or Custom."
        },
        {
          "name": "Custom range fallback",
          "description": "Uses 14 days until both dates are selected."
        },
        {
          "name": "Search everything",
          "description": "Client-side search across the loaded adjustment rows."
        },
        {
          "name": "500-row limit",
          "description": "Newest matching server rows only; displayed count may omit older history."
        },
        {
          "name": "Location filter caveat",
          "description": "Only exactly one selected ID filters; zero or multiple currently mean all locations."
        },
        {
          "name": "adjustment_id",
          "description": "URL-controlled row expansion, not a server lookup override."
        },
        {
          "name": "Reasons",
          "description": "Create, rename, enable, or disable shared adjustment reasons."
        },
        {
          "name": "Increase / Decrease reason",
          "description": "Descriptive audit type; does not enforce quantity sign."
        },
        {
          "name": "Disabled reason",
          "description": "Hidden from new selection while retained on existing records."
        },
        {
          "name": "New Adjustment",
          "description": "Location-scoped multi-line stock correction dialog."
        },
        {
          "name": "Variant stock",
          "description": "Reads variant_location_stock only, with missing row treated as zero."
        },
        {
          "name": "Qty Change",
          "description": "Signed integer delta; decimal text is truncated by parseInt."
        },
        {
          "name": "Stock preview",
          "description": "Current stock plus parsed delta; negative projected stock is allowed."
        },
        {
          "name": "Ready count",
          "description": "Only nonzero integer-parsed lines will post."
        },
        {
          "name": "Cost basis",
          "description": "Optional supplier price-list supply price used as movement unit cost."
        },
        {
          "name": "Shared Notes",
          "description": "One batch note applied to every posted line; blank becomes a fixed fallback."
        },
        {
          "name": "Apply Adjustments",
          "description": "Sequential per-line posting, not an atomic batch."
        },
        {
          "name": "Inventory movement",
          "description": "Writes the stock change and movement; writeAdjustment also records adjustment audit evidence."
        },
        {
          "name": "Price-list stock follow-up",
          "description": "Separate upsert after main movement whose returned error is not checked by this caller."
        },
        {
          "name": "Expanded detail",
          "description": "Before/after, performer/role, reason, date, SKU, location, and notes."
        },
        {
          "name": "No edit/delete",
          "description": "Posted adjustment history is immutable from this screen; correct with approved opposite evidence."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant loaded empty Adjustments capture; no stock or identity data exposed and no mutation performed."
        }
      ],
      "expectedResult": "The selected product and variant quantity changes by the intended amount at the intended location, and the named reason appears in inventory activity.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/inventory-adjustments.png",
        "alt": "Harbor & Hearth Inventory Adjustments screen showing date filters, search, locations, reasons, and the New Adjustment action in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "location-transfers",
      "url": "https://platform.getcentri.com/centripos/location-transfers",
      "title": "Transfer inventory between locations",
      "summary": "Request, route, send, physically receive, reconcile, print, recall, and—only when authorized—rebalance a transfer between CentriPOS locations.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Inventory → Transfers uses the exact ArrowLeftRight icon. The operational states are Draft, Requested, Sent, Received, and Cancelled; Approved and Shipped can appear on older records. Sending deducts the requested quantity from the source with negative-stock prevention. Receiving defaults each line to the amount sent, posts the counted quantity to the destination, and returns a shortfall to the source. Transfer creation, sending, receiving, continuation, recall, and deletion each use multiple sequential writes rather than one all-or-nothing transaction, so verify source, destination, and movement evidence before retrying after an error.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Transfers, identified by the ArrowLeftRight icon. Confirm the active business and your location access. The list is server-filtered and paged; Load more shows how many currently loaded rows are visible out of the total.",
        "Use All, Drafts, Pending Approval, In Transit, or Completed. Filter by access-scoped locations, exact source store, destination store, product/variant/SKU search, and From/Through dates. Clear resets those filters. Expand a row to see active product/variant, SKU, Requested, Sent, and Received quantities without opening it; choose the row or transfer number for full detail.",
        "Read the list carefully: Created is requested_at, Requested By is the creator, From is the inventory source, To is the requesting/destination location, and Products versus Items means distinct active lines versus summed requested units. Recalled lines are excluded from the expanded active-line list.",
        "Choose New Transfer. To begins with the current operating location when available; From begins blank. Choose two different locations, then verify which site will lose stock and which will receive it. Optionally set the expected transfer date, route the request to an eligible source-location manager, and enter notes.",
        "Add the exact product or variant and enter a whole-unit requested quantity. Review displayed source stock, name, variant, and SKU. Import from sale can add selected unfulfilled sale lines for the destination, preserve their fulfillment link, add an Imported from sale note, and auto-save when both locations are valid. It does not complete the fulfillment.",
        "A new valid draft auto-saves after changes. Save Draft explicitly when the request is not ready; Submit Request changes it to Requested. Creation writes the header and then line rows. Editing an existing Draft or Requested transfer updates the header, deletes all old item rows, and inserts replacements; those writes are not atomic, so an error can leave missing or replaced line data. Reopen and inspect every line before continuing.",
        "Print Slip is available after a transfer record exists. It includes transfer identity/status, dates, source/destination, request/sent/received people when present, tracking/notes, and requested/sent/received line quantities. If the browser blocks the print window, allow pop-ups for CentriPOS and retry printing only.",
        "A Draft can be edited or deleted. A Requested transfer can still be edited, cancelled, or sent. Cancel marks the transfer Cancelled without a stock movement. Confirm that no one has begun physical shipment before cancellation; the current cancellation update does not perform a status compare-and-set or inspect its returned error.",
        "At the source, open the exact Requested transfer and choose Send. Review Expected transfer date, optional Tracking number, and Notes, then choose Approve & Send once. The status compare-and-set prevents two senders from both entering the stock loop.",
        "Sending first claims the transfer as Sent, records approver/shipper/timestamps and notes, then processes each active line sequentially: quantity_sent becomes quantity_requested and a transfer-out movement deducts the source with prevent-negative enabled. This is not atomic. If stock is insufficient or a later line fails, the transfer may already say Sent and earlier lines may already be deducted. Stop and reconcile rather than pressing Send again.",
        "At the destination, open a Sent transfer and choose Receive. Older Approved or Shipped records also expose Receive. Actual received date defaults to today; after a recall it defaults to the original received date, and inventory movements use the selected effective date. Use the true physical receipt date.",
        "Every unreceived active line starts Counted at Expected—the sent quantity—not zero. Physically count every line and change Counted to the nonnegative whole number actually present. The input permits an overage above Expected. Review Match, Over, or Short for each line.",
        "Optionally attach each line to one eligible destination fulfillment with the exact same product and variant from up to 100 recent completed/layaway sale lines in pending, sourcing-needed, ordered, or awaiting-receipt status. A fulfillment can be attached to only one transfer line in the dialog. Receipt later marks the linked sale line received and records the source location, but a failed follow-up update is not surfaced by this caller; verify fulfillment separately.",
        "Choose Confirm Receipt. If any Counted amount differs, CentriPOS first opens Discrepancy Detected. Review Expected, Counted, and Diff. A short quantity is returned to source stock. For a short receipt choose Create continuation transfer for remaining or Close as-is and accept short receipt. An overage adds the full counted amount to destination without a source-side offset, so investigate and obtain authorization before accepting an overage.",
        "Choose Receive Anyway only when every discrepancy and remainder choice is correct. Receiving first claims the transfer as Received, then sequentially updates each line, posts counted transfer-in at destination, updates an attached fulfillment, and returns each shortfall to source. A continuation is created last when chosen. These writes are not one transaction and several updates do not check returned errors.",
        "After receipt, verify the Created, Sent, and Received cards and notes; expand/reopen every line; reconcile source deduction, destination addition, any shortfall return, continuation request, linked fulfillment, and source-linked Inventory Movements. A success toast does not prove every follow-up write completed.",
        "A continuation created for a short receipt is a new Requested transfer using the root transfer number plus the next numeric suffix. It contains only the outstanding quantities and preserves matching sale-line links. The original transfer remains Received. Owners can also choose Continue Backorder later when a received transfer still has remaining sent-versus-received units.",
        "Owners and super admins can choose Recall Receipt on a Received transfer. Enter a required reason and select at least one line with received quantity. With no replacement lines, receipt stock is reversed at destination, short-return effects are reversed where applicable, selected line receipt quantities reset, the transfer returns to Sent, and those lines can be received again.",
        "Recall Receipt can also swap selected received lines for replacement products/variants. In that mode, the selected original receipt is removed from destination and restored to source, replacements are inserted as already sent and received, source/destination replacement movements post, and the transfer remains Received. This is a high-impact sequential correction, not a simple label edit; reconcile every movement and the recall-history record.",
        "Delete & Rebalance is owner-level destructive removal for a Received transfer. It sequentially subtracts each nonrecalled received quantity from destination, restores each sent quantity to source, then deletes all item rows and the transfer. Its delete and movement calls are not protected by one transaction and several returned errors are unchecked. Use only after a documented approval and verify that both stock planes and movement evidence balance.",
        "Do not use Delete & Rebalance as an ordinary correction when Recall Receipt can preserve the transfer and its recall audit. Never delete/rebalance, recall, receive, or resend merely because the UI state appears stale. Record transfer ID, status, source/destination, line IDs, quantities, timestamps, and error message before support escalation.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Transfers route remained in a loading state during the extended capture window, so no screenshot was retained or replaced with a different inventory screen."
      ],
      "controls": [
        {
          "name": "ArrowLeftRight icon",
          "description": "Exact CentriPOS Inventory navigation and empty-state icon for Transfers."
        },
        {
          "name": "All / Drafts / Pending Approval / In Transit / Completed",
          "description": "Server-side transfer-state views."
        },
        {
          "name": "Access-scoped location filter",
          "description": "Restricts results to selected visible locations."
        },
        {
          "name": "Source / destination filters",
          "description": "Exact From and To location filters."
        },
        {
          "name": "Product search",
          "description": "Server-side product, variant, or SKU search after a short debounce."
        },
        {
          "name": "From / Through dates",
          "description": "Server-side transfer date range."
        },
        {
          "name": "Products / Items",
          "description": "Active line count versus summed requested units."
        },
        {
          "name": "Draft",
          "description": "Open transfer; can auto-save, be edited, submitted, printed, or deleted."
        },
        {
          "name": "Requested",
          "description": "Awaiting source action; can be edited, cancelled, printed, or sent."
        },
        {
          "name": "Sent",
          "description": "Source quantities have been deducted and the destination can receive."
        },
        {
          "name": "Received",
          "description": "Receipt has been claimed and counted destination movements processed."
        },
        {
          "name": "Cancelled",
          "description": "Requested transfer marked cancelled without stock posting."
        },
        {
          "name": "Approved / Shipped",
          "description": "Legacy states that remain receivable."
        },
        {
          "name": "Import from sale",
          "description": "Adds eligible unfulfilled destination-sale lines and retains sale-line linkage."
        },
        {
          "name": "Print Slip",
          "description": "Transfer handoff with identity, route, people, notes/tracking, and requested/sent/received lines."
        },
        {
          "name": "Approve & Send",
          "description": "Compare-and-set status claim followed by sequential source deductions with negative prevention."
        },
        {
          "name": "Expected",
          "description": "Quantity sent or, for legacy/unset sent data, quantity requested."
        },
        {
          "name": "Counted",
          "description": "Nonnegative whole-unit physical receipt; initially prefilled to Expected."
        },
        {
          "name": "Fulfillment",
          "description": "Optional exact product/variant destination sale-line attachment."
        },
        {
          "name": "Match / Over / Short",
          "description": "Counted minus Expected classification."
        },
        {
          "name": "Actual received date",
          "description": "Effective date used for receipt inventory movements."
        },
        {
          "name": "Discrepancy Detected",
          "description": "Mandatory review when any Counted value differs from Expected."
        },
        {
          "name": "Shortfall return",
          "description": "Expected minus Counted added back to source."
        },
        {
          "name": "Create continuation transfer",
          "description": "New Requested suffix transfer for remaining short units."
        },
        {
          "name": "Close as-is",
          "description": "Receives current count and closes without a continuation."
        },
        {
          "name": "Continue Backorder",
          "description": "Owner action on an already Received transfer with remaining units."
        },
        {
          "name": "Recall Receipt",
          "description": "Owner/super-admin line-level reversal or replacement workflow with required reason and recall history."
        },
        {
          "name": "Delete & Rebalance",
          "description": "Owner-level destructive stock reversal followed by transfer deletion."
        },
        {
          "name": "Multi-write boundary",
          "description": "Transfer operations are sequential and not one all-or-nothing transaction."
        },
        {
          "name": "No public screenshot",
          "description": "Rejected real loading-state capture; no substituted or fabricated image."
        }
      ],
      "expectedResult": "The exact transfer, active lines, source, destination, requested/sent/counted quantities, effective dates, people, notes, tracking, fulfillment links, and status sequence are verified; source deductions, destination receipts, shortfall returns or overages, continuation records, recalls/replacements, and movement evidence reconcile line by line; and a partial multi-write result is investigated before any resend, rereceipt, recall, or deletion.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "purchase-orders",
      "url": "https://platform.getcentri.com/centripos/purchase-orders",
      "title": "Create and manage a purchase order",
      "summary": "Build, price, send, track, receive, reconcile, and correct supplier orders and customer-linked demand without losing the source evidence behind inventory or fulfillment.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Inventory",
      "introduction": "Inventory → Purchase Orders uses the exact FileText icon. Draft and legacy Open both display as Draft; operational states also include Sent, In Transit, Partial, Received, and Cancelled. A PO can alter supplier commitments, receiving cost, average/last inventory cost, location distribution requests, linked sale fulfillment, customer shipment notices, and external accounting references. Saving replaces line/distribution data through a database operation, but the surrounding PO, shipment, email, receive, continuation, and recall work spans multiple writes. Verify each affected surface before retrying after an error.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Purchase Orders, identified by the FileText icon. The header states how many orders are loaded and whether more are available. Load more expands the current server result; sorting applies to the loaded list, so do not treat a partial loaded sort as the complete historical order.",
        "Search matches PO number, supplier, location, supplier invoice, tracking, internal/delivery notes, linked receipt/customer contact, product, variant, SKU, supplier code, and line note. Matching evidence appears beneath a result. Filters cover Drafts, Sent, In Transit, Partial, Received, Cancelled, visible locations, supplier, Created range, and Due range. Clear removes the active filters.",
        "Sort by PO #, Supplier, Location, Status, Date, Items, or Total. Expand a row for supplier/location/status, linked fulfillment, line details, shipments, receives, QBO links when attached, and Email/Receive shortcuts. Choose the row for the full editor; the list’s Email shortcut opens that PO with the email action.",
        "Choose New PO. Location and at least one product are required; supplier is technically optional in the save validation, but sending a supplier order without an identified vendor is operationally ambiguous. Enter or accept a generated location-scoped PO number. A manually entered PO number must be unique within the tenant.",
        "Set receiving Location, Supplier, expected delivery, delivery appointment, supplier invoice, tracking details, internal Notes, Delivery notes, and the intended ship-to presentation. A custom ship-to address changes the printed/emailed delivery destination while inventory still receives into the selected CentriPOS Location. Verify those two destinations separately.",
        "Add the exact standard product or variant. Confirm product/variant, SKU, supplier code, ordered whole units, units-per-pack/packaging context, unit cost, price source, and linked sale line when present. Use Product quick view and supplier price evidence when identity or cost is uncertain.",
        "Use Suggested Orders only on Draft/Open and after choosing a location. Use Find Customer Demand on Draft/Open, Sent, or In Transit to add eligible customer-linked demand. A PO can source multiple receipts through line-level sale links; inspect receipt/customer, fulfillment type/status/date, destination, and quantity before removing or redirecting a line.",
        "For planned post-receipt distribution, add destination locations and quantities on each line. These allocations do not move stock while drafting. During receiving, CentriPOS proportionally rounds the received quantity into new Requested location transfers for non-receiving destinations; verify the generated transfer lines because rounding and follow-up insert failures can create differences.",
        "Review item subtotal, freight, convenience fee, surcharge, surcharge-eligible lines, and grand total. Percentage and dollar fees behave differently. Shared freight/convenience contributes to landed unit cost; line surcharge eligibility/rules affect applicable cost. A Received PO recalculates financial totals on received quantities, while earlier states use ordered quantities.",
        "A supplier fee rule can auto-apply by category, tag, or brand. Saving a current rule requires a supplier, positive fee, and at least one explicit scope (including an intentional All option). Turning off auto-apply affects future POs; deleting soft-deletes the rule. Confirm the rule and every eligible line instead of assuming all merchandise shares one surcharge.",
        "Choose Save while preparation is incomplete. New-PO save creates the header, atomically replaces its item/distribution set through the dedicated database function, and then saves shipments. Existing save updates the header first, replaces items/distributions, then replaces shipments. These surrounding writes are not one transaction; reopen the PO and verify header, lines, distributions, and shipments after any error.",
        "Cancel Changes appears only with unsaved changes and reloads the page. It discards the current browser edits rather than reversing already saved data. Header actions such as Mark as Sent, Receive, Email, Print, QBO, and cancellation are disabled until changes are saved or cancelled.",
        "Choose Mark as Sent only after independently communicating the reviewed order; it changes PO status and sent timestamp but does not itself email the vendor. Email Vendor invokes the actual supplier communication. Conversely, a successful vendor email changes a Draft/Open PO to Sent after sending. If the email succeeds but the status update fails, the vendor may still have received it—check the communication audit before resending.",
        "In Email Vendor, review comma-separated To and CC addresses. Primary supplier email and supplier contacts are suggested, with contacts marked CC on PO routed to CC. Edit the message shown at the top; delivery notes remain a separate instruction box in the email/PDF. Send Email once, then inspect the audit for recipients, subject, provider, provider message ID, sender/location, Sent or Failed status, and error.",
        "Print PO creates the branded printable order and can include or omit Costs. It includes supplier/store/ship-to, dates, invoice/tracking, linked fulfillment, line identity/ordered/received quantities, financial totals, delivery notes, preparer/approver, and printer identity as supported. The financial line quantity is ordered until status is Received, then received. Allow pop-ups if blocked.",
        "Maintain Shipment records with carrier, tracking number/URL, status, store or customer destination, inventory handling, estimated/delivered dates, notes, and allocated PO lines. Saving shipments first deletes existing shipment rows and recreates the nonblank set sequentially; it is not an incremental atomic update. Verify shipment IDs, allocations, and destination after saving.",
        "Customer shipment notice is available for a saved, unchanged shipment linked to customer fulfillment and requires tracking number or URL. Email needs a destination and message. SMS needs a phone, message, staff-confirmed transactional consent, and the enforced length budget; CentriPOS adds the tracking link and STOP language. Check communication audit/delivery evidence rather than equating function success with customer receipt.",
        "Choose In Transit from Sent after shipment has actually departed; it saves the PO with shipped timestamp. Receive is available from Sent, In Transit, or Partial. The detailed physical count, barcode/case-pack rules, short choices, attestation, sequential inventory writes, and recall caveats are documented in Receive inventory.",
        "For a short PO receipt, Back-order remaining leaves Partial. A Partial PO can Receive Remaining, Close As-Is on received/payable quantities, or Close + Continue to create a linked suffix PO for the remainder. A Received PO that still contains deliberately closed short lines can later expose Continue Backorder. Verify received and payable totals on both original and continuation.",
        "Receiving applies landed cost per line, updates received quantity and inventory sequentially, then attempts average/last cost updates, PO status/totals, continuation, and distribution transfers. Several calls do not inspect returned errors. After every receipt verify line quantities, destination stock, Inventory Movements, average/last cost, PO subtotal/total, status, linked fulfillment, continuation, and generated transfers.",
        "Cancel PO is available only on saved Draft/Open/Sent records with no received quantity. It requires a reason and appends the actor/time/reason to Notes while setting Cancelled. It does not reverse supplier communication or shipment activity; confirm those external obligations separately.",
        "Recall is available on Received or Partial and requires a reason. It sequentially deducts every received line from the receiving location, resets all PO line received quantities to zero, returns status to Sent, clears received_at, and records recall history. It does not selectively recall one line. Reconcile all line movements and costs before re-receiving.",
        "View QBO PO and View QBO Bill appear only when corresponding external URLs are attached. Their presence is evidence of a link, not proof that CentriPOS lines, receipts, shipment totals, and the accounting document currently reconcile. Compare identifiers and totals in both systems.",
        "For discrepancies, preserve PO ID/number, tenant/location, supplier, status, line IDs and source sale-line IDs, ordered/received quantities, landed-cost inputs, distribution and shipment allocations, audit message ID, recall history, QBO links, and the exact error. Do not repeat Email, Receive, Recall, or Save until the existing writes are inspected.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Purchase Orders screen retained an active loading indicator after the extended inspection window, so the capture was rejected rather than represented as a loaded list or replaced with another screen."
      ],
      "controls": [
        {
          "name": "FileText icon",
          "description": "Exact CentriPOS Inventory navigation, Purchase Orders list, and empty-state icon."
        },
        {
          "name": "Loaded count / more available",
          "description": "Current server pages in the browser; additional rows require Load more."
        },
        {
          "name": "Search evidence",
          "description": "Matching PO, supplier, location, invoice/tracking, notes, receipt/customer, product/variant/SKU, supplier code, or line data."
        },
        {
          "name": "Status filter",
          "description": "Drafts, Sent, In Transit, Partial, Received, or Cancelled."
        },
        {
          "name": "Created / Due",
          "description": "Independent date-range filters."
        },
        {
          "name": "Loaded-list sorting",
          "description": "PO #, supplier, location, status, date, items, or total across rows currently loaded."
        },
        {
          "name": "New PO",
          "description": "Creates a location-scoped supplier-order draft."
        },
        {
          "name": "PO number",
          "description": "Generated or manual tenant-unique business identifier; locked after receipt begins."
        },
        {
          "name": "Location",
          "description": "CentriPOS location that receives inventory even when printed ship-to is customized."
        },
        {
          "name": "Supplier",
          "description": "Vendor and suggested email/contact source; save validation does not require it."
        },
        {
          "name": "Internal Notes / Delivery notes",
          "description": "Staff context versus separately printed/emailed delivery instructions."
        },
        {
          "name": "Suggested Orders",
          "description": "Draft/Open location-based sourcing suggestions."
        },
        {
          "name": "Find Customer Demand",
          "description": "Eligible customer fulfillment demand linkable to PO lines."
        },
        {
          "name": "Linked fulfillment",
          "description": "Sale-line connection retained through PO, shipments, receiving, and customer notice workflow."
        },
        {
          "name": "Distribution",
          "description": "Planned proportional post-receipt Requested transfers to other locations."
        },
        {
          "name": "Financial quantity mode",
          "description": "Ordered quantities until Received; received quantities after closing as Received."
        },
        {
          "name": "Freight / convenience / surcharge",
          "description": "Shared and eligible fees affecting PO total and landed cost."
        },
        {
          "name": "Supplier fee rule",
          "description": "Scoped category/tag/brand auto-apply rule with enable/soft-delete controls."
        },
        {
          "name": "Save",
          "description": "Header, atomic line/distribution replacement RPC, then sequential shipment replacement."
        },
        {
          "name": "Cancel Changes",
          "description": "Reloads and discards unsaved browser edits."
        },
        {
          "name": "Mark as Sent",
          "description": "Status/timestamp change only; not vendor communication."
        },
        {
          "name": "Email Vendor",
          "description": "Sends the PO and then marks Draft/Open Sent."
        },
        {
          "name": "Communication audit",
          "description": "Recipients, subject, provider/status/message ID, sender/location, and error evidence."
        },
        {
          "name": "Print PO / Costs",
          "description": "Branded printable purchase order with optional financial amounts."
        },
        {
          "name": "Shipment record",
          "description": "Carrier/tracking/status/destination/stock handling/dates/notes and allocated PO lines."
        },
        {
          "name": "Customer shipment notice",
          "description": "Saved tracking-linked email/SMS with consent and message-length rules."
        },
        {
          "name": "In Transit",
          "description": "Sent PO marked shipped; still eligible to receive."
        },
        {
          "name": "Receive / Receive Remaining",
          "description": "Physical posting from Sent, In Transit, or Partial."
        },
        {
          "name": "Close As-Is",
          "description": "Closes a Partial PO on received/payable quantities."
        },
        {
          "name": "Close + Continue",
          "description": "Closes and creates a linked suffix PO for remaining units."
        },
        {
          "name": "Continue Backorder",
          "description": "Creates a continuation from a Received PO with closed remaining quantities."
        },
        {
          "name": "Cancel PO",
          "description": "Reason-required cancellation before any receipt."
        },
        {
          "name": "Recall",
          "description": "All-line received-stock reversal that resets the PO to Sent and records history."
        },
        {
          "name": "View QBO PO / Bill",
          "description": "External links when attached; not reconciliation proof."
        },
        {
          "name": "Multi-write boundary",
          "description": "PO save, shipments, communications, receiving, distribution, continuation, and recall are not one transaction."
        },
        {
          "name": "No public screenshot",
          "description": "Rejected real loading-state capture; no substituted or fabricated image."
        }
      ],
      "expectedResult": "The exact PO, supplier, CentriPOS receiving location, printed ship-to, lines, variants/SKUs/supplier codes, price sources, ordered/received quantities, landed-cost fees/rules, customer fulfillment links, distributions, shipments, communication audit, status, continuation/recall history, QBO references, and source-linked inventory movements reconcile; any partial multi-write or uncertain email/receipt result is inspected before repeating an action.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "vendors",
      "url": "https://platform.getcentri.com/centripos/vendors",
      "title": "Manage suppliers and purchasing contacts",
      "summary": "Maintain the purchasing identity, email recipients, sub-contacts, address, default markup, surcharge rules, QuickBooks link, and price-list relationship behind CentriPOS supplier workflows.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Products",
      "introduction": "Products → Suppliers uses the exact Truck icon. A supplier is a purchasing/vendor record, not a retail customer. The list exposes only Supplier, Description, Default markup, and row actions—it does not display contact or email columns. Primary and sub-contact email settings prefill Purchase Order recipients, but the PO sender can edit them before sending. Supplier save updates the supplier first, then deletes and recreates all sub-contacts; this is not a single transaction, so verify contacts after any error.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Products → Suppliers, identified by the Truck icon. The alphabetical tenant list has Supplier, Description, Default markup, edit, and delete columns. There is no list search, filter, pagination, contact column, or email column on this component.",
        "Wait for the loader to finish. The supplier fetch does not surface its returned error; a failed query can therefore look like No suppliers yet. Refresh and compare a known product/PO supplier before concluding the tenant has none.",
        "Choose Add supplier, a supplier row, or the pencil. Supplier name is the only field validated as required by this form. Enter a distinct purchasing identity and optional Description. Default markup % is displayed in the list and stored for supported supplier-based pricing behavior; confirm policy before changing it.",
        "Complete Primary corporate contact: first name, last name, company, primary corporate email, phone, mobile, fax, and website. On a PO, the current supplier email is the first suggested To recipient. It is not automatically protected from editing or guaranteed to be the person who should receive every order.",
        "Use Sub-contacts for a sales representative, buyer, accounts-payable contact, or email-only recipient. Each retained row can store name, title, email, phone, mobile, notes, and CC this contact on PO emails. Completely blank rows are dropped during save.",
        "Enable CC this contact on PO emails only when the address should be prefilled in CC for every PO email using this supplier. CentriPOS blocks supplier save if a retained CC-enabled sub-contact has no email. In the PO dialog, non-CC contact emails are suggested in To and CC-enabled contacts in CC; always review the final recipients.",
        "Complete Street, Street 2, City, State, ZIP code, and Country. These fields support the supplier/vendor identity and printed/accounting context; they do not change the CentriPOS receiving location or a PO’s custom ship-to destination.",
        "On an existing supplier, review Account fee / surcharge rules. Only nondeleted rules for this supplier appear, newest first. Scope is the listed Categories, Tags, and Brands; no scope IDs means All products for this supplier. The badge says active but its number is the count of nondeleted rules, including rules whose Auto apply switch is off.",
        "Toggle Auto apply to affect future PO application. Delete soft-deletes the rule and turns auto-apply off; it does not erase prior PO fee evidence. Rules are created from the Purchase Order fee-rule controls, not from a create-rule form in this supplier dialog.",
        "Review QuickBooks Online vendor. View on QBO appears only when an external vendor URL is already attached. When no link exists, this dialog only explains that supplier sync/matching can create one; it does not provide a manual Match or Create vendor button. Use the QuickBooks integration workflow and verify identity before making accounting changes.",
        "Use Manage vendor price lists to enter the separate supplier-price-list workflow. Supplier identity alone does not assign products, supplier codes, supply costs, stock, or PO price sources. Verify product-supplier and price-list entries independently.",
        "Choose Add supplier or Save once. The supplier row is inserted/updated first. CentriPOS then deletes every existing sub-contact for that supplier and inserts the current nonblank draft rows in order. Those writes are not atomic: if contact deletion or reinsertion fails, the supplier fields can already be saved and old contacts can already be gone. Reopen the supplier and verify every recipient before emailing a PO.",
        "Surcharge rule toggles/deletes are immediate independent writes; closing the supplier dialog does not undo them. View on QBO and Manage vendor price lists navigate away from the identity form. Save pending supplier/contact edits before leaving when they must be retained.",
        "The trash icon in the supplier list immediately issues a hard delete with no application confirmation dialog and no dependency preflight. Database relationships may block it, or a successful delete may remove the list record immediately. Do not test this control. First inspect products, product-supplier rows, price lists, POs, direct receipts, returns, rules, and accounting linkage, then obtain authorized deletion approval.",
        "After any create/edit, reopen the supplier and confirm exact name, markup, corporate contact, To/CC sub-contacts/order, address, rule count/scope/auto-apply, QBO link, and price-list navigation. Then open a draft test PO only when authorized and verify suggested To/CC recipients without sending.",
        "Use the real Amelia Grant Harbor & Hearth screenshot for list orientation. It is the approved loaded `/catalog/suppliers` capture at 1440×900 and exposes supplier names plus public catalog metadata only; no vendor contacts, credentials, costs, QBO record, rule dialog, or mutation is shown."
      ],
      "controls": [
        {
          "name": "Truck icon",
          "description": "Exact CentriPOS Products navigation icon for Suppliers."
        },
        {
          "name": "Alphabetical supplier list",
          "description": "Supplier, Description, Default markup, and row actions only."
        },
        {
          "name": "Silent list-query failure",
          "description": "Returned fetch error is not surfaced and can resemble an empty tenant."
        },
        {
          "name": "Supplier name",
          "description": "Only form-validated required identity."
        },
        {
          "name": "Default markup %",
          "description": "Stored supplier-level starting markup used by supported pricing workflows."
        },
        {
          "name": "Primary corporate email",
          "description": "First suggested Purchase Order To address; still review before sending."
        },
        {
          "name": "Sub-contact",
          "description": "Optional name/title/email/phone/mobile/notes/CC recipient row."
        },
        {
          "name": "Blank contact row",
          "description": "Dropped during normalization and not saved."
        },
        {
          "name": "CC this contact on PO emails",
          "description": "Prefills PO CC and requires a contact email."
        },
        {
          "name": "Address",
          "description": "Supplier identity fields; not PO receiving or custom ship-to control."
        },
        {
          "name": "Account fee / surcharge rules",
          "description": "Nondeleted supplier PO fee rules shown newest first."
        },
        {
          "name": "Rule count caveat",
          "description": "Badge counts nondeleted rules even when auto-apply is off."
        },
        {
          "name": "Auto apply",
          "description": "Immediate future-PO rule toggle."
        },
        {
          "name": "Delete rule",
          "description": "Immediate soft-delete and auto-apply disable; prior PO evidence remains."
        },
        {
          "name": "QuickBooks Online vendor",
          "description": "Read-only external link state in this dialog."
        },
        {
          "name": "Manage vendor price lists",
          "description": "Separate supplier-specific product/SKU/cost workflow."
        },
        {
          "name": "Supplier/contact save boundary",
          "description": "Supplier first, then delete-all and reinsert contacts; not atomic."
        },
        {
          "name": "Delete supplier",
          "description": "Immediate hard-delete request with no UI confirmation or dependency preflight."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Approved real loaded Suppliers list with no sensitive contact/cost exposure or mutation."
        }
      ],
      "expectedResult": "The exact supplier identity, default markup, corporate contact, complete ordered To/CC sub-contact set, address, surcharge-rule scope/state, QBO link, and price-list relationship are reopened and verified; representative product and draft-PO selection behave as intended; and any partial supplier/contact replacement or deletion dependency is resolved before retrying.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-suppliers.png",
        "alt": "Real Harbor & Hearth Suppliers list showing supplier names, descriptions, default markup, and row actions in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "inventory-movements",
      "url": "https://platform.getcentri.com/centripos/inventory-movements",
      "title": "Trace Inventory in the Movement Ledger",
      "summary": "Use the read-only chronological evidence for sales, returns, exchanges, receiving, transfers, adjustments, counts, opening stock, fulfillment, and manual edits to explain exactly how location or variant stock changed.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Movements",
      "introduction": "Inventory → Movements uses the Activity icon. The page queries at most 500 newest matching movements, then applies product/SKU search in the browser. It is an evidence view, not an editor: no row can be changed, deleted, reversed, or opened to its source record here. Correct the originating workflow or post an approved counter-movement while preserving the audit trail.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Movements, identified by the Activity icon. Confirm the Movement Ledger has finished loading before interpreting a blank result.",
        "Choose 14 days, 30 days, 90 days, 6 months, or 1 year. Custom uses the selected range only after both Start date and End date exist; until then it falls back to 14 days. Day boundaries are created in the browser timezone and converted to ISO for the query.",
        "Choose All types or one exact movement type: Sale, Return, Exchange, PO Receive, Transfer In, Transfer Out, Adjustment, Count, Opening, Fulfillment, or Manual Edit. Unknown stored types can still appear under their raw name when All types is selected.",
        "Use the Location filter carefully. Exactly one selected location adds a server condition. Zero or multiple selected locations currently omit that condition and show all active-location movement results allowed by the data policy; do not read multi-selection as “only these locations.”",
        "The query returns the newest 500 records matching date, type, and single-location filters. Search product or SKU then filters only those loaded rows by product name/SKU or variant name/SKU. A zero result does not prove the product never moved—narrow the server filters or inspect authoritative data/reporting when older evidence matters.",
        "Read each collapsed row: product snapshot/current name, Deleted marker when the product relation is gone but a stored name remains, variant badge, displayed SKU, location, performer, type, signed quantity, stock before → stock after, time, and unit cost when greater than zero.",
        "Interpret the sign with the workflow. Positive increases stock and uses the up-right indicator; negative decreases stock and uses the down-right indicator. Do not assume a positive Return, PO Receive, or Transfer In is correct without confirming product, variant, location, source, and quantity.",
        "Expand the row to view Type, Source, Stock before/after, Unit cost, Performed by, captured Role when present, exact timestamp, current product SKU, Location, and Notes. movement_id in the URL only controls row expansion; it does not bypass date/type/location filters or fetch a missing row.",
        "Source is the stored source_type label, not a clickable document and not the source record ID. Use timestamp, product/variant, location, performer, notes, related receipts/POs/transfers/counts, and other module history to find the originating record.",
        "For Sale or Return evidence, open the relevant receipt and trace sale line, quantity, location/register session, return/exchange link, and payment/fulfillment state. Do not “fix” a sale movement with an unrelated manual edit merely to force today’s stock.",
        "For PO Receive, inspect the purchase order, receiving event, supplier/product/variant, destination location, quantity, and cost basis. Use an approved receiving correction or supplier-return workflow as appropriate.",
        "For Transfer Out/In, confirm both sides of the same location transfer, source/destination, shipment/receipt status, quantities, and timing. A single side without its counterpart requires investigation, not a duplicate transfer.",
        "For Adjustment, open Inventory → Adjustments and match its before/after, reason, user/role, note, product/variant, and location. Correct an erroneous posted adjustment with an approved opposite adjustment; do not erase movement evidence.",
        "For Count, inspect the corresponding physical inventory count, counted-versus-system quantities, posting user/time, and location. Recount or correct through the count workflow when supported.",
        "For Opening or Manual Edit, identify the authorized import/setup/edit event and its documentation. These types can establish or directly alter stock without a sale/receive/transfer, so preserve migration or administrative evidence.",
        "For Fulfillment, trace the sale line and fulfillment work to understand when operational handoff affected stock. Confirm the configured sale/fulfillment inventory policy before concluding that a timing difference is an error.",
        "Unit cost is displayed only when greater than zero and uses the tenant currency formatter. A blank dash is not evidence of a free item; inspect product/supplier valuation and the source record. The ledger itself does not calculate financial valuation or accounting entries.",
        "Deleted products can display a stored product name/SKU snapshot in the collapsed row with Deleted. The expanded current-SKU field can show a dash because the product relation is gone. Preserve the movement for historical explanation rather than recreating/deleting catalog records just to change the display.",
        "When investigating a current-stock discrepancy, reconcile a continuous chain: earliest trustworthy stock → every signed movement in time order → current location/variant stock. Account for the 500-row cap and filters; export/query authoritative records when the chain extends beyond this view.",
        "After correcting through the proper workflow, return to Movements and verify the new counter/source movement, signed quantity, before/after continuity, location, user, time, and notes. Confirm current Inventory and the originating module agree.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully rendered /inventory/movements empty state at 1440×900 for the selected range. It exposes the actual Activity icon, date/type/search/location controls, movement count, and zero results; no product, user, customer, cost, source, or stock data was exposed and no state changed."
      ],
      "controls": [
        {
          "name": "Activity icon",
          "description": "Exact Inventory navigation and empty-state icon for Movements."
        },
        {
          "name": "Date presets",
          "description": "14 days, 30 days, 90 days, 6 months, 1 year, or Custom."
        },
        {
          "name": "Custom fallback",
          "description": "Uses 14 days until both custom dates are selected."
        },
        {
          "name": "Movement type",
          "description": "Sale, Return, Exchange, PO Receive, Transfer In/Out, Adjustment, Count, Opening, Fulfillment, or Manual Edit."
        },
        {
          "name": "Single-location server filter",
          "description": "Applied only when exactly one location ID is selected."
        },
        {
          "name": "Multi-location caveat",
          "description": "Zero or multiple selected IDs currently omit location filtering."
        },
        {
          "name": "500-row cap",
          "description": "Newest server-filtered records; search and count cannot see older omitted rows."
        },
        {
          "name": "Product/SKU search",
          "description": "Client-side match across loaded product and variant name/SKU."
        },
        {
          "name": "Movement count",
          "description": "Count after client search within the capped query."
        },
        {
          "name": "Signed quantity",
          "description": "Positive adds, negative removes."
        },
        {
          "name": "Stock before → after",
          "description": "Persisted continuity evidence for the movement."
        },
        {
          "name": "Unit cost",
          "description": "Shown only when greater than zero; absence is not proof of zero economic cost."
        },
        {
          "name": "Deleted marker",
          "description": "Current product relation missing while stored snapshot identity remains."
        },
        {
          "name": "Expanded detail",
          "description": "Type/source label, before/after, unit cost, performer/role, exact time, SKU, location, notes."
        },
        {
          "name": "Source type",
          "description": "Text classification only; no source ID or clickable source record in this view."
        },
        {
          "name": "movement_id",
          "description": "URL expansion state, not a lookup bypass."
        },
        {
          "name": "Read-only ledger",
          "description": "No edit, delete, reverse, export, or source-open action in this component."
        },
        {
          "name": "No movements found",
          "description": "Completed result for current filters/cap, not proof of no historical movement."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant loaded empty Movement Ledger capture; no inventory or identity data exposed and no mutation."
        }
      ],
      "expectedResult": "The movement ledger row identifies the correct product, variant, location, quantity direction, reason, source document, user, and time for the stock change.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/inventory-movements.png",
        "alt": "Harbor & Hearth Movement Ledger in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "supplier-returns",
      "url": "https://platform.getcentri.com/centripos/supplier-returns",
      "title": "Create and verify a supplier return",
      "summary": "Record product physically leaving one location, deduct its stock immediately, preserve cost and movement evidence, and reconcile any connected QuickBooks vendor credit.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Supplier Returns",
      "introduction": "New Return is a posting action, not a saved preparation workflow. Choosing Create Return creates a return with Draft status and immediately applies a negative inventory movement for every entered line. The current customer screen does not provide a later Send/Post button, detail editor, status control, shipping fields, or cancellation reversal. Confirm physical units, location, variant, quantity, and cost before creating it.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Obtain the supplier’s return authorization outside CentriPOS as required by company policy. Physically isolate and count the units, identify exact variants/serial handling requirements, confirm which stock location owns them, and determine the approved unit cost and reason before opening the form.",
        "Go to Inventory → Supplier Returns. Review the existing table for a recent matching Date, Supplier, Location, Reason, item count, and Total Cost so the same physical return is not entered twice. The list is a summary; rows do not currently open an editable return detail screen.",
        "Choose New Return. Select the Supplier and Location. Location defaults to the active location when available, but it is independently selectable—verify it explicitly because this is where stock will be deducted.",
        "Enter a concise Reason and Notes. Use these fields for operational context that is safe to retain, such as defective, overstock, wrong items, or an authorization reference. The current form does not expose dedicated return-number, tracking-number, shipped-date, attachment, or carrier fields.",
        "Search Products and choose the exact product/variant. Selecting the same product and variant again increments its quantity instead of creating another row. Confirm the displayed product name, variant name, and SKU after every selection.",
        "For each line, enter the physical Qty leaving the selected location. Qty has a minimum of 1 in the visible control. Enter Unit Cost deliberately; Total Cost is calculated as quantity × unit cost and the return total is the sum of all lines. Cost is financial evidence and does not default to a supplier authorization amount unless the selected product data supplies it.",
        "Remove any wrong line with the trash control. Reconcile the item count, units, variants, unit costs, return total, supplier, location, reason, and notes against the physical shipment/authorization before proceeding. There is no preview page after the dialog.",
        "Choose Create Return once. Wait for Supplier return created and for the dialog to close. Do not click again while Saving is active. The new record is stored as Draft, but inventory deduction happens during this same creation path rather than waiting for Sent or Completed.",
        "Understand the inventory effect: CentriPOS applies a return movement with a negative quantity for each line at the chosen location, including the product/variant, unit cost, current user, source type supplier_return, source return ID, and note Return to supplier. This reduces on-hand stock immediately.",
        "Verify the new row in Supplier Returns: Date, Supplier, Location, Draft badge, Reason, number of item rows, and Total Cost. Then inspect the affected product/variant stock and the inventory movement history for the selected location. Reconcile before physically releasing the shipment if the screen’s item count or stock movement is missing or wrong.",
        "If QuickBooks Online purchasing settings are configured to create vendor credits from supplier returns, monitor the accounting sync outside this form. When CentriPOS stores an external vendor-credit URL, View QBO Credit appears below the status badge. Open it only to verify the supplier/vendor, date/reference strategy, item/cost totals, and accounting treatment; the link’s presence does not prove inventory or supplier settlement is otherwise complete.",
        "Do not treat Draft as permission to edit, send, cancel, or reverse from this screen. Those controls are not present. If the return was created with the wrong supplier, location, product, variant, quantity, or cost, stop physical and accounting follow-through and contact an authorized administrator/support with the return date, supplier, location, affected SKUs, expected versus actual quantities/costs, and movement evidence. Do not create an opposite stock change or duplicate return without an approved correction plan."
      ],
      "controls": [
        {
          "name": "New Return",
          "description": "Opens the creation dialog; it does not create a harmless preparatory shell until Create Return is chosen."
        },
        {
          "name": "Supplier*",
          "description": "Required vendor receiving the goods."
        },
        {
          "name": "Location*",
          "description": "Required stock location from which every return line will be deducted; defaults to active location when available but remains selectable."
        },
        {
          "name": "Reason",
          "description": "Optional short operational explanation stored on the return and shown in the list."
        },
        {
          "name": "Notes",
          "description": "Optional return notes stored on the record but not shown in the summary table."
        },
        {
          "name": "Products search",
          "description": "Adds an exact product or variant; selecting the same product/variant again increments quantity."
        },
        {
          "name": "Qty",
          "description": "Physical units returned for that line; visible input enforces a minimum of one."
        },
        {
          "name": "Unit Cost",
          "description": "Per-unit financial cost stored on the line and movement; review rather than assuming it matches a vendor credit."
        },
        {
          "name": "Trash",
          "description": "Removes a draft line from the open dialog before creation."
        },
        {
          "name": "Create Return",
          "description": "Creates the Draft return and its item rows, then immediately applies negative inventory movements. It is the posting point for stock."
        },
        {
          "name": "Saving",
          "description": "Disables repeat creation while the request is running."
        },
        {
          "name": "Supplier return created",
          "description": "Success toast; follow with list, stock, and movement verification."
        },
        {
          "name": "Draft status",
          "description": "Initial stored status. In the current screen it does not mean stock is untouched and is not paired with edit/send/cancel controls."
        },
        {
          "name": "Date / Supplier / Location / Status / Reason / Items / Total Cost",
          "description": "Read-only summary columns for existing returns. Items is the count of stored item rows, not the sum of quantities."
        },
        {
          "name": "Return inventory movement",
          "description": "Negative quantity at the selected location with movement type return and source type supplier_return."
        },
        {
          "name": "View QBO Credit",
          "description": "Appears only when an external accounting vendor-credit URL exists; opens QuickBooks in a new tab."
        },
        {
          "name": "Current screen limitation",
          "description": "No row detail, edit, status transition, ship, tracking, dedicated reference, cancellation, or inventory-reversal control is exposed."
        },
        {
          "name": "No exact screenshot",
          "description": "The Amelia Grant Harbor & Hearth /inventory/returns capture was rejected because it exposed private supplier and cost history. This guide intentionally uses no redacted-looking fabrication or unrelated image."
        }
      ],
      "expectedResult": "The supplier return records the intended vendor, items, quantities, disposition or shipment, and status, and inventory follows the configured return workflow.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "inventory-reports",
      "url": "https://platform.getcentri.com/centripos/inventory-reports",
      "title": "Use Inventory Reports",
      "summary": "Review tracked-product quantity and cost value, find replenishment and zero-stock exceptions, compare recorded margin, and identify inventory whose product record has been idle.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Reports",
      "introduction": "Open Inventory → Reports with the Bar Chart 3 icon. This screen is a current product-level inventory snapshot, not a dated movement report. It has five visible tabs and include/exclude filters; it currently has no date range, variant/location drill-down, export, Save Report, or working row regrouping. Use Inventory → Movements for historical stock activity and Inventory → Saved Reports only for configurations created by a supported save flow elsewhere.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Reports. The page title is Inventory Reports even though the browser title currently says Report Center. Only products with Track inventory enabled participate; untracked catalog products are excluded before any report filter is applied.",
        "Start on Summary. Products is the number of filtered tracked product records. Total Units adds stock_on_hand across every returned location-stock row. Total Value adds each location quantity multiplied by the product’s current Supply price. Negative stock can reduce both totals and value.",
        "Read each Summary row as one master product: product name, base SKU, aggregate units across its location-stock rows, and aggregate cost value using the base product supply price. The current screen does not expand variants or locations and does not open the product from the row.",
        "Choose Add Filter. Select Product Name, SKU, Supplier, Brand, Category, Tag, or Location, then choose Include or Exclude and type to search. Suggestions are limited to the first 10 matches for the chosen type; choose the exact suggestion to create a filter chip.",
        "Understand filters of the same type and mode as a group. Multiple Include chips for the same dimension work as OR: a product can match any chip in that group. Separate include dimensions work together as AND because each dimension group is applied in turn. Multiple Exclude chips remove a product if it matches any excluded value in that group.",
        "Understand Location filtering precisely. A product matches a Location chip only when it has a location-stock row for that location with stock_on_hand greater than zero. Include Location therefore does not show zero or negative stock at that location, and Exclude Location removes only products with positive stock there. The totals still aggregate all returned location rows for products that survive; they are not recalculated to only the selected location.",
        "Remove one chip with its X, or choose Clear all to remove every filter. The tab, filters, and nondefault group selector are encoded in the page URL, so a copied authenticated link can restore those controls for a permitted user. It does not preserve a historical inventory snapshot.",
        "Choose Replenishment to list a product when any location-stock row has a non-null Reorder point and stock_on_hand is less than or equal to that threshold. The row shows aggregate stock as “remaining,” not the specific triggering location or its reorder point. Use Live Inventory or the product/location record to identify the actual exception before ordering.",
        "Choose Performance to sort the filtered products by the stored Margin field from highest to lowest. Each row shows margin, aggregate units, and aggregate cost value. This is not sales velocity, profit earned, turns, or sell-through; no sales date window is queried on this screen.",
        "Choose Out of Stock to list products whose aggregate stock across all returned location rows equals exactly zero. A product with negative aggregate stock is not included, and one positive location can offset a negative location to produce zero. The row does not identify which location is empty.",
        "Choose Dusty to list products with aggregate stock greater than zero, ordered from the oldest product updated_at timestamp to the newest. The “days idle” number is days since the product record was updated, not days since last sale, receipt, transfer, count, or stock movement. Treat it as catalog-record staleness rather than proven slow-moving inventory.",
        "On desktop, choose Summary, Replenishment, Performance, Out of Stock, or Dusty from the tab row. On mobile, use the single report dropdown; the header collapses after scrolling to leave more room for results.",
        "The screen initially renders 50 result rows. Choose Load more to add the next 50 until all rows for the active tab and filters are visible. Changing the tab or any filter resets the visible count to the first 50.",
        "Treat the By Product, By Brand, By Category, and By Location selector as nonfunctional for row grouping in the current implementation. It changes the group parameter in the URL, but the calculations and rows remain product-level. Do not describe or screenshot the unchanged rows as a brand, category, or location grouping.",
        "Interpret empty states in context. No products currently below reorder point means the current replenishment/filter result is empty. All products are in stock means no filtered product has aggregate stock exactly zero. No results found covers Summary, Performance, or Dusty when filters or source records produce no rows.",
        "For location-specific stock, variants, reorder points, or available quantity, open Inventory → Live Inventory. For dated sales, receipts, transfers, counts, returns, fulfillments, or adjustments, open Inventory → Movements. For audit-quality purchasing decisions, trace the product and exact location instead of relying only on aggregate product rows.",
        "There is no Export, Print, Save Report, scheduled report, row detail, or chart control on this screen today. Do not tell a user to save or export this view. If a repeatable report is required, preserve the authenticated URL for the current controls or use another supported reporting surface until Inventory Reports exposes a real save/export action."
      ],
      "controls": [
        {
          "name": "Bar Chart 3 icon",
          "description": "The exact CentriPOS navigation icon for Inventory → Reports."
        },
        {
          "name": "Tracked products only",
          "description": "The source list begins with products whose Track inventory setting is enabled."
        },
        {
          "name": "Summary",
          "description": "Current product-level quantities and supply-cost value for the active filters."
        },
        {
          "name": "Products",
          "description": "Count of filtered tracked master-product records, not variants or location rows."
        },
        {
          "name": "Total Units",
          "description": "Sum of stock_on_hand across every location-stock row belonging to filtered products."
        },
        {
          "name": "Total Value",
          "description": "Sum of stock_on_hand × current base product Supply price across location-stock rows; negative stock can reduce it."
        },
        {
          "name": "Product row",
          "description": "Master product name, base SKU, aggregate units, and product-level cost value; it is not interactive."
        },
        {
          "name": "Add Filter",
          "description": "Opens filter type, Include/Exclude mode, and a searchable suggestion list."
        },
        {
          "name": "Product Name filter",
          "description": "Matches one exact product ID selected from suggestions."
        },
        {
          "name": "SKU filter",
          "description": "Matches the exact base product SKU; variant SKUs are not offered by this screen’s filter source."
        },
        {
          "name": "Supplier / Brand / Category / Tag filter",
          "description": "Matches relationships attached to the master product."
        },
        {
          "name": "Location filter",
          "description": "Matches only a location-stock row whose stock_on_hand is greater than zero; totals remain aggregated across the surviving products’ rows."
        },
        {
          "name": "Include chip group",
          "description": "OR within the same dimension; different dimension groups are applied together."
        },
        {
          "name": "Exclude chip group",
          "description": "Removes products matching any excluded value in that dimension."
        },
        {
          "name": "Filter-chip X",
          "description": "Removes one exact include or exclude filter."
        },
        {
          "name": "Clear all",
          "description": "Removes every active filter without changing the selected report tab."
        },
        {
          "name": "Replenishment",
          "description": "Products having any location row at or below a non-null reorder point; the displayed remaining quantity is aggregate."
        },
        {
          "name": "Performance",
          "description": "Products sorted by stored margin descending, with units and cost value; it is not dated sales performance."
        },
        {
          "name": "Out of Stock",
          "description": "Products whose aggregate stock equals exactly zero; negative aggregate inventory is excluded."
        },
        {
          "name": "Dusty",
          "description": "Positive aggregate-stock products ordered by product-record updated_at; days idle does not represent last inventory movement or sale."
        },
        {
          "name": "Mobile report dropdown",
          "description": "Mobile replacement for the five desktop tab buttons."
        },
        {
          "name": "Load more",
          "description": "Adds 50 more product rows for the active result."
        },
        {
          "name": "By Product / Brand / Category / Location",
          "description": "Currently writes URL group state only and does not regroup or recalculate the displayed product rows."
        },
        {
          "name": "URL state",
          "description": "Stores tab, filters, and nondefault group choice for an authenticated permitted user; it is not a saved historical snapshot."
        },
        {
          "name": "No products currently below reorder point",
          "description": "Completed empty Replenishment result for current filters."
        },
        {
          "name": "All products are in stock",
          "description": "Completed empty Out of Stock result under the exact aggregate-zero rule."
        },
        {
          "name": "No results found",
          "description": "Completed empty result for the active source, tab, and filters."
        },
        {
          "name": "Not available here",
          "description": "No date range, movement history, variant/location drill-down, export, print, chart, Save Report, or scheduled report control."
        }
      ],
      "expectedResult": "The active tab and include/exclude chips return the intended tracked master products; aggregate units and supply-cost value reconcile to their location-stock rows; replenishment, exact-zero, margin, and product-update-age rules explain every exception; and no dated movement, variant/location drill-down, export, save, or regrouping behavior is inferred from controls that do not provide it.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "saved-inventory-reports",
      "url": "https://platform.getcentri.com/centripos/saved-inventory-reports",
      "title": "Understand Saved Inventory Reports",
      "summary": "Review the current Saved Reports registry without mistaking its placeholder scheduling and opening controls for a working automated-report service.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Saved Reports",
      "introduction": "The current Inventory → Saved Reports screen can create, list, and deactivate inventory-summary records, but it does not save the filters, columns, grouping, location scope, or date logic from another report. Its Schedule automatic delivery fields are stored, yet no report-generation or email-delivery worker is present in the current customer-visible implementation. Open navigates to /inventory/reports?slug=…, a route whose approved Harbor & Hearth inspection did not resolve to a finished Inventory Reports view. Treat this screen as an in-progress registry, not a dependable reporting or delivery workflow.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Saved Reports. The navigation uses the Bookmark icon; the page describes itself as Manage scheduled and bookmarked reports.",
        "Wait for the loading spinner to finish. The list is tenant-scoped, includes only active saved_reports rows, and orders newest records first. “No saved reports yet” is a fully rendered empty state, not proof that Inventory data is missing.",
        "If records exist, read the report name, type badge, creation date, Scheduled badge, recipient count, and creator name. These labels describe stored metadata; they do not prove a report has successfully run, refreshed, or reached any recipient.",
        "Choose Save Report only if you intentionally want to create a named inventory_summary registry record. Enter Report Name. The current dialog does not capture a source report, locations, products, filters, columns, grouping, date range, format, or timezone.",
        "Leave Schedule automatic delivery off unless CentriPOS support has separately confirmed an active delivery service for this tenant. Turning it on reveals a raw Schedule (cron) string and comma-separated Recipients field; the default string is 0 8 * * 1 and the UI labels it every Monday at 8:00 AM, but the page does not identify a timezone.",
        "If scheduling has been explicitly approved, confirm every recipient address and the intended schedule outside this screen before saving. The client splits recipients on commas and stores nonblank text; it does not visibly validate each address or send a test email. Never enter passwords, payment data, or customer lists into these fields.",
        "Choose Save Report once. A successful toast says Report saved and the new record appears after the list refreshes. This action currently saves report_type inventory_summary with an empty filters object; it does not snapshot or run a report.",
        "Use Open cautiously. It navigates to Inventory Reports with the saved slug, but the current Saved Reports code does not itself load, render, or verify a report result. If the destination is blank, mismatched, loading, or otherwise unfinished, return without repeatedly creating duplicate records and contact support.",
        "Use the trash icon only when you intend to remove the record from the active list. The action immediately sets is_active to false and shows Report removed; there is no confirmation dialog, visible restore action, or permanent-delete action on this screen.",
        "For an inventory count filter preset, use the supported Save filter inside the inventory-count creation workflow. Those presets also use saved_reports storage but have report_type inventory_count_filter and real filter snapshots; they are separate from the blank inventory_summary records created here.",
        "For dependable current inventory, use the working Inventory screens and exports described in their exact guides. For scheduled email reporting, confirm a supported reporting workflow with CentriPOS support instead of relying on the badges or cron fields alone."
      ],
      "controls": [
        {
          "name": "Bookmark icon",
          "description": "Exact CentriPOS navigation and empty-state icon for Saved Reports."
        },
        {
          "name": "Saved report list",
          "description": "Active tenant-scoped saved_reports records, newest first."
        },
        {
          "name": "Report type badge",
          "description": "Stored report_type with underscores displayed as spaces; it does not prove the report renderer is implemented."
        },
        {
          "name": "Created date",
          "description": "Record creation date shown in the viewer’s date formatting."
        },
        {
          "name": "Scheduled badge",
          "description": "Shows is_scheduled is true; it is not delivery evidence."
        },
        {
          "name": "Recipient count",
          "description": "Number of stored recipient strings; no delivery status or address list is shown in the row."
        },
        {
          "name": "Creator",
          "description": "Display name from the profile that created the record when available."
        },
        {
          "name": "Save Report",
          "description": "Creates a named inventory_summary record with empty filters; it does not capture the current report setup."
        },
        {
          "name": "Report Name",
          "description": "Only required field in the current creation dialog."
        },
        {
          "name": "Schedule automatic delivery",
          "description": "Stores is_scheduled, a cron string, and recipients. No active generator/email runner was found in the current implementation."
        },
        {
          "name": "Schedule (cron)",
          "description": "Raw technical schedule string; default 0 8 * * 1 is labeled Monday at 8:00 AM, with no timezone shown."
        },
        {
          "name": "Recipients",
          "description": "Comma-separated strings stored with the record; the UI does not visibly validate individual email addresses or send a test."
        },
        {
          "name": "Open",
          "description": "Navigates to /inventory/reports?slug=<saved slug>; it does not itself guarantee a rendered report."
        },
        {
          "name": "Trash icon",
          "description": "Immediately deactivates the record without a confirmation dialog or visible restore."
        },
        {
          "name": "No saved reports yet",
          "description": "Completed zero-record state in the Amelia Grant Harbor & Hearth account."
        },
        {
          "name": "Inventory count filter",
          "description": "Separate saved filter preset created inside Inventory Counts with report_type inventory_count_filter and an actual filter snapshot."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /inventory/saved-reports in its fully rendered empty state. It safely shows the Bookmark icon, Save Report control, and zero-record message without exposing inventory or recipient data."
        }
      ],
      "expectedResult": "The named view reopens with the intended inventory filters, columns, grouping, and sorting while continuing to show current inventory data.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/inventory-saved-reports.png",
        "alt": "Harbor & Hearth Saved Reports screen showing inventory navigation, saved-report management, and the fully rendered empty state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "inventory-network-overview",
      "url": "https://platform.getcentri.com/centripos/inventory-network-overview",
      "title": "Review Network Inventory",
      "summary": "Use the dedicated HQ Network Inventory screen to compare recorded stock, reorder exceptions, cost value, and HQ-versus-local retail pricing across participating businesses and locations.",
      "collection": {
        "id": "inventory",
        "title": "Inventory"
      },
      "section": "Network Inventory",
      "introduction": "Inventory → Network Inventory opens the dedicated /inventory/network workspace for an HQ-enabled role. It is not the ordinary Inventory screen in an all-location mode, and /network/inventory is a different route. This screen is read-only: it does not adjust inventory, reserve stock, create a transfer, or prove that units are available to promise.",
      "beforeYouBegin": "Confirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.",
      "steps": [
        "Go to Inventory → Network Inventory. The navigation item and page heading use the Globe icon. This Enterprise navigation item is HQ-only, so it may be absent when the current role or business is not eligible.",
        "Confirm the enterprise context. The screen aggregates the network represented by the current HQ identity rather than only the active selling location.",
        "Read the five summary cards: Franchisees counts represented businesses, Products counts grouped master products, Network Units sums recorded stock-on-hand, Below Reorder counts represented location exceptions, and Network Value aggregates stock value. Cost-restricted roles see dots instead of Network Value.",
        "Use All, In Stock, Below Reorder, Zero, or Negative. In Stock, Zero, and Negative classify each product by its filtered aggregate quantity. Below Reorder includes a product when at least one represented location has positive stock below its reorder point.",
        "Search by grouped product name or master SKU. This search does not match brand, business, location, variant name, or variant SKU.",
        "When more than one business is represented, open Franchise and select one or more businesses. The visible product rows, stock totals, reorder count, and value are recalculated from those tenant rows. Choose Clear all to restore the full represented network.",
        "Read the result count as visible products out of the full loaded product count. If no products appear, clear Search, choose All, and clear the Franchise filter before treating the result as missing inventory.",
        "Open a product row. The collapsed row shows its name, master SKU, brand on wider screens, participating-business count, variant count when present, location-level reorder exceptions, aggregate units, and permitted value and HQ retail information. Discontinued marks a deprecated HQ/master record; it does not erase local stock.",
        "For a simple product, expand the business row, then read each location’s stock-on-hand and configured reorder point. For a variable product, expand the intended variant first, then its business row, so you compare the exact SKU rather than only the master total.",
        "Use the retail badge only as an HQ price comparison when price visibility is permitted: green is a match within one cent, amber is above HQ, and red is below HQ. It is not an inventory-health or margin indicator.",
        "Treat Network Units as recorded on-hand and Network Value as an operational cost aggregation. Neither accounts for commitments, incoming supply, open purchase orders, transfer-in-transit quantities, or fulfillment availability. Negative stock can reduce the totals.",
        "Use Network Transfers for a cross-business request or movement, and use the appropriate local count or adjustment workflow to correct a location quantity. Before promising an item, confirm the exact business, variant, location, and current fulfillment state in the operational workflow."
      ],
      "controls": [
        {
          "name": "Globe icon",
          "description": "Exact CentriPOS navigation and screen icon for Inventory → Network Inventory."
        },
        {
          "name": "HQ-only",
          "description": "The Inventory navigation entry is limited to eligible headquarters access."
        },
        {
          "name": "Franchisees",
          "description": "Distinct participating businesses represented by the loaded network products."
        },
        {
          "name": "Products",
          "description": "Grouped master-product count returned by the network inventory source."
        },
        {
          "name": "Network Units",
          "description": "Sum of recorded stock-on-hand across represented product, business, and location rows."
        },
        {
          "name": "Below Reorder summary",
          "description": "Number of represented locations with stock greater than zero and below their reorder point."
        },
        {
          "name": "Network Value",
          "description": "Aggregated stock-on-hand value; hidden when cost visibility is restricted."
        },
        {
          "name": "All",
          "description": "Every product remaining after Search and Franchise filters."
        },
        {
          "name": "In Stock",
          "description": "Products whose filtered aggregate stock is greater than zero."
        },
        {
          "name": "Below Reorder tab",
          "description": "Products with at least one positive-stock location below its reorder point."
        },
        {
          "name": "Zero",
          "description": "Products whose filtered aggregate stock equals zero."
        },
        {
          "name": "Negative",
          "description": "Products whose filtered aggregate stock is below zero."
        },
        {
          "name": "Search product name or SKU",
          "description": "Matches only grouped product name or master SKU."
        },
        {
          "name": "Franchise filter",
          "description": "Limits represented businesses and recalculates the product rows and their filtered totals."
        },
        {
          "name": "Product row",
          "description": "Grouped master-product summary with participating-business, variant, reorder, unit, value, and HQ retail context as permitted."
        },
        {
          "name": "Discontinued",
          "description": "HQ/master record is deprecated while represented stock can remain visible."
        },
        {
          "name": "Variant row",
          "description": "Exact variant name, SKU, network units, business count, reorder exceptions, and permitted HQ retail reference."
        },
        {
          "name": "Business row",
          "description": "Participating-business retail comparison, location count, reorder count, and total units."
        },
        {
          "name": "Location row",
          "description": "Exact location stock-on-hand and configured reorder point."
        },
        {
          "name": "Retail comparison badge",
          "description": "Green matches HQ within one cent, amber is above HQ, and red is below HQ."
        },
        {
          "name": "Read-only boundary",
          "description": "No inventory adjustment, reservation, purchasing, movement, or transfer is performed on this screen."
        },
        {
          "name": "Available-to-promise boundary",
          "description": "A positive recorded quantity does not prove that units are uncommitted and ready for a new sale."
        }
      ],
      "expectedResult": "The dedicated HQ Network Inventory screen shows the intended represented businesses and exact product or variant totals; Franchise, stock-state, search, reorder, value, and retail-comparison evidence reconcile to the expanded location rows without being mistaken for available-to-promise inventory.",
      "troubleshooting": [
        "Confirm the exact product variant and stock location before posting a quantity change.",
        "Use the movement ledger to identify the source workflow instead of correcting history directly.",
        "Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/inventory-network.png",
        "alt": "Real Amelia Grant Harbor & Hearth Network Inventory screen showing franchise, product, network-unit, reorder, value, stock-state, search, and franchise-filter controls in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "products-list",
      "url": "https://platform.getcentri.com/centripos/products-list",
      "title": "Use the Products list",
      "summary": "Search the entire loaded catalog, use URL-backed product and variant filters, inspect pricing/stock safely, and perform immediate row or bulk catalog actions without confusing filtered display scope with export or network-publish scope.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Products → Products uses the Package icon. The page loads active and inactive products for the current tenant, then filters and sorts them in the browser. Search/filter values are shareable URL state, but selection and expanded rows are local state. Several controls mutate records immediately. Export always writes every loaded product—not only the filtered/selected rows—and includes supply price even when the screen hides costs. Import, Composites, and network Publish appear only for an enterprise/HQ tenant; network Publish is distinct from the selected-product Online Store actions.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Products, identified by the Package icon. Confirm the active CentriPOS business and read “<filtered> of <total> items in catalog.” The default Status is Active, so the first number can be smaller than the total even before you type a search.",
        "Wait for the product loader to finish. No products match your search appears when a nonblank search produces zero rows. No products yet can also mean the current filters produce zero rows, not necessarily that the tenant has no loaded products; choose Clear filters and All products before concluding the catalog is empty.",
        "Search product name, product SKU, barcode, variant name, variant SKU, variant supplier code, or variant attribute values. Every whitespace-separated token must occur somewhere in the combined lowercased product/variant text, but the tokens do not need to occur in the same field or variant.",
        "Use Brand, Category, Tag, Supplier, Type, and Status filters. Multiple selections within Brand/Category/Tag/Supplier use any-match logic; different filter groups all must pass. Supplier matching comes from supplier price-list entries, not only a product’s visible base vendor field.",
        "Type supports Standard, Variable, and Bundle (stored as composite). Status supports All products, Active, Inactive, POS enabled, POS disabled, Published online, and Not published. Not published means publish_status is anything other than exactly `published`, including hidden and missing values.",
        "Variant filters can arrive in the URL as repeated `variantAttribute` and `variant` values. Attribute filters require one variant to contain every selected attribute key. Value filters require one variant to match every selected attribute/value pair exactly after lowercase normalization. The visible chips can be cleared separately with Clear variant filters.",
        "Understand URL persistence. Search uses `q`; Brand, Category, Tag, Supplier, Type, Variant, and Variant Attribute can repeat; nondefault Status is stored. Opening/closing a product editor preserves these list parameters and attempts to restore the prior product/scroll position. A shared URL does not grant catalog permissions.",
        "Choose Clear filters to reset search, all catalog/variant filters, and Status to Active. The list is always sorted by product name A–Z using case-insensitive natural numeric order, then SKU; “Sorted A-Z” is informational and has no alternate list-sort control.",
        "Read a product card. It can show image, name, minimum enabled-variant retail price as From, permission-sensitive minimum enabled-variant vendor cost, displayed margin, stock, category names, Standard/Variable/Bundle type, SKU, Inactive, HQ source, variant count, and a franchisee-only recommended retail price.",
        "Cost and margin are hidden when the profile’s cost-visibility permission says to hide them. Do not treat an absent cost as zero. Export currently still includes supply_price and calculated margin for all loaded products regardless of this card-level hideCosts state, so only authorized users should export and the downloaded file must be protected.",
        "For a variable product, card Retail and Vendor Cost use the minimum positive retail/supply price among enabled variants when present; “From” indicates that rollup. The displayed margin combines those two minima even if they come from different variants. Inspect the expanded variant/product detail before pricing decisions.",
        "Stock follows the active app location ID when present; otherwise it sums location_stock across all returned locations. An untracked item shows ∞ Stock. A tracked quantity below 10 is styled as warning, but 10 is only this visual threshold—not a configured reorder rule. Choose the Stock link to open Live Inventory expanded to the product.",
        "Choose the row or chevron to expand the embedded Product Quick View. Cost-visible users can select Base cost or returned supplier price-list cost bases there; missing retail/base/selected cost, no price book, low margin below 35%, and 50%+ margin are diagnostic badges, not automatic price changes.",
        "Choose Edit to open `/catalog/products/<product ID>` while preserving list search. Add Product opens `/catalog/products/new`. Save/cancel behavior belongs to the product editor; returning to the list attempts to center the edited product or restore prior scroll. Verify the correct ID and persisted record.",
        "Treat Active/Inactive and POS badges as immediate row actions. Clicking Active toggles `is_active`; clicking POS toggles `sell_pos`; there is no confirmation and no success toast, only an error toast if the update fails. Reload and verify before assuming the catalog or register changed. Active and POS are independent.",
        "Select product checkboxes only for intentional bulk work. The header checkbox in the bulk bar selects or clears every product in the current filtered result—not every loaded product—based on whether selected count equals filtered count. Existing selections are not automatically cleared when filters change, so the selected count can include products no longer visible. Use Clear selection and rebuild it after any filter change.",
        "Under Actions → Categories or Tags, Add upserts the selected product relationships and Remove deletes them immediately with no confirmation. Empty option lists mean no categories/tags are available. Wait for Categories updated or Tags updated, then inspect representative selected products.",
        "Under Actions → Online Store, Publish online sets publish_status `published` and sell_online true. Unpublish (draft) sets `draft` and sell_online false. Set hidden sets `hidden` and sell_online false. These are immediate selected-product database updates with no confirmation; verify the storefront behavior and do not confuse them with network publication.",
        "Under Actions → Pricing, Enable or Disable custom price at sale immediately updates allow_custom_price for every selected ID. This changes whether authorized checkout users can enter a custom price; it does not set a price, create a discount, or limit by register. Test permissions and receipt/audit behavior with a controlled sale.",
        "Delete products opens a browser confirmation naming only the selected count. Confirming hard-deletes those product rows. The UI says denormalized sales and inventory history remains with a Deleted note, but there is no restore action. Audit variants, inventory, open/saved sales, online listings, bundles, supplier lists, labels, integrations, and historical reporting before deletion.",
        "Use Export → XLSX or CSV with care. The export ignores search, filters, and selectedIds and serializes every product in the loaded `products` array. It includes name, SKU, product type, brand, supply price, retail price, calculated margin, inventory/POS/online/active flags, barcode, description, categories, and tags; it omits variant rows, supplier price-list detail, stock quantities, and images.",
        "The XLSX/CSV export filename is `products-export` and the success message reports the total loaded product count. CSV is written through the workbook library from the same single Products sheet. Check row count and protect cost/barcode/description data before sharing.",
        "Import and Composites appear only for an enterprise/HQ tenant. Import receives a location map built from every tenant location name with spaces converted to underscores; duplicate normalized names can overwrite one another in that map. Preview and validate a backup/export, location columns, products, variants, warnings, and counts before any controlled import.",
        "Network Publish appears only for enterprise/HQ with child tenants. Choose one franchisee or All franchisees, then Publish. All runs one RPC sequentially per child and sums returned counts; a later failure does not roll back earlier franchisees. This is master-catalog synchronization, not online-store publishing. Audit each target and do not retry blindly after partial failure.",
        "A franchisee product with source_product_id shows HQ and can show HQ recommended retail. That badge does not prove every field is current, locked, or safe to overwrite; inspect Master Catalog/network synchronization rules before local edits.",
        "Use the real Amelia Grant Harbor & Hearth screenshot to orient to `/catalog/products` at 1440×900. It is the exact loaded Products list capture recorded in the approved manifest. No import, export, bulk mutation, product editor, network publish, deletion, customer, or transaction action was performed for the screenshot."
      ],
      "controls": [
        {
          "name": "Package icon",
          "description": "Exact CentriPOS Products navigation/page identity."
        },
        {
          "name": "Filtered of total count",
          "description": "Browser-filtered rows versus every loaded active/inactive product."
        },
        {
          "name": "Search",
          "description": "All whitespace tokens must appear somewhere in combined product and variant search text."
        },
        {
          "name": "Brand / Category / Tag / Supplier",
          "description": "Any-match within each group; all active groups must pass."
        },
        {
          "name": "Supplier filter",
          "description": "Derived from supplier price-list entries."
        },
        {
          "name": "Type",
          "description": "Standard, Variable, or Bundle/composite."
        },
        {
          "name": "Status",
          "description": "All, Active, Inactive, POS enabled/disabled, Published online, or Not published."
        },
        {
          "name": "Not published",
          "description": "Any publish_status other than exactly published, including hidden/missing."
        },
        {
          "name": "Variant Attribute",
          "description": "Requires one variant containing every selected attribute key."
        },
        {
          "name": "Variant value",
          "description": "Requires one variant matching every selected attribute/value pair."
        },
        {
          "name": "URL state",
          "description": "q and repeated filter parameters persist through editor routing."
        },
        {
          "name": "Sorted A-Z",
          "description": "Fixed name natural sort then SKU; no alternate list sort."
        },
        {
          "name": "Vendor Cost / Margin",
          "description": "Permission-hidden on cards but currently still included in export."
        },
        {
          "name": "From price/cost",
          "description": "Minimum positive values among enabled variants; may not represent the same variant."
        },
        {
          "name": "Stock",
          "description": "Active-location quantity when a location exists, otherwise all-location sum."
        },
        {
          "name": "∞ Stock",
          "description": "Inventory tracking is off."
        },
        {
          "name": "Stock link",
          "description": "Working Live Inventory link expanded to the product."
        },
        {
          "name": "Expand row",
          "description": "Embedded Product Quick View and cost/price-book diagnostics."
        },
        {
          "name": "Edit / Add Product",
          "description": "Route-backed product editor preserving list URL state."
        },
        {
          "name": "Active badge",
          "description": "Immediate is_active toggle with no confirmation/success toast."
        },
        {
          "name": "POS badge",
          "description": "Immediate sell_pos toggle with no confirmation/success toast."
        },
        {
          "name": "Selection",
          "description": "Local set that can retain hidden IDs after filters change."
        },
        {
          "name": "Select all",
          "description": "Current filtered rows only."
        },
        {
          "name": "Categories / Tags",
          "description": "Immediate bulk relationship add/remove."
        },
        {
          "name": "Online Store bulk action",
          "description": "Immediate publish_status and sell_online update for selected IDs."
        },
        {
          "name": "Custom price at sale",
          "description": "Immediate allow_custom_price update for selected IDs."
        },
        {
          "name": "Delete products",
          "description": "Confirmed hard delete with no restore control."
        },
        {
          "name": "Export XLSX / CSV",
          "description": "Every loaded product, not filtered/selected rows; includes supply cost and no variant/stock detail."
        },
        {
          "name": "Import / Composites",
          "description": "Enterprise/HQ-only catalog ingestion workflows."
        },
        {
          "name": "Publish Products to Network",
          "description": "Enterprise/HQ child-tenant RPC, sequential by child for All and nontransactional across targets."
        },
        {
          "name": "HQ badge / recommended retail",
          "description": "Product linked to a source master; not complete synchronization proof."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real approved loaded `/catalog/products` capture with no mutation or sensitive workflow opened."
        }
      ],
      "expectedResult": "The intended product is identified by product/variant evidence and the active URL filters; displayed price/cost/stock scope is understood, selected IDs are rebuilt after filter changes, each immediate row/bulk mutation is verified on the exact products, exports are treated as all-loaded-product cost-bearing files rather than filtered downloads, and any HQ network publication is audited target by target for partial completion.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-products.png",
        "alt": "Harbor & Hearth Products screen showing product search, catalog filters, import and export controls, and product cards in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "create-product",
      "url": "https://platform.getcentri.com/centripos/create-product",
      "title": "Create and verify a product",
      "summary": "Build the selling identity, product type, taxability, channel and location availability, cost/price, inventory, variants, codes, shipping data, online-store content, and post-save stock details for a new catalog item.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Name is the only universally required visible field, but a minimally valid save is not a sell-ready product. Product type cannot be changed after creation. SKU validation checks reserved system values and duplicates across products and variants; missing SKUs may be generated according to tenant SKU settings. New standard-product per-location stock, serial numbers, extra product codes, packaging relationships, history, and health tools require saving the base product first.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Confirm the intended business and catalog scope, then go to Products → Product Catalog. Use the real Harbor & Hearth Products screenshot below to identify the catalog landing screen; choose Add product to open the Product editor. Do not use Add Custom Item Product for normal reusable catalog merchandise.",
        "In General, enter the customer/staff-facing Name and Description. Choose the Brand, Category, and Tags that should drive search, filters, promotions, labels, online merchandising, and reporting. New tags can be created from the search when no exact tag exists; avoid duplicates caused by spelling or casing.",
        "Choose Product type before creation: Standard / Variable for ordinary or variant merchandise, Composite (Bundle) for a product/variant assembled from components, Non-inventory for non-stocked items, or Gift card for the gift-card model. The selector is disabled when editing an existing product, so correct a wrong type before the first save.",
        "Set Sales tax type deliberately. General merchandise uses standard tax; No tax bypasses tax; ZipTax TIC choices support product-specific reduced rates, exemptions, thresholds, food, clothing, software, services, and other rules. Tax type is product taxability, not the customer’s exemption or location nexus decision.",
        "Set Sell at point of sale. Enable Custom price at sale only for legitimate open-price products; it prevents a $0 default from being treated as an extreme markdown, but it also authorizes associates to enter the selling amount through the supported flow.",
        "Choose Availability restrictions: Available everywhere, Only selected locations, or Only selected registers. If restricted, select at least one allowed location/register or save is blocked. Availability controls where the item can be offered; it does not move stock or grant access to another business.",
        "Add warranty label and an optional PDF when the product has customer-facing coverage. A newly selected PDF uploads when the product is saved. Verify the document contains no unrelated private data and that the label accurately describes coverage.",
        "For a product without variants, enter its SKU and Barcode. Use the camera control to scan/capture when appropriate. Turn on Track inventory only when on-hand quantities should be maintained, Track serial numbers only when individual units require serial custody, and set Leasable / Financeable explicitly or leave the supported category inheritance. New products must be saved before per-location stock or serial management appears.",
        "Choose the Primary vendor and Vendor code. For a nonvariant product, enter Vendor Cost and Retail price and review the calculated markup and margin. Composite cost can be derived/restricted when components exist. Do not mistake vendor cost for average or last received cost, which appears later on existing products.",
        "For Standard / Variable or Composite products, add attribute names and values. CentriPOS automatically generates every cross-combination. Review each variant’s unique SKU, vendor code, cost, retail, enabled On state, barcode, stock/reorder details, and any per-variant bundle recipe. Parent SKU/barcode fields are hidden once variants exist.",
        "Use Sync vendor code to SKU only when both identifiers should intentionally match. Missing SKUs can be assigned from tenant rules at save, but reserved system SKUs and duplicates within this product or anywhere else in the catalog are blocked. Resolve the named conflict rather than slightly disguising a duplicate.",
        "For a Composite product, add exact component products/variants and quantities. Validate that recipes do not create unsafe self-reference or circular/nested relationships. Component cost drives the supported derived cost. For variant composites, expand and verify the recipe on every affected variant.",
        "Add the Primary Product Image. Confirm crop/orientation and that the image represents the exact sellable item rather than another size/color. Images are reused in catalog, Sell, labels, online surfaces, and integrations where supported.",
        "Open Labeling & Shipping. On a brand-new unsaved product, review shipping data but save the base product before adding additional product codes. After the first save, add UPC, EAN, GTIN, ISBN, manufacturer, internal, supplier, case-pack, or other codes; or generate from SKU/supplier code. Choose whether a code applies to the product or an enabled variant, its pack quantity, Scan default, and Label default.",
        "Enter shipping weight in ounces, length/width/height in inches, package preset, origin country, HS code, and customs description when shipped. Set Ships individually, Signature default, Fragile, Oversized, Restricted, and Insure by default only when operationally true. These values support shipping fulfillment/EasyPost; they do not create a shipping method or buy postage by themselves.",
        "Open Online Store. Enable online sale and choose publish status only when the connected storefront and product content are ready. Complete online description, SEO title, meta description, URL slug, sort order, online tags, custom fields and storefront visibility, gallery/mapping, and supported WooCommerce/ACF sync. Saving a product does not guarantee an external store published successfully—verify the integration result separately.",
        "Choose Create product once and wait. Save blocks a blank name, empty selected availability scope, unsafe variant bundle recipes, reserved/duplicate SKUs, and other returned errors. If you close with unsaved changes, use the discard confirmation deliberately.",
        "Reopen the product after success. Complete any second-pass controls that require a product ID: per-location stock/reorder values, serial numbers, additional codes, label printing, packaging relationships, vendor price-list references, price/cost history, product health, online custom fields/gallery, and other supported edit-only panels. Save again and verify.",
        "Test from Register → Sell in the intended location/register. Search by name, SKU, barcode, and added scan-default code; select the intended variant; verify POS availability, enabled state, price/custom-price behavior, tax, inventory/serial prompts, bundle components, fulfillment/shipping behavior, image, warranty, labels, and receipt identity. Also verify online visibility separately when enabled."
      ],
      "controls": [
        {
          "name": "Product Catalog / Add product",
          "description": "Opens the reusable catalog Product editor from the Products landing screen shown in the real Harbor & Hearth screenshot."
        },
        {
          "name": "Name*",
          "description": "Only universally required visible field; whitespace-only names are rejected."
        },
        {
          "name": "Product type",
          "description": "Standard / Variable, Composite (Bundle), Non-inventory, or Gift card; disabled after creation."
        },
        {
          "name": "Sales tax type",
          "description": "Product taxability selection: General merchandise, No tax, or supported ZipTax TIC."
        },
        {
          "name": "Tags",
          "description": "Search/add existing tags or create a missing exact tag; tags feed supported search, filters, merchandising, and rules."
        },
        {
          "name": "Sell at point of sale",
          "description": "Controls POS channel eligibility."
        },
        {
          "name": "Custom price at sale",
          "description": "Allows supported sale-time price entry for open-price products."
        },
        {
          "name": "Availability restrictions",
          "description": "Everywhere, selected locations, or selected registers; restricted scope must contain at least one selection."
        },
        {
          "name": "Warranty PDF",
          "description": "Uploads when the product is saved; edit mode can open or clear the stored attachment."
        },
        {
          "name": "SKU validation",
          "description": "Rejects reserved system SKUs, duplicates within the draft, and conflicts with any other product or variant; tenant rules may generate missing SKUs."
        },
        {
          "name": "Track inventory",
          "description": "Enables stock behavior; new nonvariant products must be saved before per-location stock controls appear."
        },
        {
          "name": "Track serial numbers",
          "description": "Enables serialized-unit management; serial controls require an existing saved product."
        },
        {
          "name": "Leasable / Financeable",
          "description": "Explicit eligible/ineligible choice or supported category inheritance."
        },
        {
          "name": "Primary vendor / Vendor code",
          "description": "Catalog supplier relationship and supplier-facing identifier; variant products manage vendor codes per variant."
        },
        {
          "name": "Vendor Cost / Retail price",
          "description": "Base nonvariant cost and sell price used to calculate displayed markup and margin."
        },
        {
          "name": "Variants",
          "description": "Automatic cross-combinations of attribute values with per-variant identifier, price, enabled, barcode, inventory, and supported bundle detail."
        },
        {
          "name": "Composite recipe",
          "description": "Component product/variant quantities used to represent a bundle; unsafe recipes are blocked."
        },
        {
          "name": "Primary Product Image",
          "description": "Main catalog image reused by supported POS, online, label, and integration surfaces."
        },
        {
          "name": "Product codes",
          "description": "Additional scannable/label identifiers with type, product/variant target, pack quantity, Scan default, Label default, and active state; require a saved product ID."
        },
        {
          "name": "Labeling & Shipping",
          "description": "Tab for product codes/label printing plus weight, dimensions, package, customs, and shipment-default flags."
        },
        {
          "name": "Online Store",
          "description": "Tab for online eligibility/status, content, SEO, tags, custom fields, gallery, and supported WooCommerce/ACF behavior."
        },
        {
          "name": "Create product / Save",
          "description": "Validates and writes the product; post-save edit-only data may require reopening and saving again."
        },
        {
          "name": "Exact screenshot scope",
          "description": "The screenshot is the approved real Amelia Grant Harbor & Hearth Product Catalog landing screen where this workflow begins. The modal’s private editable values are not fabricated into the image."
        }
      ],
      "expectedResult": "The product is saved once with the intended variants, codes, prices, tax, inventory behavior, media, availability, and location or network scope.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-products.png",
        "alt": "Real Amelia Grant Harbor & Hearth Product Catalog landing screen where Add product opens the CentriPOS product editor",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "variants-attributes",
      "url": "https://platform.getcentri.com/centripos/variants-attributes",
      "title": "Create variants and standardize variant attributes",
      "summary": "Build sellable variant combinations inside a product, then use Variant Attributes to audit existing names and values and safely standardize duplicates across connected SKUs.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Products → Variant Attributes is not a blank attribute library and does not create Size, Color, or other reusable choices by itself. It summarizes attributes already stored on product variants. Its Standardize actions write directly to every listed affected variant and rebuild those variant names, so review product and variant counts before using them. The approved Harbor & Hearth capture for this route was rejected because the live page displayed a recovery error; no screenshot is substituted.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Plan the attribute model before editing: use stable customer-facing names such as Size, Color, Material, or Comfort and consistent values. Decide which combinations are actually sold, how each will be identified, priced, stocked, labeled, and selected at checkout.",
        "Go to Products → Product Catalog and create or open the parent product. Complete the product-level identity, supplier, pricing, tax, inventory-tracking, and other required settings before relying on inherited variant defaults.",
        "In the product editor’s variant section, enter an Attribute name and choose Add attribute. Add each allowed value under that attribute. Names are matched exactly inside the editor, so avoid alternate casing, extra spaces, abbreviations, or near-duplicates.",
        "Add additional attributes only when every generated cross-combination is meaningful. CentriPOS automatically builds the Cartesian product of all nonempty attribute value lists—for example, three Sizes and two Colors create six variant rows. Review the resulting count before saving.",
        "Rename an attribute or value carefully. The editor updates affected draft attribute keys/values and rebuilds variant display names from the nonempty values. Removing a value regenerates the combination list; removing the final value removes the attribute. Confirm no legitimate combination or existing variant detail was unintentionally dropped.",
        "Review every generated variant row. Set a unique SKU and vendor code as required, Vendor Cost, Retail, and the On switch. Sync vendor code to SKU copies nonblank vendor codes into SKU and disables direct SKU editing while selected; use it only when those identifiers are intentionally identical.",
        "Expand each variant to manage its barcode and supported detail, bundle, and per-location inventory fields. Confirm stock on hand, reorder point, and reorder quantity when inventory tracking applies. Variant-level cost can be restricted when that variant is a bundle.",
        "Save the product and wait for success. Reopen it to confirm the exact combinations and identifiers persisted. Then test the product in Register → Sell: search or choose the product, use the variant picker, and confirm disabled variants are unavailable and the selected SKU, attributes, price, barcode, and inventory behavior are correct.",
        "To audit catalog-wide consistency, go to Products → Variant Attributes. Read the headline counts for attributes, values, and cleanup candidates. Search by attribute, value, product, or SKU; the query is reflected in the URL so filtered views can be revisited.",
        "Review Duplicate Attribute Names. Candidates differ only by normalized casing or whitespace, such as Size versus size. Read every source label and the affected variant/product counts, enter the exact canonical attribute name, and choose Standardize only when they truly represent the same concept.",
        "Review Duplicate Variant Values separately. These candidates differ only by casing or whitespace under the same normalized attribute family. Enter the intended canonical value and choose Standardize only when the meanings are identical. Do not merge business-distinct choices merely because their spelling looks similar.",
        "Understand the write before confirming: attribute-name Standardize rewrites the matching key on every affected product variant, preserves the first value encountered under the target key, and rebuilds each variant name from its remaining attribute values. Value Standardize rewrites the matching value and also rebuilds the variant name. The update runs variant by variant and is not presented as a preview or undoable batch.",
        "After Attribute names standardized or Variant values standardized appears, wait for products to reload. Expand the affected attribute card, review its value/product/variant counts, use View all products or View products, and inspect representative products and SKUs. Test search, Sell variant selection, labels, dynamic quick picks, reporting filters, and online/integration behavior that depends on the changed label.",
        "If a batch fails or produces an unexpected result, stop further standardization. Record the canonical label, original spellings, affected products/SKUs, time, and error. Correct individual products deliberately or escalate rather than repeatedly applying another bulk label."
      ],
      "controls": [
        {
          "name": "Attribute name",
          "description": "Key stored on each variant, such as Size or Color; created and edited inside a product, not in a separate reusable library."
        },
        {
          "name": "Attribute value",
          "description": "Choice stored under an attribute key, such as Queen or Blue."
        },
        {
          "name": "Generated combinations",
          "description": "Cartesian product of every nonempty attribute value list in the product editor."
        },
        {
          "name": "Variant row",
          "description": "One sellable combination with its own enabled state, SKU, vendor code, cost, retail, barcode, stock, and supported bundle/detail settings."
        },
        {
          "name": "Sync vendor code to SKU",
          "description": "Copies nonblank vendor codes into SKU and keeps SKU input disabled while enabled."
        },
        {
          "name": "On switch",
          "description": "Controls whether the variant is enabled for supported product-selection workflows."
        },
        {
          "name": "Variant Attributes screen",
          "description": "Catalog-wide summary built from existing product_variants.attributes records; primarily an audit and cleanup surface."
        },
        {
          "name": "Attribute / value / cleanup counts",
          "description": "Headline totals derived from currently loaded products and their variants."
        },
        {
          "name": "Search attributes, values, products, or SKU",
          "description": "Filters the summary and writes q to the route query string."
        },
        {
          "name": "Duplicate Attribute Names",
          "description": "Labels whose trimmed, collapsed-space, lowercase form is the same but whose original spelling differs."
        },
        {
          "name": "Duplicate Variant Values",
          "description": "Value spellings whose normalized form is the same within the same normalized attribute family."
        },
        {
          "name": "Suggested label",
          "description": "Most-used spelling, with alphabetical tie-breaking; it is a suggestion, not proof of the correct business term."
        },
        {
          "name": "Standardize attribute name",
          "description": "Bulk-writes the target key across every listed affected variant and rebuilds variant names."
        },
        {
          "name": "Standardize variant value",
          "description": "Bulk-writes the target value across every listed affected variant and rebuilds variant names."
        },
        {
          "name": "Attribute names standardized / Variant values standardized",
          "description": "Success toast followed by product-query invalidation and reload."
        },
        {
          "name": "Attribute card",
          "description": "Expandable summary of value, product, and variant counts for one exact attribute key."
        },
        {
          "name": "View all products for …",
          "description": "Opens Product Catalog filtered by the selected attribute key."
        },
        {
          "name": "View products",
          "description": "Opens Product Catalog filtered by the exact attribute/value selection."
        },
        {
          "name": "No exact screenshot",
          "description": "The Amelia Grant Harbor & Hearth /catalog/variant-attributes capture was rejected because the live route showed a recovery error. This guide intentionally uses no fabricated or mismatched image."
        }
      ],
      "expectedResult": "The attribute values generate only the intended variants, each variant has a distinct identity and selling configuration, and no duplicate combinations remain.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "categories",
      "url": "https://platform.getcentri.com/centripos/categories",
      "title": "Organize product categories",
      "summary": "Create and nest up to three category levels, set financing and availability policy, and associate one product-label template while accounting for immediate deletion, hidden fields, and nontransactional template updates.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Products → Product Categories uses the Grid 3×3 icon. The list table shows only Name, Level, Parent, Label template, and row actions; it does not display Leasable/Financeable or availability restrictions after save. Category and label-template writes are separate. Delete has no confirmation and does not clean category IDs from label-template settings in this component. The approved Harbor & Hearth route rendered a recovery error, so no screenshot is published.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Product Categories, identified by the Grid 3×3 icon. Confirm the active business and wait for loading to finish. Categories are ordered by sort_order then name; locations, registers, and active product label templates are loaded for the editor.",
        "Treat the loaded table cautiously because the fetch function ignores query errors. An empty “No categories yet” table can appear after a failed categories query, while location/register/template option lists can also silently be empty. Confirm connectivity and another known catalog source before adding records to an unexpectedly empty page.",
        "Read each row’s indented Name, stored Level, resolved Parent name, and label-template name or Default. The table does not show category availability or Leasable/Financeable state, so open the exact row to verify those fields.",
        "Choose Add category to open `/catalog/categories/new`, or choose a row/pencil to open `/catalog/categories/<category ID>`. The editor is route-backed; closing it navigates to the category list.",
        "Enter a required trimmed Name. The page has no visible uniqueness check, description, image, color, slug, status, sort-order editor, search, filter, or drag-and-drop hierarchy control. Use a stable distinct name and verify downstream product/Sell labels.",
        "Choose None (top-level) or a Parent category. Parent choices exclude the current category and categories whose stored level is 3 or higher. Saving computes Level as parent.level + 1, or 1 with no parent, which supports at most three levels through the normal picker.",
        "Do not assume the picker prevents every cycle. When editing, it excludes only the current ID—not that category’s descendants. A level-one category can potentially be assigned beneath its own level-two descendant, producing a circular/inconsistent hierarchy. Map ancestors/descendants first and never select a child or descendant as parent.",
        "Set Leasable / Financeable only under approved financing policy. It defaults on for a new category and when an old row has no is_leasable value. The helper specifically references Katapult lease-to-own eligibility; it does not prove PayTomorrow eligibility, provider approval, customer qualification, or that every product/category consumer enforces it.",
        "Choose Product label template. Store default means this component removes the category ID from every loaded active product label template. Choosing a template means it adds the ID to that template and removes it from every other loaded active product template. This is category-to-template membership stored inside each template’s settings.categoryIds—not a label_template_id column on the category.",
        "Only active templates with template_source `product` appear. A template marked Default can also be selected explicitly and is labeled (Default); this differs from Store default, which selects no specific template association. Products in the category preselect the associated template during supported label printing; verify actual print selection/output.",
        "Use Availability restrictions when at least one location or register loaded. Available everywhere stores both available ID arrays as null. Only selected locations stores a normalized location-ID array and null registers; Only selected registers stores a normalized register-ID array and null locations.",
        "For a restricted scope, choose at least one location/register. Clear empties the draft and Save is blocked until an allowed target is selected or scope returns to Available everywhere. Switching scope clears the IDs from the other scope immediately in the draft.",
        "Register choices show register name and available location name; confirm both. A register restriction is more specific than a location restriction and does not automatically include other registers at that location. Category policy combines with product, register, location, tenant, and channel availability rules.",
        "Choose Add category or Save once. The category row write happens first. For a new category, sort_order becomes the current maximum plus one. For an edit, name, parent, computed level, leasable state, and availability arrays are updated.",
        "After the category row succeeds, CentriPOS concurrently updates every loaded active product label template whose category membership must change. These template updates are not one transaction and can partially succeed. If one fails, the category remains created/updated and the page reports that the label template did not update; the dialog remains open.",
        "After a template partial-failure warning, do not click Save repeatedly. Inspect the category row and every relevant template’s categoryIds because the category can temporarily belong to multiple templates or none. Reconcile with a controlled authorized fix and record before/after membership.",
        "On full success, wait for Category added or Category updated, then the dialog closes and all four lists refetch. Reopen the exact category to verify hidden Leasable and availability values; verify its row Name/Level/Parent/Label template and confirm one intended template association only.",
        "Assign the category on representative products, then test Sell at an allowed and disallowed location/register, POS/online availability as applicable, a Katapult-eligible test cart if authorized, and product-label template preselection/print. Do not use a real financing applicant merely to test the category flag.",
        "Use Trash only after mapping assigned products, direct child categories, deeper descendants, availability, financing behavior, labels/templates, saved carts, online store, reports, integrations, and network/master catalog. The button immediately sends a hard delete with no confirmation dialog.",
        "Deletion can fail due to database dependencies; the raw error is shown. On success it says Deleted, logs a category_deleted activity request, and refetches. This component does not remove the deleted category ID from label_templates.settings.categoryIds, so audit and clean stale membership through an authorized process. There is no restore control.",
        "No screenshot is published. The real Amelia Grant Harbor & Hearth `/catalog/categories` inspection rendered “This view needs a refresh”; the error-state capture was rejected rather than represented as a working list or replaced with another screen."
      ],
      "controls": [
        {
          "name": "Grid 3×3 icon",
          "description": "Exact CentriPOS Products navigation icon for Product Categories."
        },
        {
          "name": "Name",
          "description": "Required trimmed category name with no visible uniqueness check."
        },
        {
          "name": "Level",
          "description": "Stored/computed hierarchy depth shown in the table."
        },
        {
          "name": "Parent",
          "description": "Optional category with stored level below 3; descendants are not excluded automatically."
        },
        {
          "name": "Three levels",
          "description": "Normal picker/computation supports levels 1–3."
        },
        {
          "name": "Cycle risk",
          "description": "Editor excludes self but not descendants; never parent a category beneath its child."
        },
        {
          "name": "Leasable / Financeable",
          "description": "Katapult-oriented stored category flag, hidden from the list after save."
        },
        {
          "name": "Store default",
          "description": "No specific active product-template category association."
        },
        {
          "name": "Explicit template",
          "description": "Category ID stored in one template settings.categoryIds and removed from others."
        },
        {
          "name": "Default template label",
          "description": "An explicitly selectable active template whose is_default flag is true; distinct from Store default."
        },
        {
          "name": "Available everywhere",
          "description": "Both availability ID arrays stored null."
        },
        {
          "name": "Only selected locations",
          "description": "Normalized allowed location IDs; requires at least one."
        },
        {
          "name": "Only selected registers",
          "description": "Normalized allowed register IDs; requires at least one."
        },
        {
          "name": "Clear",
          "description": "Empties restricted IDs and blocks Save until a target or Everywhere is chosen."
        },
        {
          "name": "Add / Save",
          "description": "Category row write followed by concurrent label-template membership updates."
        },
        {
          "name": "Partial template failure",
          "description": "Category persists while one or more separate template writes may have succeeded/failed."
        },
        {
          "name": "Sort order",
          "description": "New category receives current maximum sort_order + 1; no manual reorder UI."
        },
        {
          "name": "Table boundary",
          "description": "Shows Name, Level, Parent, and Label template only—not availability or leasable state."
        },
        {
          "name": "Trash",
          "description": "Immediate hard delete with no confirmation and no restore control."
        },
        {
          "name": "Stale template category ID",
          "description": "Delete does not clean label-template settings in this component."
        },
        {
          "name": "Silent load errors",
          "description": "Queries ignore returned errors and can render empty option/list states."
        },
        {
          "name": "No public screenshot",
          "description": "Rejected real Harbor & Hearth recovery-error capture; no substitute or fabrication."
        }
      ],
      "expectedResult": "The category appears once in a noncircular level-1-to-3 hierarchy; hidden leasable and location/register availability values are reopened and verified; exactly the intended active product-label template contains its ID after the separate nontransactional writes; representative products behave correctly in Sell, financing, and label printing; and no stale template membership or dependency remains after an authorized deletion.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "price-books",
      "url": "https://platform.getcentri.com/centripos/price-books",
      "title": "Create and use Customer Price Books",
      "summary": "Build targeted customer pricing, organize product and variant lines, bulk-edit prices, and create printable or PIN-protected customer sheets and online order forms.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Open Products → Customer Price Books using the Book Open icon. A price list must target at least one location, customer group, specific customer, or association/company. CentriPOS has no editable Priority field: in-store pricing resolves specific customer first, then association, then group, then location-only. Avoid overlapping active books at the same tier because their winner is not user-controlled.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Open Products → Customer Price Books. The Customer Pricing index shows Active lists, Products connected, Saved forms, and Online submissions across the business.",
        "Review each Price lists row before editing. It shows Active or Inactive, channel, last update, up to five Valid for chips plus a more count, unique product/variant count, total rows, saved forms, active links, start and end dates, and order-submission count.",
        "Choose New price list. Enter a required Price list name, then choose Channel: In-store, Online, or In-store & online. The Sell pricing engine uses only In-store and In-store & online books.",
        "Set Valid from and Valid to when the pricing is time-limited, or leave either side blank for no boundary. Confirm the dates yourself before saving; the current editor does not visibly enforce that the end follows the start.",
        "Set the target. Locations restrict the book to those operating locations. With locations but no customer, association, or group target, the book acts as location retail pricing for everyone there.",
        "Choose Customer groups for members of one or more groups. Choose Specific customers when a list belongs directly to one customer. Choose Associations / companies to apply it to every customer attached to that household or company association. These targeting types can be combined with Locations to require the current location too.",
        "Understand in-store precedence before creating overlaps: a direct customer match ranks above an association match, association above customer group, and group above a location-only book. There is no Priority control. If two active books provide the same product at the same rank, do not assume which one will win; remove the overlap or make the scope unambiguous.",
        "Turn Active on only when the scope, dates, channel, and line prices are ready. Inactive, future, expired, and Online-only books do not override prices in the in-store Sell cart.",
        "In Products, open Add from catalog and search by product name or SKU. Add a simple product directly. For a variable product, choose Add all or Pick to select the intended variants. A base product and a variant are separate price-list keys.",
        "Use the section-heading tools to organize customer sheets. Create formatted custom headings, save reusable headings, apply a heading to filtered or selected lines, or generate sections from category, brand, or vendor. Deleting a reusable heading does not substitute for reviewing the lines already assigned to it.",
        "Use Product table to switch among All products, Group by header, and Reorder. Filter by name or SKU, Brand, Category, Tag, Supplier, or Header. Reorder mode lets you drag headings and move product groups into a heading.",
        "Choose Cost basis when more than one supported vendor or cost list is available. Supply price is an internal calculation basis; sharing internal cost columns is a separate explicit Print / share choice and should remain off for customer-facing material.",
        "Edit each product or variant line’s retail price, markup, discount, margin, optional minimum and maximum units, section, sort order, and customer-facing line note. Variant-specific pricing is checked before the product-level price.",
        "Use Bulk update to apply a Markup % or Discount % to the currently represented line set, then inspect the resulting retail values. A bulk calculation is not a substitute for checking cost basis, rounding, and margin.",
        "Use Export CSV before a large external edit. Import CSV requires a sku or id column and a retail_price column; it updates matching entries and can add resolved catalog entries while reporting skipped or unmatched rows. Review the in-memory table, then choose Save Pricing to persist it.",
        "Choose Save Pricing. CentriPOS requires a name and at least one location, customer group, customer, or association. Wait for Pricing saved and return to the index; unsaved product, assignment, heading, or scope changes are not active.",
        "Attach the intended customer before testing in Sell. Confirm the active business and location, add the exact product or variant, and inspect the price-book indicator. Test one eligible customer and one ineligible customer at the same location.",
        "Open an existing list and choose Duplicate to copy prices, product order, headings, assignments, and saved-form settings. Public links are not reused; create fresh links from the copied book. Rename and review the copy before activating it.",
        "Choose Print / share or New form to create a saved Price sheet, Quantity sheet, or Order form. Configure its name, formatted header, customer, whether prices or authorized internal-review columns appear, table density and width, grouping, headings, store identity overrides, notes, online and print-only fields, signature lines, and writable document layout.",
        "Save distinct customer-facing forms when the same price list needs different layouts or recipients. The Saved customer sheets & order forms panel shows its customer, form type, price/cost visibility, field count, update time, and whether an active link exists. Use Adjust, Print, Copy link, Open, or Delete from that row.",
        "For a public customer link, choose a numeric or alphanumeric PIN. New links require a unique six-character PIN before the sheet opens. Save the form and link, copy the visible PIN separately, and send it only to the intended recipient.",
        "If you Regenerate PIN, save the updated form and give the recipient the new value; the prior PIN no longer represents current access. Email access notice sends the current visible PIN and records a send audit, but it does not prove the recipient opened or completed the form.",
        "Use only the branded public URL generated by CentriPOS. The saved-form row reports Link active or No active link; the current editor does not show an expiration date, last-access timestamp, or a separate Revoke button. If access must be withdrawn without deleting the form, contact CentriPOS support with the price-list and form names—never send the PIN.",
        "Treat Online submissions as customer orders requiring staff review, not automatic proof of inventory, fulfillment, payment, or acceptance. Confirm the submitted quantities, customer identity, fields, pricing version, location, availability, and next operational action.",
        "Delete a price list only when its entries, targeting, saved forms, and historical operational references have been reviewed. Deletion removes the price book and its configuration; using Inactive is safer when pricing should merely stop applying."
      ],
      "controls": [
        {
          "name": "Book Open icon",
          "description": "Navigation icon for Products → Customer Price Books."
        },
        {
          "name": "Customer Pricing index",
          "description": "Business-wide summary of active lists, connected products, saved forms, online submissions, and every price-list row."
        },
        {
          "name": "Valid for",
          "description": "Customer, Group, Association, and Location chips representing saved targeting links. No chips means the row has no specific target summary and should be reviewed before use."
        },
        {
          "name": "Products / rows",
          "description": "Products counts unique product-or-variant keys; rows counts every saved price-book entry."
        },
        {
          "name": "Channel",
          "description": "In-store, Online, or In-store & online. Only the two in-store-capable values participate in the current Sell pricing resolver."
        },
        {
          "name": "Valid from / Valid to",
          "description": "Optional start and end boundaries. A blank side has no boundary."
        },
        {
          "name": "Locations",
          "description": "Restricts applicability to selected locations; location-only targeting can provide alternate retail pricing for everyone there."
        },
        {
          "name": "Customer groups",
          "description": "Targets customers currently linked to any selected group."
        },
        {
          "name": "Specific customers",
          "description": "Highest-ranked in-store customer targeting and does not require a one-person group."
        },
        {
          "name": "Associations / companies",
          "description": "Targets customers attached to a selected company or household association."
        },
        {
          "name": "Precedence",
          "description": "Specific customer, then association/company, then customer group, then location-only. No editable Priority field exists."
        },
        {
          "name": "Active",
          "description": "Required for the price book to participate in supported pricing or current customer-facing use."
        },
        {
          "name": "Add from catalog",
          "description": "Searches by product name or SKU and adds a simple product, selected variants, or all variants."
        },
        {
          "name": "Section headings",
          "description": "Formatted custom or reusable headings used to organize printed sheets and forms; smart sections can follow category, brand, or vendor."
        },
        {
          "name": "All products / Group by header / Reorder",
          "description": "Changes the product-table working view and enables drag-based heading or line organization."
        },
        {
          "name": "Cost basis",
          "description": "Selected supported supply-cost source used for markup, margin, and retail calculations."
        },
        {
          "name": "Retail price",
          "description": "Override price stored for the product or variant line. A variant-specific override is checked before its product-level fallback."
        },
        {
          "name": "Markup / Discount / Margin",
          "description": "Related pricing calculations for a line. Review the resulting retail value after editing any of them."
        },
        {
          "name": "Min / Max units",
          "description": "Optional quantity boundaries stored with the price override and exposed to supported price-list/order workflows."
        },
        {
          "name": "Line note",
          "description": "Optional customer-facing note printed or shown beneath that item in supported sheets and forms."
        },
        {
          "name": "Bulk update",
          "description": "Applies entered markup or discount values to the current working line set; verify every resulting price."
        },
        {
          "name": "Export CSV",
          "description": "Downloads the current price-list entries for controlled bulk editing."
        },
        {
          "name": "Import CSV",
          "description": "Requires sku or id plus retail_price; updates matches, adds resolvable entries, and reports skipped or unmatched rows."
        },
        {
          "name": "Save Pricing",
          "description": "Persists details, entries, targeting links, and heading order after required name and target validation."
        },
        {
          "name": "Duplicate",
          "description": "Copies the price list, entries, ordering, headings, targeting, and form settings but creates no reusable public access link."
        },
        {
          "name": "Print / share",
          "description": "Builds or edits a printable price sheet, quantity sheet, or order form and its optional protected public link."
        },
        {
          "name": "Saved form",
          "description": "Reusable customer-facing document configuration with its own layout, recipient, fields, price/cost visibility, and link state."
        },
        {
          "name": "Internal review columns",
          "description": "Optional cost-related columns for authorized internal output; leave them out of customer-facing forms."
        },
        {
          "name": "Link access PIN",
          "description": "Unique six-character numeric or alphanumeric code required by new public customer links."
        },
        {
          "name": "Regenerate PIN",
          "description": "Creates a replacement PIN that must be saved and redistributed securely."
        },
        {
          "name": "Email access notice",
          "description": "Sends the current visible PIN through the supported email workflow and records the attempt."
        },
        {
          "name": "Active link",
          "description": "Current nonrevoked, nonexpired public link. The editor reports only active or not active; it does not expose expiry, last access, or a dedicated revoke control."
        },
        {
          "name": "Online submissions",
          "description": "Submitted customer order-form records awaiting staff review; not automatic acceptance, payment, inventory reservation, or fulfillment."
        },
        {
          "name": "Inactive",
          "description": "Stops the list from current pricing eligibility while preserving its configuration for later review."
        },
        {
          "name": "Delete",
          "description": "Permanently removes the price book after confirmation; use carefully when saved forms or submissions exist."
        }
      ],
      "expectedResult": "The saved price list has an unambiguous customer, association, group, and/or location scope; the intended channel and date window; reviewed product or variant prices and quantity rules; no same-rank conflict; and eligible and ineligible Sell tests resolve differently according to specific-customer → association → group → location precedence. Any customer form exposes only approved columns through a branded, current, PIN-protected link, and submissions remain pending staff review.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "product-images-warranties",
      "url": "https://platform.getcentri.com/centripos/product-images-warranties",
      "title": "Manage product images, video, and warranty PDFs",
      "summary": "Upload, order, select, remove, and verify product media plus the branded warranty attachment used by staff and supported label/customer surfaces.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "Images & Video and Warranty live inside the exact product editor but save differently. Gallery media requires an already-saved product and uploads immediately; it is not waiting for the main product Save. A new Warranty PDF is queued locally and uploads only during the main Save. The gallery’s upload, primary, delete, and reorder operations perform multiple storage/database calls with limited error checking, while warranty storage and product attachment are also separate writes. Verify the live product after every change.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products and open the exact product. Confirm name, product/variant identity, and SKU before changing media. Product media belongs to the parent product; variants can associate an existing parent product image elsewhere, but this gallery does not upload a separate variant-owned file.",
        "For a brand-new unsaved product, Images & Video shows Save the product first to upload images and videos. Complete the required product identity and choose Save. Reopen the saved product before uploading so every storage object has the intended product ID.",
        "Choose Upload media or the empty gallery upload area. Despite the empty-state text saying Click or drag, this component has no file-drop handler on that area; use the file picker. Multiple files can be selected in one picker action.",
        "Each accepted image/* file may be at most 2.5 MB and each video/* file at most 50 MB. Other MIME types and oversized files show an error for that file and the loop continues with later selected files. The current accepted image extensions are described as JPG, PNG, and WebP, while actual validation accepts any browser-provided image/* MIME type.",
        "Uploads write to the product-media storage bucket under tenant/product/timestamp-index, then insert a product_images row with public URL and sort order. A storage failure is reported and skipped. The following database insert result is not checked, so a file can upload without a gallery row. Media uploaded is a batch-level toast, not proof every selected file succeeded.",
        "When the gallery was empty at the start, the first selected file is marked Primary. Because the whole batch uses the original images array, only batch index zero gets that flag. Reopen/refetch and confirm exactly one intended primary.",
        "Hover a nonprimary card and choose the Star to make it Primary. CentriPOS first clears Primary on every product image, then sets the chosen row. Neither update result is checked and the two writes are not atomic; a failure can leave no primary or the wrong primary. Verify the badge and downstream surface before leaving.",
        "Drag a media card onto another card and release to reorder. The editor updates changed sort_order rows one by one. Returned update errors are not inspected and there is no optimistic preview retained after the query refresh; verify the final sequence. The upload area itself is not a drop target for new files.",
        "Hover a card and choose Trash only after identifying the exact image/video. There is no confirmation. CentriPOS first attempts to remove the storage object parsed from its URL, then deletes the product_images row. Neither result is checked; the Deleted toast can appear even if one side failed. Verify both the gallery and a fresh public/storage request through support when cleanup matters.",
        "Video display is inferred from the URL extension mp4, webm, mov, or avi. A video with another accepted video MIME/extension can upload but be rendered like an image because the gallery’s display test is extension-based. Test the saved video card and every intended customer/staff surface rather than assuming upload means playback support.",
        "In Warranty, enter a customer-readable Warranty label and select an application/pdf file. The visible input uses the browser’s PDF accept hint, but this form does not independently validate PDF contents or impose a file-size limit before upload. Use a trusted, product-only PDF with no customer or confidential vendor information.",
        "A selected file card says Uploads when the product is saved. The pending filename is used as the fallback warranty label when the entered label is blank. Choose the main product Save once; do not confuse media’s immediate upload with the warranty’s deferred upload.",
        "The main Save first writes the product base fields and relationships. It then uploads the warranty file to product-warranties under tenant/product/timestamp-safe-filename and separately updates warranty path, branded absolute attachment URL, and label on the product. If attachment update fails after storage succeeds, an orphaned file can remain. Preserve the error and product ID rather than repeatedly uploading.",
        "After success, reopen the product. The stored Warranty card shows the label and Open action. Open uses the branded product-warranty attachment route derived from the saved storage path; confirm it resolves through the branded CentriPOS host, downloads/opens the intended PDF, and uses the correct readable filename/label.",
        "Clear removes the pending file and clears the saved path/URL from form state. Choose the main Save to persist clearing an existing attachment. The current clear/save path removes the product reference but does not delete the old object from product-warranties, so request authorized storage cleanup when retention policy requires physical deletion. Changing only the Warranty label while retaining a path rebuilds the branded attachment URL on Save.",
        "Open Product Quick View for the exact product. Warranty appears when a label or attachment exists; Open warranty appears only with a resolvable attachment. On product label printing, hasWarranty is true for a label or stored path/URL and Warranty / AS IS resolves to the warranty label/fallback versus AS IS. Print one controlled label when this field is operationally required.",
        "Verify the intended primary/order in Sell, product quick view, and any enabled online/customer channel. WooCommerce Product Images are a separate pass-through whose files are hosted on WordPress; do not assume this native product-media gallery automatically proves WooCommerce order or hosting state.",
        "For a discrepancy, record tenant, product ID/SKU, media row ID, exact file name/type/size, storage path/public URL, primary flag, sort order, warranty path/branded URL/label, action time, and toast/error. Avoid repeating uploads or deletes until storage and database sides are reconciled.",
        "No screenshot is published for this guide. The approved Harbor & Hearth capture set has a real Products list but no exact open Images & Video or Warranty editor state. A list screenshot would not demonstrate these controls, so it is not substituted or fabricated."
      ],
      "controls": [
        {
          "name": "Saved product required",
          "description": "Native gallery media needs an existing product ID."
        },
        {
          "name": "Upload media",
          "description": "Immediate multi-file picker upload; the displayed drop-area text is not backed by a drop handler."
        },
        {
          "name": "Image limit",
          "description": "2.5 MB per accepted image/* file."
        },
        {
          "name": "Video limit",
          "description": "50 MB per accepted video/* file."
        },
        {
          "name": "Per-file continuation",
          "description": "Unsupported, oversized, or failed storage files are skipped while later selected files continue."
        },
        {
          "name": "Media uploaded",
          "description": "Batch-level toast; not proof every storage upload and row insert succeeded."
        },
        {
          "name": "Primary",
          "description": "product_images flag; first file of an initially empty batch is primary."
        },
        {
          "name": "Star",
          "description": "Nonatomic clear-all then set-one primary operation with unchecked results."
        },
        {
          "name": "Media order",
          "description": "Drag/release sequential sort_order updates with unchecked results."
        },
        {
          "name": "Trash",
          "description": "Immediate storage-remove then row-delete without confirmation or checked results."
        },
        {
          "name": "Extension-based video rendering",
          "description": "Only mp4/webm/mov/avi URLs are detected as video by this gallery."
        },
        {
          "name": "Warranty label",
          "description": "Customer/staff-readable label and fallback attachment filename."
        },
        {
          "name": "Warranty PDF",
          "description": "Browser-hinted application/pdf pending file uploaded during main product Save."
        },
        {
          "name": "Warranty storage boundary",
          "description": "Storage upload followed by separate product attachment update; partial orphan is possible."
        },
        {
          "name": "Open",
          "description": "Branded warranty attachment route for the stored product path."
        },
        {
          "name": "Clear",
          "description": "Clears pending/stored references in form; main Save required and old storage object is not deleted."
        },
        {
          "name": "Product Quick View",
          "description": "Shows label and Open warranty when the attachment resolves."
        },
        {
          "name": "Warranty / AS IS label data",
          "description": "Warranty presence/label passed into supported product-label printing."
        },
        {
          "name": "WooCommerce boundary",
          "description": "Separate WordPress-hosted image pass-through, not this native product-media gallery."
        },
        {
          "name": "No public screenshot",
          "description": "No exact approved open media/warranty editor capture; no list substitution."
        }
      ],
      "expectedResult": "The exact parent product owns the intended media rows and storage objects; one verified primary and the saved sort order render correctly on supported surfaces; video type/playback is tested; warranty path, branded attachment URL, label, quick-view action, and Warranty / AS IS label data agree; and any partial storage/database upload, deletion, reordering, clearing, or orphaned object is reconciled before repeating an action.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "labels",
      "url": "https://platform.getcentri.com/centripos/labels",
      "title": "Print product and sale-item labels",
      "summary": "Generate catalog price labels or receipt-specific sold-item tags with the correct template, target SKU, encoded scan value, override behavior, copy count, and physical printer settings.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Products",
      "introduction": "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.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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."
      ],
      "controls": [
        {
          "name": "Product label workflow",
          "description": "Saved Product → Labeling & Shipping custom-label generation."
        },
        {
          "name": "Active Product templates",
          "description": "Only active label_templates with template_source product."
        },
        {
          "name": "Automatic template priority",
          "description": "Category match, then default, then first; built-in only when none exist."
        },
        {
          "name": "Template dimensions/offsets",
          "description": "Stored size/design/background with safe fallbacks and ±1-inch offset clamp."
        },
        {
          "name": "Product label",
          "description": "Parent-level data and parent code priority."
        },
        {
          "name": "All SKUs",
          "description": "Every enabled variant times copy quantity."
        },
        {
          "name": "Specific SKU",
          "description": "One enabled variant target."
        },
        {
          "name": "Label pages",
          "description": "Digits-only input parsed/clamped to at least one physical copy per target."
        },
        {
          "name": "Code priority",
          "description": "Primary-for-label, primary-for-scanning, active/barcode/SKU fallbacks scoped to parent or variant."
        },
        {
          "name": "One-off sale price",
          "description": "Nonnegative scan/print override, not product retail-price edit."
        },
        {
          "name": "Compare at",
          "description": "Explicit comparison price or regular-price fallback when sale override exists."
        },
        {
          "name": "Print callout",
          "description": "Override text that also triggers an override scan code."
        },
        {
          "name": "label_scan_overrides",
          "description": "One unique persisted override row per physical override-label copy."
        },
        {
          "name": "Override partial state",
          "description": "Rows can remain when print-window opening later fails."
        },
        {
          "name": "Warranty / AS IS",
          "description": "Derived from product warranty label/path/URL for supported product templates."
        },
        {
          "name": "Browser print window",
          "description": "External printer/media/margin/scale selection; pop-ups required."
        },
        {
          "name": "Print sale labels",
          "description": "Receipt-specific fixed sold-item template, separate from Product templates."
        },
        {
          "name": "Returned-line exclusion",
          "description": "Sale lines with is_return true do not appear."
        },
        {
          "name": "Unchecked defaults",
          "description": "Every eligible receipt line starts unselected."
        },
        {
          "name": "Receipt-line quantity default",
          "description": "Initial copies equal at least one sale quantity."
        },
        {
          "name": "Selected label count",
          "description": "Sum of requested copies for checked lines."
        },
        {
          "name": "Sold-label Amount Due",
          "description": "Current whole-sale balance_due, not individual line price."
        },
        {
          "name": "Sold-label date",
          "description": "Sale fulfillment_date or current local date fallback."
        },
        {
          "name": "Sold-label barcode",
          "description": "Line barcode then SKU fallback."
        },
        {
          "name": "Remarks / notes",
          "description": "Print-job-only notes; no receipt/product mutation."
        },
        {
          "name": "No public screenshot",
          "description": "No exact approved label-panel/dialog/print capture; no substitute."
        }
      ],
      "expectedResult": "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "lightning-layouts",
      "url": "https://platform.getcentri.com/centripos/lightning-layouts",
      "title": "Build Lightning Layouts",
      "summary": "Create, assign, organize, test, and safely maintain register-specific manual or dynamic product grids for faster selling.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Register",
      "introduction": "Register → Lightning Layouts uses the exact LayoutGrid icon. Any signed-in user can view assigned/visible layout cards and star personal favorites, but only owners or users with Manage Lightning Layouts can create, edit, assign, or delete. Layouts reference existing catalog records and are filtered again in Sell by active product, location/register availability, and availability rules. Saving a layout spans metadata, folder/item upserts/deletes, and register-assignment writes rather than one transaction; test the exact register after every structural change.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Register → Lightning Layouts, identified by the LayoutGrid icon. A user without management permission sees the list/favorite controls and the message about starring favorites; opening an editor URL shows Access denied.",
        "Search layouts matches layout name in the already loaded list. The register filter matches a layout when it is assigned to any selected register. Its register list is loaded from all tenant locations for this list view; selecting multiple registers uses any-match, not “assigned to every selected register.”",
        "Each card shows name, grid columns × rows, assigned-register count, and distinct location names, or Unassigned. Star is personal to the current user and orders Favorites first in the Sell switcher; it does not assign a register, change another user, or establish a default.",
        "Choose New Layout only when authorized. Enter a nonblank name and Create. The new record starts as a 3×3 layout with no register assignment, folders, or product cells, then opens in the editor. Creation does not make it available on Sell until the appropriate assignment is saved.",
        "The card trash control is manager-only but issues layout deletion immediately with no confirmation dialog. Dependent folders, items, assignments, and favorites can be removed by database relationships. Audit register use and obtain approval before choosing it; there is no visible undo.",
        "In the editor, change the layout name, Columns, and Rows. Grid size controls the visible cell matrix at each folder level. Before shrinking it, move or remove content that would sit outside the new boundary; verify all levels after Save rather than assuming off-grid cells were automatically reorganized.",
        "Assign Registers from the editor. Owners/admin-equivalent location scope can load active locations across the tenant; other users receive only their scoped location IDs. The query returns registers at those locations and does not add an explicit active-register condition. Select only registers whose teams and screen sizes have been tested.",
        "Choose Add Product and search by parent product name or SKU; the candidate list is capped at the first 50 filtered products. For a variable product, choose Entire product or a specific supported variant when prompted. A product cell stores product ID and optional variant ID; it does not copy price, stock, tax, or availability into the layout.",
        "Use Rename/Edit Product Cell for an optional button label and color/size controls supported by the editor. A custom label changes only this layout cell, not product/variant identity. Confirm the Sell tile still resolves the expected catalog record.",
        "Create a manual Folder with required name and color. It can hold product cells and nested manual folders. Use the breadcrumb/Main layout navigation to edit each level. A dynamic folder is filter-driven and does not behave like a manual container for placed children.",
        "Drag a product or folder to an empty cell to move it. Drop a product/folder onto a manual folder to place it at that folder’s next available position. Dropping a product onto another product offers a new folder containing both. Review destination level and occupied cells before releasing.",
        "Dynamic Folder criteria can include exact products, variants, brands, categories, suppliers, tags, variant attribute values, and optional target price with range, depending on the dialog entry point. It queries a capped option set (up to 500 active products and 1,000 variants in the shared dialog); absent options are not proof the catalog has none.",
        "At Sell time, dynamic-folder brand/category/supplier/tag/variant-value and price criteria are passed into the same ranked product/variant selection logic with active location, register, and availability rules. Contents can change as catalog metadata, price, availability, or stock context changes; it is not a frozen snapshot. Exact productIds/variantIds saved by some shared-dialog paths are not included in the Sell grid’s current folderFilters object, so verify those criteria in the target register rather than trusting the chip alone.",
        "Delete a cell or folder only after inspecting the current level and descendants. Removing a layout item does not delete its catalog product. Removing a folder removes that organizational record and can remove/cascade contained layout records according to database relationships; Save is the persistence point for editor removals.",
        "Choose Save once. The save operation first updates layout name/grid size without checking that update’s returned error, reads existing records, upserts current folders/items, deletes removed items/folders, then adds/removes register assignments. It is sequential, not atomic; later failure can leave earlier metadata/content changes saved. Reopen and compare every level and assignment after an error.",
        "Unsaved Changes protects the editor Back action, browser history/popstate, and tab close/reload differently. Discard clears dirty state and leaves. Save & Exit calls the caught-error save handler and then navigates even if that handler displayed Failed to save lightning layout, so do not assume remaining on the page is the success test. Reopen and verify after Save & Exit.",
        "Go to Register → Sell in an assigned register and enter Lightning Layout Mode. If more than one available layout exists, the switcher appears; favorites are grouped first, other layouts second, active has a check, and Default labels the layout returned as the active/default register layout. The Lightning Layout editor itself has no Set default control.",
        "Open every manual and dynamic folder and test representative standard/variant cells. Static cells are suppressed when the linked product is missing or disallowed at the active location/register. Dynamic results are likewise re-ranked/filtered. A tile can therefore exist in the editor but not appear or add in Sell.",
        "Choose a static product with variants carefully: a product-level cell can invoke variant selection, while a variant-specific cell should resolve that variant. Confirm price, tax, fulfillment, availability, and stock behavior in the resulting cart; the layout never bypasses those workflows.",
        "Verify desktop and target touch devices. Grid positions, spans, scroll state per folder, breadcrumbs, names, and dynamic result density can behave differently by viewport. Do not solve a layout-density issue by changing catalog availability or product data.",
        "For troubleshooting record tenant, user permission/location scope, layout ID/name/grid, folder/item IDs and parent/positions/spans, dynamic criteria, register assignments, active location/register, favorite/default/active IDs, missing catalog ID, availability rules, Save toast/error, and exact Sell result.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth `/register/lightning-layouts` route ended at Could not load Lightning Layouts, so the rejected error capture is not shown as a valid layout and no different screen is substituted."
      ],
      "controls": [
        {
          "name": "LayoutGrid icon",
          "description": "Exact Register navigation and empty-state icon for Lightning Layouts."
        },
        {
          "name": "Manage Lightning Layouts",
          "description": "Permission required to create/edit/assign/delete; owners also qualify."
        },
        {
          "name": "Search layouts",
          "description": "Client-side name match across loaded layouts."
        },
        {
          "name": "Register filter",
          "description": "Any selected assigned register match."
        },
        {
          "name": "Layout card",
          "description": "Name, grid dimensions, assignment count/locations, personal star, and manager delete."
        },
        {
          "name": "Favorite",
          "description": "Current-user preference and Sell switcher grouping only."
        },
        {
          "name": "New Layout",
          "description": "Creates unassigned empty 3×3 layout."
        },
        {
          "name": "Immediate card deletion",
          "description": "No confirmation or visible undo."
        },
        {
          "name": "Columns / Rows",
          "description": "Per-level visible grid boundary."
        },
        {
          "name": "Assign Registers",
          "description": "Scoped register availability; not default selection."
        },
        {
          "name": "Product cell",
          "description": "Product ID plus optional variant ID and layout-only presentation."
        },
        {
          "name": "50-product add search",
          "description": "First 50 name/SKU matches in editor."
        },
        {
          "name": "Manual folder",
          "description": "Placed/nested layout container."
        },
        {
          "name": "Dynamic folder",
          "description": "Live filter criteria evaluated against current Sell catalog/context."
        },
        {
          "name": "Dynamic option caps",
          "description": "Shared dialog loads up to 500 active products and 1,000 variants."
        },
        {
          "name": "Exact-ID criteria caveat",
          "description": "Sell grid currently forwards attribute/price criteria but not saved productIds/variantIds in its folderFilters object."
        },
        {
          "name": "Drag/drop",
          "description": "Move to cell/folder or merge product-on-product into a new folder."
        },
        {
          "name": "Save boundary",
          "description": "Unchecked metadata update, then sequential content and assignment operations."
        },
        {
          "name": "Unsaved Changes",
          "description": "Discard or Save & Exit; Save & Exit can navigate after a caught save failure."
        },
        {
          "name": "Layout switcher",
          "description": "Shown only with more than one available layout; active/check, favorite grouping, and Default label."
        },
        {
          "name": "No editor Set default",
          "description": "Default comes from active register-layout resolution, not a control on this screen."
        },
        {
          "name": "Sell revalidation",
          "description": "Product/variant and dynamic results remain subject to active catalog/location/register availability."
        },
        {
          "name": "No public screenshot",
          "description": "Rejected real error-state capture; no substituted or fabricated image."
        }
      ],
      "expectedResult": "The exact layout name/grid, every folder/item identity and position/span, manual hierarchy, dynamic criteria, scoped register assignments, and current-user favorite state are reopened after save; the target register’s active/default/switcher behavior is understood; representative standard and variant tiles remain correctly filtered by catalog/location/register availability; and any partial sequential save or Save & Exit failure is reconciled before further edits.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "custom-items",
      "url": "https://platform.getcentri.com/centripos/custom-items",
      "title": "Create and review Custom Items safely",
      "summary": "Use one-off product records for exceptional sale lines, understand their sold-status lifecycle, and keep them out of regular inventory and purchasing workflows.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Custom Items",
      "introduction": "Custom Items uses the Archive icon. These records live in the products table with product_type custom, but they are intentionally outside regular master inventory, purchase orders, and receiving. Register-created custom items are non-inventory, POS-only, and offline-only. A completed sale marks them Sold; supported return/exchange or receipt reversal paths can reactivate them. Manual status buttons do not validate the related receipt, so never reactivate and resell a genuinely sold one-off item without reconciliation.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Custom Items. Wait for the loading state to finish. The subtitle counts every custom product in the current business before search or status filtering, not only the visible matches.",
        "Open the information icon beside Custom Item Archive. Its product guidance is the governing boundary: custom items are miscellaneous one-off records with cost history on the customer receipt, not regular master inventory and not available for PO or receiving workflows.",
        "Use Search custom items… to filter the already-loaded tenant list by product Name or SKU only. Search is client-side and case-insensitive; it does not inspect description, customer, receipt, price, cost, dates, brand, categories, tags, or sale number.",
        "Choose All, Active, Inactive, or Sold. These buttons compare sold_status, not sale status or inventory availability. The table shows Item, Cost, Price, Status, Created date, and row actions.",
        "For the fastest register flow, open Sell and choose Custom Item. Enter required Item name and a Sell price greater than zero; optional Cost supports margin history. Add to Cart creates a product_type custom row with inventory tracking off, POS selling on, online selling off, and sold_status Active, then adds it to the current cart.",
        "If creating from the archive, choose Add Custom Item. This opens the full Product editor as Add Custom Item Product. Saving creates the custom product record but does not automatically add it to a Sell cart. Review its name, pricing/cost, tax treatment, labels, and other entered fields before later using it.",
        "Distinguish the two creation paths before retrying. Register Custom Item creates the database record before calling Add to Cart; if cart insertion or the surrounding workflow is uncertain, search the archive before creating another duplicate. Archive Add Custom Item is a product-editor save only.",
        "Complete the sale through the normal Sell workflow. Checkout marks each custom product in that transaction Sold. The archive status is product-level, so a custom item should represent one exceptional item rather than a reusable miscellaneous SKU.",
        "Open a row or pencil to inspect/edit the custom product through Product Details. Although the full editor exposes broad catalog fields, using variants, tracked inventory, online selling, purchasing, or repeat-sale design defeats the intended one-off model; create a standard or non-inventory catalog product instead when repeatability is required.",
        "For Active rows, Deactivate immediately writes sold_status Inactive and is_active false. For Inactive rows, Activate immediately restores sold_status Active and is_active true. Neither action has a confirmation dialog or checks a linked cart/receipt.",
        "For Sold rows, Reactivate immediately changes sold_status to Active and is_active true. Use this only after verifying the original transaction was properly returned, exchanged, voided, or otherwise reversed. The button itself does not create a return, reverse revenue/payment, update a receipt, or restore inventory.",
        "Supported receipt reversal/return logic can also reactivate custom products, and sale repair/completion logic can set them Sold. After any exception, verify the receipt and custom archive together rather than treating the badge as the accounting source of truth.",
        "When no rows exist, No custom items yet is a completed empty state. When search has no match, the screen says No items match your search. Clear search and return to All before concluding the record is missing.",
        "Protect customer context: the archive does not show the associated receipt/customer, and editing a row does not reveal which sale made it Sold. Use the authorized receipt workflow to establish provenance; do not infer ownership from the product name."
      ],
      "controls": [
        {
          "name": "Archive icon",
          "description": "Exact CentriPOS navigation icon for Custom Items."
        },
        {
          "name": "Information icon",
          "description": "Explains that custom items are miscellaneous receipt-history records excluded from regular inventory, POs, and receiving."
        },
        {
          "name": "One-off item count",
          "description": "Total loaded custom-product count before the current search/status filter."
        },
        {
          "name": "Search custom items…",
          "description": "Client-side Name or SKU match only."
        },
        {
          "name": "All / Active / Inactive / Sold",
          "description": "Filters by product sold_status, not receipt status or stock state."
        },
        {
          "name": "Item / Cost / Price / Status / Created",
          "description": "Columns in the archive list."
        },
        {
          "name": "Sell → Custom Item",
          "description": "Quick dialog requiring name and positive sell price, with optional cost; creates the record and adds it to the cart."
        },
        {
          "name": "Add Custom Item",
          "description": "Archive action opening the full custom Product editor; saving does not add the item to a cart."
        },
        {
          "name": "Register-created defaults",
          "description": "product_type custom, track_inventory false, sell_pos true, sell_online false, sold_status active."
        },
        {
          "name": "Sold",
          "description": "Product status written when supported checkout/repair logic completes a sale containing the custom item."
        },
        {
          "name": "Deactivate",
          "description": "Immediately writes sold_status inactive and is_active false without checking a receipt."
        },
        {
          "name": "Activate",
          "description": "Immediately writes sold_status active and is_active true."
        },
        {
          "name": "Reactivate",
          "description": "Available for Sold rows; immediately restores Active without reversing the original transaction."
        },
        {
          "name": "Row / pencil",
          "description": "Opens the full Product editor for that custom record."
        },
        {
          "name": "No custom items yet",
          "description": "Fully rendered zero-record state."
        },
        {
          "name": "No items match your search",
          "description": "Search/filter result state; clear filters before concluding the item is absent."
        },
        {
          "name": "Not provenance",
          "description": "Archive rows show no customer, receipt, or sale identifier; use Sales/Receipts for transaction evidence."
        },
        {
          "name": "Not reusable inventory",
          "description": "Use a standard/non-inventory catalog product for repeat sales, variants, purchasing, receiving, or inventory tracking."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/custom-items in a fully rendered empty state. It shows no one-off items and no customer or receipt data; no item dialog was opened."
        }
      ],
      "expectedResult": "The one-off item appears once in the intended archive state and on the related sale and receipt without being mistaken for a reusable inventory product.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-custom-items.png",
        "alt": "Harbor & Hearth Custom Item Archive showing search, status filters, and archived custom-item management in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "master-product-book",
      "url": "https://platform.getcentri.com/centripos/master-product-book",
      "title": "Use the Master Product Book",
      "summary": "See which active HQ products have been published into child businesses, inspect variant pricing, and mark a master product discontinued or restore it network-wide.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Master Product Book",
      "introduction": "Master Product Book is an Enterprise HQ, Agency, or Platform screen under Products and uses the Globe icon. It is not a storefront adoption screen and it does not publish, import, edit, or synchronize products. Child organizations do not receive this navigation item; publication is started separately from the HQ Products screen.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Open Products → Master Product Book. If the signed-in tenant is not an Enterprise HQ, Agency, or Platform account, CentriPOS states that the book is available only for franchise HQ accounts.",
        "Read the Total, Active, and Discontinued cards first. Total represents active, nondeleted products in the current HQ catalog; Active and Discontinued divide that set by the HQ deprecation flag.",
        "Use Search products to filter by the master product name or the product-level SKU. The current search does not inspect brand, child business name, variant name, or variant SKU.",
        "Read each product row. It shows the master product name, product SKU or a dash, brand when present, linked franchisee-product count, linked child-business names, retail price, and a Suggested price only when the recommended retail differs from retail.",
        "Do not read the franchisee count as a count of physical stores, locations, or inventory units. It counts child product records linked back to that HQ source product; the displayed names are the distinct child tenants represented by those links.",
        "When a row has variants, choose the row or chevron to expand it. The variant badge shows how many variants are available. Each expanded line shows the variant name, variant SKU when present, retail price, and a differing Suggested price when present.",
        "Use Discontinue only when HQ intends to retire that master product across the network. Read the confirmation carefully: child businesses can still sell remaining stock, but they will see the Discontinued by HQ flag. This action does not delete the HQ product or its child copies.",
        "Choose Cancel to leave the product unchanged, or Discontinue to set the HQ deprecation flag. Wait for the product-name marked as discontinued confirmation and confirm the Discontinued card increases.",
        "For a discontinued product, choose Restore and confirm. Restore removes the Discontinued by HQ flag; it does not republish a missing product, reactivate a deleted product, change local inventory, or reconstruct a child record.",
        "To publish the HQ catalog, leave Master Product Book and open Products. Use the separate Publish Products to Network action, choose All franchisees or one child tenant, and confirm the publish there. Returning to Master Product Book lets you review the resulting linked-product distribution.",
        "To change a product name, brand, SKU, variant, image, retail price, or recommended retail, edit the master record from Products. Master Product Book is intentionally read-only for those values.",
        "If No products found appears, clear the search. If the empty state remains, confirm the HQ has active, nondeleted products; this view deliberately excludes inactive or deleted HQ records.",
        "After a publish, discontinue, or restore action, verify both the HQ row and a representative child product. The HQ count and flag are control-plane evidence; they do not by themselves prove every child catalog, price policy, sellability rule, or inventory quantity."
      ],
      "controls": [
        {
          "name": "Globe icon",
          "description": "Navigation and page icon for the HQ-only Master Product Book."
        },
        {
          "name": "Total",
          "description": "Count of current HQ products that are active and not deleted, including both active and discontinued master products."
        },
        {
          "name": "Active",
          "description": "Products in the displayed HQ set without a deprecation timestamp."
        },
        {
          "name": "Discontinued",
          "description": "Products in the displayed HQ set carrying the HQ deprecation timestamp."
        },
        {
          "name": "Search products",
          "description": "Filters only by product name or product-level SKU on this screen."
        },
        {
          "name": "Product row",
          "description": "HQ product name, SKU, brand, child-product distribution count and names, retail price, optional suggested price, variant count, and current discontinue state."
        },
        {
          "name": "Franchisee count",
          "description": "Number of linked child product records, not a location count, stock count, or proof of successful use at every child business."
        },
        {
          "name": "Child-business names",
          "description": "Distinct tenant names found on linked child product records."
        },
        {
          "name": "Variant badge",
          "description": "Number of variants attached to the HQ product."
        },
        {
          "name": "Expanded variants",
          "description": "Variant name, SKU, retail price, and a differing recommended or Suggested price when present."
        },
        {
          "name": "Suggested price",
          "description": "Recommended retail shown only when it exists and differs from the row’s retail price. How a child may use it depends on the network pricing policy."
        },
        {
          "name": "Discontinue",
          "description": "Sets the HQ deprecation flag after confirmation and surfaces Discontinued by HQ to linked child products while allowing remaining stock to be sold."
        },
        {
          "name": "Restore",
          "description": "Removes the HQ deprecation flag. It does not recreate, republish, or reactivate missing child records."
        },
        {
          "name": "Publish boundary",
          "description": "Publishing is a separate Products-screen action with an All franchisees or single-child target; it is not available inside Master Product Book."
        },
        {
          "name": "Editing boundary",
          "description": "Names, SKUs, brands, variants, images, and prices are edited from the HQ Products record, not this book."
        },
        {
          "name": "No products found",
          "description": "No master product matches the product-name or product-SKU search, or the HQ has no active, nondeleted products."
        }
      ],
      "expectedResult": "The intended active, nondeleted HQ product appears once with the correct master identity, variant pricing, linked child-product count and tenant names, and deprecation state; any Discontinue or Restore action shows the expected network flag on a representative child without being mistaken for publish, delete, local stock, or sellability.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "promotions",
      "url": "https://platform.getcentri.com/centripos/promotions",
      "title": "Build and test Promotions without relying on unwired labels",
      "summary": "Create simple or conditional in-store offers, understand manual cart application and stacking, and avoid unsupported delivery, online, targeting, loyalty, or code-gating assumptions.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Promotions",
      "introduction": "Products → Promotions uses the Megaphone icon. The current matcher loads only Active promotions whose channel is In store or In store & online, evaluates their schedule/conditions against the Sell cart, and presents each match for staff to manually accept or dismiss. Several editor labels are not fully enforced: Online-only is not loaded by this matcher; Free delivery calculates $0 and does not waive fees; Entire sale excluding delivery is calculated against the full subtotal; promo codes are not required entry codes; Target everyone and Offer loyalty points are stored but not evaluated. Test every rule with exact carts before activation.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Promotions. Wait for loading, then review newest-first Name/code, headline Discount, Schedule, Channel, and Active. The real Harbor & Hearth screenshot is a loaded list capture with no editor or active-state changes.",
        "Do not treat the list headline as the complete rule. For a complex promotion it stores/displays only the first valid action as discount_type/value; open the row to review every IF condition and THEN action.",
        "Choose Add promotion. Enter a required operational Name, optional uppercase Promo code, and staff Description. Promo code is only stored/displayed; the current Sell flow does not ask the customer/cashier to enter it. When staff manually applies the eligible promotion, the code is appended to the sale note as Promo: <code>.",
        "Choose Simple for one reward. Select Percentage or fixed tenant-currency value, then Entire sale, Entire sale (excl. delivery), Specific products, Category, Brand, Supplier, or Delivery/Shipping. A positive numeric value is required except Free delivery.",
        "For product/category/brand/supplier targeting, select at least one exact reference even though the form does not enforce it. Saving an item action with no reference creates a null-target action that the evaluator applies to every cart item. Verify selections after reopening.",
        "Do not use Delivery/Shipping in production: the saved free_delivery action has value 0, the evaluator only describes Free delivery, and the cart’s promotion discount remains $0. It does not remove the fulfillment fee.",
        "Do not rely on Entire sale (excl. delivery): the editor writes an exclusion marker, but percent_off_cart/fixed_off_cart evaluation ignores it and the cart applies the promotion against its full line subtotal, including fulfillment-charge lines.",
        "Choose Complex (If / Then) for multiple conditions/actions. Every saved condition row must pass. Cart total minimum uses subtotal; Cart quantity minimum sums item quantities; contains conditions check selected product/category/brand/supplier references. Multiple selected references are flattened into multiple conditions, so all selected references—not any one—must match.",
        "Add THEN actions for percent/fixed off cart, percent/fixed off specific items, or Free delivery. Multiple valid actions are summed. Percentage inputs have no 100% maximum validation; enter only an approved 0–100 value. Item fixed discounts are capped per unit price, while cart fixed discount is capped to subtotal for that action.",
        "Category/brand/supplier conditions/actions depend on the exact identifiers present on Sell cart product objects. Because product category values can be names while the editor stores category IDs, and supplier identity can be represented through relationships, test each targeted rule against actual eligible and ineligible products; a saved reference is not proof it will match.",
        "Set Sales channel honestly. Current Sell matcher queries In store and In store & online only. Online-only promotions are excluded from Sell, and no customer-storefront promotion evaluator was found in the active source. Do not advertise online availability until a controlled storefront checkout proves it.",
        "For One-time schedule, optionally select Starts at and Ends at. The calendar writes ISO timestamps from selected dates; the evaluator compares current time against those timestamps. Verify timezone and boundary-day behavior. Blank start/end is unbounded. The form does not prevent end before start.",
        "For Recurring weekly, select Sun–Sat. The matcher checks only the browser’s current weekday. If no days are selected, the current condition treats it as active every day. Recurring mode does not use the one-time start/end fields, times of day, timezone selection, or date-range bounds.",
        "Target everyone is stored but the editor exposes no customer/group selector when turned off, and the current matcher does not inspect the field or attached customer. Leave it on unless/until a supported targeting flow is implemented; turning it off does not create a targeted offer.",
        "Offer loyalty points stores a flag, but Admin → Loyalty is a coming-soon screen and the current promotion matcher does not award points. Do not enable or advertise loyalty from this toggle.",
        "Create with Active off for safe testing setup. Save is multi-step and non-transactional: it writes the promotion, deletes/recreates conditions, then deletes/recreates actions. A failure after the first write can leave a partially updated promotion/rule set. Reopen and inspect all fields after every save error or success.",
        "When ready, use the list Active switch. It writes immediately with no confirmation or success toast. Active alone is insufficient: schedule, channel, and conditions still determine eligibility. The promotion query can remain cached for up to about 30 seconds, so do not toggle repeatedly while testing.",
        "In Sell, build one exact eligible cart. Matching promotions appear as suggestions showing name, description, and calculated savings. Staff must choose Check to apply or X to dismiss; offers are not auto-applied. Applied promotions appear separately and can be removed.",
        "Build ineligible boundary carts: below/at minimum, missing/including every selected reference, delivery/no-delivery, different weekday/date, returns/negative quantities, tax/line discounts, and manual sale discount. Verify subtotal, tax adjustment, total, receipt, saved discount, and reporting.",
        "Test overlaps explicitly. Multiple matched promotions can all be manually applied and their discountAmount values are summed. Each action/promotion may cap itself, but the combined promotion sum is not capped to the subtotal before finalSubtotal, and it stacks with line and manual sale discounts. Avoid overlapping active rules that could make subtotal/tax/total invalid.",
        "To delete, choose Trash and confirm Delete <name>? This cannot be undone. The code deletes product/location link rows and then the promotion; child-delete errors are not surfaced before the parent attempt. There is no archive, restore, duplicate, usage report, or historical-sale impact preview. Prefer deactivation until retention/reporting impact is understood."
      ],
      "controls": [
        {
          "name": "Megaphone icon",
          "description": "Exact CentriPOS navigation icon for Promotions."
        },
        {
          "name": "Name / promo code",
          "description": "Operational label and optional uppercase annotation; code is not an entry gate."
        },
        {
          "name": "Headline Discount",
          "description": "First saved action summarized in the list, not the complete complex rule."
        },
        {
          "name": "Simple",
          "description": "One generated reward action with optional target references."
        },
        {
          "name": "Complex (If / Then)",
          "description": "All conditions must pass; every valid action is applied/summed."
        },
        {
          "name": "Entire sale",
          "description": "Percent/fixed cart action against current cart subtotal."
        },
        {
          "name": "Entire sale (excl. delivery)",
          "description": "Currently mislabeled behavior: exclusion marker is ignored by calculator."
        },
        {
          "name": "Specific products / Category / Brand / Supplier",
          "description": "Item-target references; choose at least one and verify runtime identifiers."
        },
        {
          "name": "Delivery / Shipping",
          "description": "Currently yields a $0 Free delivery match and does not waive fees."
        },
        {
          "name": "Cart total / quantity minimum",
          "description": "Numeric conditions evaluated against subtotal or summed quantities."
        },
        {
          "name": "Contains conditions",
          "description": "Reference conditions; multi-select expands to AND rows requiring all selected references."
        },
        {
          "name": "Percentage value",
          "description": "Positive number with no 100% upper-bound validation."
        },
        {
          "name": "Sales channel",
          "description": "Sell loads In store and In store & online; Online-only is not loaded there."
        },
        {
          "name": "One-time schedule",
          "description": "Optional timestamp start/end with no end-after-start validation."
        },
        {
          "name": "Recurring weekly",
          "description": "Browser weekday only; no selected days behaves as every day."
        },
        {
          "name": "Target everyone",
          "description": "Stored flag not evaluated; off provides no target selector."
        },
        {
          "name": "Offer loyalty points",
          "description": "Stored flag not wired to the current coming-soon loyalty system."
        },
        {
          "name": "Active switch",
          "description": "Immediate save without confirmation/toast; eligibility may remain cached briefly."
        },
        {
          "name": "Sell suggestion Check / X",
          "description": "Manual apply or dismiss; no automatic application."
        },
        {
          "name": "Applied promotion",
          "description": "Can be removed; eligible discounts sum with other applied promotions."
        },
        {
          "name": "Stacking risk",
          "description": "Combined promotion discounts are not globally capped before subtotal/tax calculation and also stack with other discounts."
        },
        {
          "name": "Non-transactional save",
          "description": "Promotion and child rule replacements occur in separate writes; reopen after any error."
        },
        {
          "name": "Delete",
          "description": "Confirmed permanent removal of promotion and supported child links; no restore."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/promotions in a loaded list state. It shows headline offer metadata without opening editors, toggling Active, or exposing customer transactions."
        }
      ],
      "expectedResult": "The promotion shows the intended status and schedule, applies to an eligible test cart, and does not apply to an ineligible cart.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-promotions.png",
        "alt": "Harbor & Hearth Promotions screen showing promotion search, status filters, and promotion management in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "availability-rules",
      "url": "https://platform.getcentri.com/centripos/availability-rules",
      "title": "Configure Availability Rules",
      "summary": "Limit the products or categories available to a specific location or register in Sell, quick picks, scanning, and location inventory-count selection without changing stock quantities.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Availability Rules",
      "introduction": "Open Products → Availability Rules using the Sliders Horizontal icon. This screen has no rule name, schedule, date, time, channel, fulfillment-method, priority, edit, or inactive control. Every added rule is active immediately; remove it with the trash control when it should no longer apply.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Open Products → Availability Rules and read the page explanation: Include only makes a location or register sell only selected products or categories; Exclude hides selected products or categories from that scope.",
        "Choose Scope: Location or Register. Changing Scope clears the previously selected location/register so a stale ID cannot be saved under the wrong type.",
        "Choose the exact active Location, or choose the Register shown with its location name. The location list includes active locations; the register list is tenant-wide and labels each register with its related location when available.",
        "Choose Rule: Include only or Exclude. Include only establishes an allowlist for that scope; Exclude establishes a deny rule for the selected target.",
        "Choose Target: Category or Product. Changing Target clears the previous category/product selection.",
        "Choose the Category, or choose the active Product shown with its SKU when present. The product selector loads up to 500 active products ordered by name; if an expected item is absent, confirm it is active and consider whether the catalog exceeds that visible limit.",
        "Choose Add rule. Both a scope ID and target ID are required. CentriPOS saves the rule active immediately and reports Availability rule saved. Re-adding the identical scope, target, and effect updates the same unique rule rather than intentionally creating a duplicate.",
        "Read the rules table after every change. Scope shows Location or Register plus its resolved name; Rule shows Include only or Exclude; Target shows Category or Product plus its resolved name and SKU. Unknown location, register, category, or product means the referenced record can no longer be resolved and the rule should be investigated.",
        "Understand multiple Include only rules as a union. Once any include rule exists for the current location/register context, a product must match at least one included product or category. It does not need to match every include rule.",
        "Understand Exclude as a veto. If a product matches any applicable Exclude product or category, it is unavailable even if it also matches an Include only rule.",
        "At a register, CentriPOS evaluates active rules for both the current location and that exact register together. A match against any applicable include can satisfy the include allowlist, while any applicable exclude still blocks the product. Test combined location and register rules deliberately.",
        "Availability rules are evaluated after the product and each attached category’s own available-location or available-register restrictions. A rule cannot make a product available where the product or one of its categories is already restricted. Product register restrictions take precedence over its location list when register IDs are configured.",
        "In Sell, unavailable products are filtered from the standard product collection, search results, quick-pick grid, remote scanner state, and add-from-quick-pick checks for that operating location/register. These rules do not reduce inventory, deactivate the product globally, or create a fulfillment rule.",
        "For inventory counts, only Location-scoped rules participate because a count belongs to a location rather than a register. Include-only and Exclude use the same union/veto behavior, combined with the product and category’s own location restrictions. Register-scoped rules do not alter countable lines.",
        "To remove a rule, choose the Trash icon at the end of its row. There is no confirmation dialog and no inactive toggle; a successful deletion reports Rule removed and refreshes the table. Resolve the exact row before clicking.",
        "If No availability rules yet appears, the rule table is empty and this layer permits all products. Product- and category-level location/register restrictions can still hide items independently.",
        "Test with one matching and one nonmatching active product in the intended location and register. Check standard Sell search, the product grid, quick picks, and barcode/remote scan behavior. For a Location rule, also begin a controlled inventory count and confirm the countable product scope.",
        "Do not use Availability Rules to manage online-store publication, eCart visibility, delivery eligibility, dates, hours, customer groups, or inventory availability. Use the feature that owns that behavior and describe the intended rule to support if the correct control is unclear."
      ],
      "controls": [
        {
          "name": "Sliders Horizontal icon",
          "description": "Navigation icon for Products → Availability Rules."
        },
        {
          "name": "Scope",
          "description": "Location or Register. It determines where the active rule is evaluated."
        },
        {
          "name": "Location",
          "description": "One active tenant location selected as the rule scope."
        },
        {
          "name": "Register",
          "description": "One tenant register selected as the rule scope and labeled with its location when known."
        },
        {
          "name": "Include only",
          "description": "Adds a target to the applicable allowlist. If any include exists in the current combined scope, a product must match at least one include."
        },
        {
          "name": "Exclude",
          "description": "Blocks a matching target and always vetoes an include match in the same operating context."
        },
        {
          "name": "Target",
          "description": "Category or Product. It determines how the rule matches catalog items."
        },
        {
          "name": "Category target",
          "description": "Matches products attached to the selected category. A product can match through any of its attached category IDs."
        },
        {
          "name": "Product target",
          "description": "Matches only the selected product ID, including its variants as part of that product."
        },
        {
          "name": "Add rule",
          "description": "Immediately upserts an active rule after scope and target are selected. There is no separate Save button."
        },
        {
          "name": "Rules table",
          "description": "Current active and stored rules with scope, effect, target, resolved names, and remove action."
        },
        {
          "name": "Unknown … label",
          "description": "The referenced scope or target ID no longer resolves in the currently loaded tenant records."
        },
        {
          "name": "Include union",
          "description": "A product is allowed when it matches any applicable Include only rule; includes are not an all-must-match intersection."
        },
        {
          "name": "Exclude veto",
          "description": "Any applicable matching Exclude rule blocks the product even when an include also matches."
        },
        {
          "name": "Combined register context",
          "description": "Sell at a register evaluates both matching location rules and matching rules for that exact register."
        },
        {
          "name": "Product/category availability boundary",
          "description": "Existing available location/register IDs on the product and every attached category are checked before these rules and cannot be overridden by an include."
        },
        {
          "name": "Sell enforcement",
          "description": "Filters standard Sell products, search, quick picks, remote scanning state, and protected add actions for the current operating context."
        },
        {
          "name": "Inventory-count enforcement",
          "description": "Uses Location rules and location-level product/category availability to build countable lines; Register rules do not apply to a location count."
        },
        {
          "name": "Trash icon",
          "description": "Deletes the exact rule immediately, without an inactive state or confirmation dialog."
        },
        {
          "name": "No availability rules yet",
          "description": "No rows exist in this rules layer; it does not prove every product is otherwise unrestricted."
        },
        {
          "name": "Not supported here",
          "description": "Schedules, channels, fulfillment methods, online-store publication, customer eligibility, stock quantity, and priority are not controlled on this screen."
        }
      ],
      "expectedResult": "At the intended operating context, a matching product appears only when it passes its own and every attached category’s location/register restrictions, matches at least one applicable Include only rule when any include exists, and matches no applicable Exclude rule; Sell, quick picks, search, and scanning agree, while a Location rule also produces the expected countable inventory scope without changing stock.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "brands",
      "url": "https://platform.getcentri.com/centripos/brands",
      "title": "Create, assign, rename, and remove Product Brands",
      "summary": "Maintain one canonical brand per manufacturer or label, assign it from Product Details, and protect product and promotion relationships before deletion.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Brands",
      "introduction": "Brands uses the Tag icon in CentriPOS navigation. Each product can reference one brand or None. Brand names are unique within the business. Renaming updates the shared brand; deleting is immediate with no confirmation, sets assigned products’ brand to None, and removes brand-based promotion filter rows. Audit both products and promotions before deletion.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Brands. Wait for loading to finish, then review the alphabetized Name and Description table for the current business.",
        "Before creating a brand, scan for spelling, punctuation, capitalization, abbreviations, or legal-name variants of the same label. The page has no search, merge, assignment count, or duplicate-cleanup control.",
        "Choose Add brand. Enter the required Name and an optional concise Description. Both values are trimmed; an empty description is stored as no description and displays as a dash in the list.",
        "Choose Add brand once and wait for Brand added. An exact duplicate tenant/name value is rejected; read the error toast rather than creating a near-duplicate spelling. Creating a brand does not assign it to any product.",
        "To assign the brand, open Products, create or edit the exact product, and choose the brand under Product Details → General → Brand. One product can select one brand or None. Save the product and verify its details afterward.",
        "To correct shared brand text, choose the brand row or Edit pencil, update Name or Description, and choose Save. Wait for Brand updated. The existing brand ID remains linked to its products, so the new name is reflected through that relationship.",
        "Remember that brand Description belongs to the brand-management record; it is not the product’s rich-text Description, an online merchandising guarantee, or a substitute for product-specific copy.",
        "Before deletion, audit every assigned product and every active or scheduled promotion that filters by this brand. The Brands list does not show either relationship. Reassign products and replace promotion criteria first when the business still needs them.",
        "Choose the trash icon only when the brand should be removed. The delete runs immediately without a confirmation dialog or visible undo. On success, Brand deleted appears; product brand_id relationships are set to null and brand-targeted promotion filter rows are deleted by their database relationships.",
        "After add, rename, assignment, or deletion, verify representative Product Details, Products filters/search where supported, promotion targeting, exports, and reports that depend on the brand. A brand selection does not by itself change price, tax, stock, supplier, category, product type, POS availability, or online publication.",
        "Use Product Tags for flexible many-to-many labels and Categories for hierarchical grouping. Do not create brands merely to reproduce those structures."
      ],
      "controls": [
        {
          "name": "Tag icon",
          "description": "Exact CentriPOS navigation icon for Brands."
        },
        {
          "name": "Name",
          "description": "Required trimmed canonical brand name, unique within the current business."
        },
        {
          "name": "Description",
          "description": "Optional plain-text brand-management description; a missing value displays as a dash."
        },
        {
          "name": "Add brand",
          "description": "Opens /catalog/brands/new and creates the shared record after validation."
        },
        {
          "name": "Brand row",
          "description": "Opens the existing brand editor."
        },
        {
          "name": "Edit pencil",
          "description": "Opens the same editor without triggering the row action."
        },
        {
          "name": "Save",
          "description": "Updates the existing brand record, preserving its ID and current product relationships."
        },
        {
          "name": "Trash icon",
          "description": "Immediately deletes the brand with no confirmation or visible restore."
        },
        {
          "name": "Product Details → Brand",
          "description": "Single-select product relationship with a None option."
        },
        {
          "name": "Product deletion effect",
          "description": "Deleting a brand sets assigned products’ brand reference to None; it does not delete those products."
        },
        {
          "name": "Promotion deletion effect",
          "description": "Deleting a brand removes promotion-product filter rows that target that brand; review promotions before deletion."
        },
        {
          "name": "No assignment count",
          "description": "The Brand list does not reveal how many products or promotions reference a row."
        },
        {
          "name": "Not a behavior switch",
          "description": "Brand selection alone does not alter pricing, tax, inventory, supplier, category, product type, selling channel, or publication state."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/brands in a loaded list state. It accurately shows the Brands heading, Add brand control, Name/Description table, and row actions without opening an editor or delete action."
        }
      ],
      "expectedResult": "The canonical brand appears once in the Brands list and can be selected on the intended product records.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-brands.png",
        "alt": "Harbor & Hearth Brands screen showing product-brand search and management in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "suppliers",
      "url": "https://platform.getcentri.com/centripos/suppliers",
      "title": "Create and maintain Suppliers",
      "summary": "Manage vendor identity, purchasing contacts, addresses, PO email recipients, product relationships, price lists, QuickBooks links, and supplier-specific surcharge rules.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Suppliers",
      "introduction": "Suppliers uses the Truck icon in CentriPOS navigation. A supplier is an operational vendor, not a customer contact. The editor contains private business contact data and purchasing rules. Deletion is immediate with no confirmation; dependent purchasing records can block it, while other linked data may cascade away. Audit products, price lists, contacts, surcharge rules, purchase orders, receipts, returns, and accounting links first.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Suppliers. Wait for loading to finish, then review the alphabetized Supplier, Description, and Default markup table for the current business. The real Harbor & Hearth screenshot is a read-only list capture; it does not expose contact details or open an editor.",
        "Before adding a vendor, compare legal name, trading name, punctuation, and existing QuickBooks or purchasing identity. The list has no search, duplicate merge, assignment count, or dependency preview. Supplier names are unique within the business.",
        "Choose Add supplier. Enter the required Supplier name and review Default markup %. The field accepts a number and defaults to zero. Treat it as a supplier default, not proof that existing product prices were recalculated; verify the exact product or vendor-list workflow that uses it.",
        "Add an optional Description, primary contact first/last name, company, corporate email, corporate phone, mobile, fax, website, and postal address. The primary corporate email becomes the default To address for purchase-order emails. Verify it belongs to the intended vendor before sending a PO.",
        "Under Sub-contacts, choose Add contact for buyers, representatives, accounts-payable contacts, or email-only CC recipients. Each draft can store name, title, email, phone, mobile, and notes. Blank drafts are discarded when the supplier is saved.",
        "Enable CC this contact on PO emails only when that recipient should be prefilled on purchase-order messages. A CC-enabled sub-contact must have an email address or the entire supplier save stops with a validation error. Confirm sensitive PO pricing and terms are appropriate for every To and CC recipient.",
        "Choose Add supplier once. On success, Supplier added appears and the editor closes. The supplier record is created first, then its nonblank sub-contacts are written; if contact saving fails after supplier creation, inspect the resulting supplier before retrying so a duplicate is not created.",
        "To edit, choose the supplier row or pencil. Review all fields before Save. The current save process deletes that supplier’s existing sub-contact rows and recreates them in displayed order, so remove or alter a contact only when the complete replacement list is correct.",
        "For an edited supplier, read QuickBooks Online vendor. View on QBO appears only when a saved external vendor URL exists. An absent link means no link is shown; it does not authorize creating a duplicate QBO vendor. QuickBooks supplier sync behavior is controlled in the separate integration settings.",
        "Review Account fee / surcharge rules. These are rules saved from purchase orders for the supplier and can auto-apply a dollar or percentage fee to all supplier products or category-, tag-, or brand-scoped products. Use Turn on/off deliberately; each action saves immediately.",
        "Choose Delete on a surcharge rule only when it should stop existing. This action soft-deletes the rule and turns auto-apply off immediately, with no confirmation. Create new surcharge rules from a purchase order after selecting the supplier and an account fee/surcharge; the supplier editor only reviews, toggles, or deletes existing rules.",
        "Choose Manage vendor price lists for <supplier> to open the supplier-specific price-list area. Use that workflow for uploaded or maintained vendor pricing rather than placing pricing data in Description or Notes.",
        "Assign a supplier to products through Product Details or the supported Products workflow. A product can have supplier relationships separate from the supplier’s Default markup. Verify primary-supplier selection, cost, SKU, lead time, and price-list effects in the product/purchasing workflow rather than assuming the supplier record supplies every value.",
        "Before deleting a supplier, inventory all dependent products, supplier contacts, vendor price lists, active surcharge rules, open and historical purchase orders, receipts, returns, and QuickBooks mappings. Reassign or close them according to policy and retain any legally required purchasing history.",
        "Choose the supplier-row trash icon only after that audit. It issues a delete immediately with no confirmation or visible undo. A foreign-key error means retained dependent records block deletion; stop and resolve them correctly. A successful Deleted toast means the supplier row is gone and cascade-configured links such as contacts, product-supplier associations, or surcharge rules may also be removed.",
        "After any change, verify representative Product Details, purchase-order supplier selection and email recipients, vendor price lists, surcharge behavior, receiving/return history, and QBO link. Supplier maintenance alone does not send email, create a PO, change inventory, update product price, or create a QuickBooks vendor unless the separate workflow does so."
      ],
      "controls": [
        {
          "name": "Truck icon",
          "description": "Exact CentriPOS navigation icon for Suppliers."
        },
        {
          "name": "Supplier table",
          "description": "Alphabetized current-business list showing Supplier, Description, and Default markup only."
        },
        {
          "name": "Supplier name",
          "description": "Required trimmed canonical vendor name, unique within the tenant."
        },
        {
          "name": "Default markup %",
          "description": "Numeric supplier default; verify where it is applied before expecting product prices to change."
        },
        {
          "name": "Primary corporate email",
          "description": "Default purchase-order To recipient for this supplier."
        },
        {
          "name": "Primary contact and address",
          "description": "Vendor identity/contact fields stored on the supplier; they are not customer records."
        },
        {
          "name": "Sub-contacts",
          "description": "Ordered optional vendor contacts recreated as a complete set each time the supplier is saved."
        },
        {
          "name": "CC this contact on PO emails",
          "description": "Prefills the sub-contact in PO CC; requires that contact to have an email address."
        },
        {
          "name": "Add supplier / Save",
          "description": "Writes the supplier, then replaces its saved sub-contact rows with the nonblank drafts."
        },
        {
          "name": "QuickBooks Online vendor",
          "description": "Read-only link status in the editor; View on QBO appears only for a saved external vendor URL."
        },
        {
          "name": "Account fee / surcharge rules",
          "description": "Supplier-specific PO fee rules with dollar/percent value, scope, and auto-apply state."
        },
        {
          "name": "Turn on / Turn off",
          "description": "Immediately toggles an existing surcharge rule’s auto-apply state."
        },
        {
          "name": "Delete surcharge rule",
          "description": "Immediately soft-deletes the rule and disables auto-apply without a confirmation dialog."
        },
        {
          "name": "Manage vendor price lists",
          "description": "Opens /catalog/supplier-price-lists/<supplier id> for the selected supplier."
        },
        {
          "name": "Product-supplier assignment",
          "description": "Separate relationship managed from the product/purchasing workflow; may include primary supplier and supplier-specific details."
        },
        {
          "name": "Trash icon",
          "description": "Immediately attempts supplier deletion with no confirmation or visible restore. Dependencies may block deletion; cascade-configured related rows can be removed on success."
        },
        {
          "name": "No suppliers yet.",
          "description": "Fully rendered empty state when the tenant has no supplier rows."
        },
        {
          "name": "Not an operational transaction",
          "description": "Saving a supplier does not itself email a vendor, issue a PO, receive stock, return goods, recalculate product prices, or create QBO activity."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/suppliers in a loaded list state. It shows supplier names and public catalog metadata only; no vendor contacts, credentials, costs, or dialogs are exposed."
        }
      ],
      "expectedResult": "The supplier appears in the Suppliers list and is selectable on the intended product and purchasing workflows.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-suppliers.png",
        "alt": "Real Harbor & Hearth Suppliers list showing supplier names, descriptions, default markup, and row actions in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "vendor-price-lists",
      "url": "https://platform.getcentri.com/centripos/vendor-price-lists",
      "title": "Use Vendor Price Lists",
      "summary": "Maintain exact supplier-specific product and variant costs, minimum order quantities, vendor SKUs, effective dates, and calculated surcharge layers for purchasing.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Vendor Price Lists",
      "introduction": "Open Products → Vendor Price Lists with the File Text icon. This is a structured editor, not a file-import workflow: the current screen has no upload, CSV/XLSX column mapping, currency selector, preview/apply batch, or exception queue. Manual rows and dynamic calculated rows use the tenant currency shown by CentriPOS.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Vendor Price Lists. The first screen lists every Supplier with Truck icons, its description, vendor-price-list count, up to three list-name badges, and an All vendor price lists table with Name, Vendor, Valid from, Valid to, and Default.",
        "If No suppliers yet appears, choose Add a supplier and create the canonical supplier first. A vendor price list always belongs to one supplier; it is not a global cost sheet that can be reassigned between suppliers.",
        "Choose the intended supplier. Review its description and existing Vendor Price Lists before adding another. A row can show Default, a Dynamic percent/dollar badge, description, and validity dates.",
        "Choose Add vendor price list or Add first vendor price list. Enter the required Name, optional Description, Valid from, Valid to, and whether it is the Default price list for this supplier. The dates are metadata shown on the list; purchasing workflows decide which supported list is selectable or preferred.",
        "Choose Vendor price list type. Manual pricing stores exact rows you edit. Dynamic adjustment starts from Standard catalog cost or another non-dynamic list for the same supplier and calculates a percent or dollar addition. Choosing Dynamic turns off Default in the editor.",
        "For Dynamic adjustment, select the Base vendor price list, Percent or Dollar, and the value to add. Standard catalog cost uses product/variant catalog supply cost as the base; another list uses its saved vendor rows. Dynamic lists cannot be selected as the base of another dynamic list in this editor.",
        "Optionally narrow a dynamic list with Apply to filters for Brand, Category, Tag, Product, and Variant. Leaving a filter group blank includes all. Within a selected group the chosen values are alternatives; when multiple groups are used, a line must satisfy each group.",
        "Save a dynamic list to run its synchronization. Calculated cost rows are generated from matching base rows and displayed read-only with Product, optional Variant, Vendor SKU, and Calculated cost. Change an individual value in the base list or switch this list to Manual pricing; do not expect a calculated row to be editable.",
        "For Manual pricing, choose Add from catalog and search by product name, base SKU, brand, tag, or category. The initial picker can show the first catalog products even before text is entered, then limits search results.",
        "For a product without variants, select it once. The new row starts from the product’s catalog supply price, Minimum Order Quantity 1, and blank Supplier SKU. A duplicate base-product row is rejected as Already in this price list.",
        "For a product with variants, choose Add all to add every variant not already present or Pick to open the multi-select variant picker. Each new variant row starts from that variant’s catalog supply price and Minimum Order Quantity 1. Existing variant IDs are skipped rather than duplicated.",
        "Edit each manual row’s Supplier SKU, Vendor Cost, and Min Order Qty. The card shows Published Retail plus calculated Markup, Margin percentage, and margin dollars as reference. Vendor Cost is specific to this list; changing it here does not disguise or overwrite the displayed retail price.",
        "Use the product-name link to open Product Quick View when you need broader catalog, variant, base-pricing, customer-price-book, or vendor-list context. An Inactive badge warns that the catalog product is not active; the list row can still exist and should be reviewed before purchasing.",
        "Filter existing manual entries with Name or SKU, Brand, Category, Tag, or Supplier. The Supplier filter means suppliers represented by any vendor-list entry for that product, not only the current list’s supplier. Filters change what is visible, not which entries will be saved. Clear all restores the full list.",
        "Expand a product group to edit its variant rows. Trash on one row removes that product/variant from the unsaved list; trash on the group removes all displayed variant entries for that product. Review removal before saving because the manual save replaces the list’s stored entry set.",
        "Choose Save Vendor Price List. A name is required. For a manual list, CentriPOS deletes its previous stored entries and inserts the entire current editor set; for a dynamic list, it runs the dynamic synchronization. Success returns to the supplier list and reports Price list saved.",
        "Use Cancel to leave without invoking Save. For an existing list, Delete asks Delete this price list and all its entries? and permanently removes the entries and list after confirmation. The supplier-level Trash action performs the same destructive list deletion.",
        "Verify the saved list under the correct supplier, check Default/Dynamic and validity badges, reopen representative base and variant rows, and confirm the intended list is available in the Purchase Order vendor-price-list selector. A price-list row is cost/reference data; it does not itself create a purchase order, change stock, or update customer retail pricing.",
        "Do not look for an import or batch-apply button on this screen. If the vendor supplied a spreadsheet, reconcile its products and variants outside this nonexistent workflow, then enter reviewed rows manually or use an approved data-import process managed separately."
      ],
      "controls": [
        {
          "name": "File Text icon",
          "description": "The exact CentriPOS navigation icon for Products → Vendor Price Lists."
        },
        {
          "name": "Supplier overview",
          "description": "One row per supplier with description, list count, and up to three list badges."
        },
        {
          "name": "All vendor price lists",
          "description": "Cross-supplier table of list name, vendor, validity dates, and Default state."
        },
        {
          "name": "Truck icon",
          "description": "Supplier identity icon on the overview and supplier heading."
        },
        {
          "name": "Add a supplier",
          "description": "Opens supplier creation when no canonical supplier exists."
        },
        {
          "name": "Add vendor price list",
          "description": "Creates a new list under the selected supplier."
        },
        {
          "name": "Name",
          "description": "Required vendor-list name such as Standard, Drop Ship, Truck Delivery, or LTL."
        },
        {
          "name": "Description",
          "description": "Optional operating context for staff choosing the list."
        },
        {
          "name": "Valid from / Valid to",
          "description": "Optional list metadata shown on list summaries."
        },
        {
          "name": "Default price list for this supplier",
          "description": "Marks the preferred/default supplier list; Dynamic selection turns this off in the editor."
        },
        {
          "name": "Manual pricing",
          "description": "Editable exact rows for product or variant Vendor Cost, Supplier SKU, and minimum quantity."
        },
        {
          "name": "Dynamic adjustment",
          "description": "Calculated rows based on Standard catalog cost or another non-dynamic list plus a percent or dollar amount."
        },
        {
          "name": "Base vendor price list",
          "description": "Standard catalog cost or another manual list belonging to the same supplier."
        },
        {
          "name": "Percent / Dollar adjustment",
          "description": "Amount added to each matching base cost during dynamic synchronization."
        },
        {
          "name": "Apply to filters",
          "description": "Optional Brand, Category, Tag, Product, and Variant scope; blank includes all and populated groups combine by group."
        },
        {
          "name": "Calculated cost rows",
          "description": "Read-only synchronized product/variant rows shown after saving a dynamic list."
        },
        {
          "name": "Add from catalog",
          "description": "Manual-list product picker searching name, base SKU, brand, tag, or category."
        },
        {
          "name": "Add all",
          "description": "Adds every not-yet-present variant for the selected variable product."
        },
        {
          "name": "Pick",
          "description": "Opens multi-select variant choice while disabling variants already in the list."
        },
        {
          "name": "Supplier SKU",
          "description": "Vendor’s identifier for the exact product or variant in this list."
        },
        {
          "name": "Vendor Cost",
          "description": "Tenant-currency cost for that manual list row."
        },
        {
          "name": "Min Order Qty",
          "description": "Smallest purchasing quantity recorded for the row; the editor enforces at least 1."
        },
        {
          "name": "Pub. Retail",
          "description": "Current catalog retail reference used to calculate the displayed markup and margin."
        },
        {
          "name": "Markup / Margin",
          "description": "Reference calculations from retail and this row’s vendor cost; they do not change retail."
        },
        {
          "name": "Product Quick View",
          "description": "Broader product and pricing context opened from the product-name link."
        },
        {
          "name": "Inactive",
          "description": "Catalog-status warning on a product whose vendor row remains present."
        },
        {
          "name": "Name or SKU / Brand / Category / Tag / Supplier filters",
          "description": "Visibility filters for existing manual entries; they do not remove hidden rows from the editor set."
        },
        {
          "name": "Entry Trash",
          "description": "Removes one unsaved product/variant row from the current manual list."
        },
        {
          "name": "Group Trash",
          "description": "Removes every variant entry for that product from the current manual list."
        },
        {
          "name": "Save Vendor Price List",
          "description": "Persists metadata and either replaces the complete manual entry set or synchronizes calculated dynamic rows."
        },
        {
          "name": "Delete",
          "description": "Permanently deletes the list and all its entries after browser confirmation."
        },
        {
          "name": "Purchase Order selector",
          "description": "Downstream supported use for choosing a vendor list while building purchasing lines."
        },
        {
          "name": "Not available here",
          "description": "No upload, CSV/XLSX import, column matching, currency choice, proposed-versus-current preview, exception queue, or batch Apply control."
        }
      ],
      "expectedResult": "The saved list remains under the intended supplier; manual product/variant rows preserve the reviewed Supplier SKU, Vendor Cost, and minimum quantity, or dynamic rows match the chosen base, adjustment, and filters; validity and Default/Dynamic badges are correct; the Purchase Order selector can use the intended list; customer retail and stock remain unchanged; and no nonexistent file-import or batch-apply workflow is implied.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "product-tags",
      "url": "https://platform.getcentri.com/centripos/product-tags",
      "title": "Create, assign, rename, and remove Product Tags",
      "summary": "Maintain tenant-wide product labels, connect them to products individually or in bulk, and avoid accidental assignment loss when deleting a tag.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Product Tags",
      "introduction": "Product Tags uses the Tags icon in CentriPOS navigation. Tags are shared tenant-wide labels, not categories, brands, suppliers, product types, or online publication rules. Tag names must be unique within the business. Renaming keeps the same tag record and assignments; deleting is immediate, has no confirmation dialog, and removes that tag’s product assignments through the database relationship.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Product Tags. Wait for loading to finish, then review the alphabetized Name table. The list is scoped to the current business. “No tags yet.” is a complete zero-tag state.",
        "Before adding a label, search the visible list manually for the intended wording and check whether a category, brand, supplier, product type, or existing tag already represents the same concept. The page itself has no search, usage count, merge, or duplicate-cleanup tool.",
        "Choose Add tag. Enter one concise reusable Name; surrounding whitespace is trimmed. Add tag stays disabled until the name contains non-space text. Choose Add tag once and wait for Tag added.",
        "If the database rejects the name, read the error toast. Names are unique per tenant, so an exact existing value cannot be added twice; case behavior follows the stored database value and should not be used to create near-duplicates.",
        "To assign tags to one product, open Products, create or edit the product, and find Tags in Product Details. Search the existing tag, choose it, and save the product. The selected tag appears as a removable badge.",
        "If no result matches in the product Tags search, choose Create “name” only when a new tenant-wide tag is intended. Inline creation adds the tag and selects it for that product; the product still must be saved for its assignments to persist.",
        "To assign or remove a tag across several products, select the exact rows in Products and use the bulk tag action. Adding ignores duplicate product/tag links; removing deletes that tag association from the selected products. Verify the selection count and affected products before applying.",
        "To rename a tag, choose its table row or Edit pencil, change Name, and choose Save. Wait for Tag updated, then verify representative product records and filters show the new name. Renaming edits the shared tag rather than creating a second label.",
        "Before deletion, identify every product using the tag from the Products workflow or another approved audit. The Product Tags list does not show assignment counts or affected products. Record a replacement plan if the label supports operations or online merchandising.",
        "Choose the trash icon only when the shared tag and all of its product associations should be removed. The delete request runs immediately with no confirmation dialog and no undo/restore control on this screen; successful completion shows Deleted and removes the row.",
        "After any add, rename, assignment, bulk change, or deletion, reopen representative products and verify their Tags badges and the intended supported product filtering. A tag label alone does not change price, stock, tax, category, brand, supplier, product type, POS availability, or online publication."
      ],
      "controls": [
        {
          "name": "Tags icon",
          "description": "Exact CentriPOS navigation icon for Product Tags."
        },
        {
          "name": "Name table",
          "description": "Alphabetized tenant tag list with one canonical name per row."
        },
        {
          "name": "Add tag",
          "description": "Opens /catalog/tags/new and a one-field creation dialog."
        },
        {
          "name": "Name",
          "description": "Required trimmed tenant-wide label. An exact duplicate is rejected by the tenant/name uniqueness rule."
        },
        {
          "name": "Add tag button",
          "description": "Creates the new tag; it does not assign the tag to any product by itself."
        },
        {
          "name": "Row / Edit pencil",
          "description": "Opens the shared tag editor."
        },
        {
          "name": "Save",
          "description": "Renames the existing tag and preserves its ID and product relationships."
        },
        {
          "name": "Trash icon",
          "description": "Immediately deletes the tag without confirmation; its product-tag associations cascade away."
        },
        {
          "name": "No tags yet.",
          "description": "Fully rendered empty state, not a loading error."
        },
        {
          "name": "Product Details → Tags",
          "description": "Searchable individual-product assignment control with removable selected badges."
        },
        {
          "name": "Create “name”",
          "description": "Inline product-editor action that creates and selects a new tenant-wide tag when no exact result exists."
        },
        {
          "name": "Bulk tag action",
          "description": "Adds or removes one tag association across the selected Products rows."
        },
        {
          "name": "Assignment",
          "description": "Many-to-many relationship between a product and a shared tag; creating a tag alone creates no assignment."
        },
        {
          "name": "Not a behavior switch",
          "description": "Tags do not independently alter pricing, inventory, taxability, categorization, supplier, product type, selling channel, or publication state."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/tags in the fully rendered No tags yet state. It safely shows the Tags heading, Add tag control, Name table, and empty state without exposing product records."
        }
      ],
      "expectedResult": "The tag appears once in Product Tags and can be found on the intended products and supported filters.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-tags.png",
        "alt": "Harbor & Hearth Product Tags screen showing the Add tag action, tag-name table, and fully rendered empty state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "gift-cards",
      "url": "https://platform.getcentri.com/centripos/gift-cards",
      "title": "Read the Gift Cards configuration summary",
      "summary": "Confirm whether the tenant setting is enabled and read its stored sales channel and amount limits without mistaking this summary for a card-management or issuance screen.",
      "collection": {
        "id": "catalog",
        "title": "Products & catalog"
      },
      "section": "Gift Cards",
      "introduction": "Products → Gift Cards uses the Gift icon and reads the same tenant gift_card_settings record edited under Admin → Store Credit & Gift Cards. When enabled, this page is read-only. When disabled or no row exists, its visible Enable gift cards button currently has no click handler and does not change configuration. No card number, balance, customer, issuance, reload, redemption, expiration date, transaction, or search controls exist here.",
      "beforeYouBegin": "Search first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.",
      "steps": [
        "Go to Products → Gift Cards. Wait for the loading spinner to finish and confirm the Gift Cards heading.",
        "If the page says Gift Cards are not enabled, treat that as the stored tenant state or absence of a settings row. Do not rely on the visible Enable gift cards button: in the current implementation it performs no action and shows no confirmation.",
        "For an authorized configuration change, go to Admin → Store Credit & Gift Cards. That is the wired editor for is_enabled, has_expiry, min_amount, and max_amount. Return to Products → Gift Cards after saving to read the updated summary.",
        "When enabled, read Sales channel. The screen converts the stored sales_channel value from underscores to spaces and capitalizes it for display. It does not provide a channel selector or prove that a complete selling workflow is available in that channel.",
        "Read Limits as the stored minimum and maximum amounts. These values are configuration metadata; this screen does not validate a proposed load, issue a card, alter a balance, or show whether historical cards fall outside the current range.",
        "Do not enter or search for customer, card, or transaction data here; no such controls are present. Use permission-controlled reports or operational tooling only when a supported workflow exists and protect full card codes and balances as financial-value credentials.",
        "Current source inspection shows gift-card database/reporting structures, Payment Type metadata, receipt-template display settings, QuickBooks liability mappings, and this configuration surface, but no customer-visible issuance, reload, balance lookup, or redemption component in the active POS source. Do not promise or train a live card workflow until it is implemented and verified end-to-end.",
        "If gift cards are expected to be operational, contact CentriPOS support with the business, location/register, intended issuance/redemption scenario, and the settings summary. Do not create a generic custom payment type as a substitute for a controlled stored-value ledger."
      ],
      "controls": [
        {
          "name": "Gift icon",
          "description": "Exact CentriPOS navigation and disabled-state icon for Products → Gift Cards."
        },
        {
          "name": "Shared settings row",
          "description": "The tenant gift_card_settings record read here and edited in Admin → Store Credit & Gift Cards."
        },
        {
          "name": "Gift Cards are not enabled",
          "description": "Displayed when no settings row is returned or is_enabled is false."
        },
        {
          "name": "Enable gift cards button",
          "description": "Currently visual only: no click handler is attached, so it does not enable or save anything."
        },
        {
          "name": "Sales channel",
          "description": "Read-only formatted display of the stored sales_channel value; no selector exists on this page."
        },
        {
          "name": "Limits",
          "description": "Read-only Min/Max display from min_amount and max_amount."
        },
        {
          "name": "Not card management",
          "description": "No card list, code, balance, customer, issuance, reload, redemption, expiration, transaction, search, edit, or delete controls exist here."
        },
        {
          "name": "Admin editor",
          "description": "Admin → Store Credit & Gift Cards is the current wired configuration surface."
        },
        {
          "name": "Payment Type metadata",
          "description": "A separate enabled payment-type label is not proof that a stored-value issuance/redemption workflow is implemented."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /catalog/gift-cards in an enabled settings-summary state. It shows only Sales channel and Limits; no gift-card numbers, balances, or customer records are exposed."
        }
      ],
      "expectedResult": "The gift-card product or program follows the intended sale, activation, balance, redemption, location, and receipt behavior in a controlled test.",
      "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."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/catalog-gift-cards.png",
        "alt": "Harbor & Hearth Gift Cards screen showing the in-store sales channel and configured gift-card value limits in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-list",
      "url": "https://platform.getcentri.com/centripos/customer-list",
      "title": "Use the Contacts list",
      "summary": "Search and filter active customer records, open shareable profiles, export all permitted matches, and run controlled page-scoped bulk relationship or merge actions.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "Open Contacts → Contacts with the Users icon. This is a tenant-wide customer-record surface containing personal and financial information. Search, quick view, page, and the open profile ID are stored in the authenticated page URL, but access still requires the signed-in user’s tenant permissions. Export and bulk actions are separately permission-controlled. No customer-list screenshot is published because the Harbor & Hearth capture was rejected as sensitive.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Contacts and confirm the active business. The count beneath Contacts is the number of active customer records matching the current quick view and search—not always the tenant’s unfiltered lifetime contact count. Archived or inactive records excluded by the active-customer lookup helper do not participate.",
        "Use Search names, phone, email, address, company…. Input waits about 300 milliseconds, normalizes spaces, resets to page 1, and writes q to the URL. It searches customer code, name, company, primary email and phone, legacy/full address fields, street lines, city, state, ZIP, imported code and external ID, contact role, and internal customer ID.",
        "Understand multi-term search. Up to eight parsed words, email-like tokens, or digit groups are applied one after another, so every term must match at least one supported column. A phone-shaped query is split into digit groups to tolerate common formatting. Search does not inspect notes, additional phone-line arrays, sales, groups, associations, or activity.",
        "Choose All, Has phone, Has email, Companies, Imported, or Balances. Has phone and Has email require a non-null primary field, even if it contains an empty legacy value. Companies requires non-null company_name. Imported requires non-null source_external_id—not merely a local or imported-looking customer code.",
        "Balances includes a customer when account balance is greater than zero or store-credit balance is greater than zero. It excludes zero and negative balances and does not net the two amounts. The row’s Balance column displays only customer account balance; open the profile or Store credit workspace for store-credit detail.",
        "Clear Search with X and return to All before treating a contact as missing. Search and quick-view changes reset pagination and clear any selected rows. The URL preserves q, nondefault view, and zero-based page state for an authenticated permitted user.",
        "Read a row. Contact shows avatar initials, customer name or Unknown, local customer code, and company. The next Contact column shows primary email and phone. Address shows street/city/state/ZIP or the legacy address. Balance is the customer account balance. On mobile, address and company are omitted from the compact card.",
        "Choose the row outside its selection checkbox to open the Customer Profile. The URL stores profileCustomerId so browser history or a copied authenticated link can reopen that customer. Closing the panel removes the profile parameter without discarding the list search, view, or page.",
        "Use Prev and Next when more than 50 records match. The footer shows the displayed range and Page n of total. Server pagination first orders by customer_name; the 50 rows on each page are then locally reordered so named profiles appear before email-only, phone-only, and otherwise unidentified records. Do not assume the visible sequence is one globally sorted alphabetic list across pages.",
        "Choose Add Contact to create a customer. Search first, because Add Contact does not mean the current search proved no duplicate exists; the New Customer save performs its own email/phone check according to tenant duplicate policy.",
        "Export appears only with customers.export permission. Choose Export as XLSX or Export as CSV. Export fetches every active contact matching the current search and quick view in stable 1,000-row batches; it is not limited to the visible 50-row page or currently selected checkboxes.",
        "Review export contents before sharing. It includes local and imported codes, internal customer ID, display name, company, primary email and phone, address fields, full address, account balance, store-credit balance, credit limit, tax-exempt flag, contact-only-profile classification, created time, and last-updated time. The file is named contacts-export-YYYY-MM-DD and contains a Contacts sheet for XLSX.",
        "If no contacts match the export filters, CentriPOS stops with No contacts match the current export filters. Treat the exported file as sensitive customer and financial data: save it only to an approved location, share with the minimum audience, and delete stale copies according to policy.",
        "Bulk selection appears only when tenant-management authority or an Owner, Store Owner, Super Admin, or Manager role is verified. If permission resolution fails, the destructive controls remain hidden. The duplicate-scanner banner has a narrower owner/admin gate and does not automatically appear for every manager.",
        "Check individual rows or choose Select all contacts on this page. The header checkbox selects only the current 50-row page. Changing tenant, search, quick view, or page clears the entire selection, so bulk actions cannot silently span pages. Read the selected count before acting.",
        "Choose Merge only with exactly two selected contacts. It loads their current complete records and opens the irreversible field-by-field merge dialog. One selected row says Select one more contact; more than two says Merge compares exactly two contacts at a time.",
        "Choose Add to group to select one existing alphabetized customer group. Existing memberships are kept. CentriPOS avoids duplicate customer-ID membership; it can safely attach one unambiguous legacy email-only membership to its exact customer, and avoids duplicating an ambiguous shared-email legacy row. No group found means create one under Contacts → Groups first.",
        "Choose Add to association to select one existing Household or Company association. Existing member links are kept; new links store the selected customer ID and display label. This does not copy association profile fields, set company member roles, or merge customers. Configure those details in Contacts → Associations.",
        "On a touch phone, the group/association destination opens as a bottom picker sheet; on desktop it uses a dialog. Search the destination list, select the exact row, then choose Add. The picker cannot be dismissed while the save is in progress.",
        "Choose Clear to leave selection mode without changing customer records. After any bulk action, open the destination Group or Association and a representative Customer Profile to confirm membership. After Merge, verify the surviving record and financial/history reconciliation separately.",
        "Interpret empty states precisely. No contacts match your search means q excluded every active record. No contacts found means the current quick view/source has no rows without a search. Neither state proves the tenant never had a customer or that inactive records do not exist.",
        "The owner/admin duplicate scanner can appear above the list when pending shared-email or phone candidates exist. A candidate is review evidence, not a confirmed duplicate; use Ignore, Household, or the full Merge comparison according to verified identity.",
        "No real screenshot is shown for this article. The Harbor & Hearth manifest explicitly marks /contacts/list rejected-sensitive-customer. The help center keeps this guide text-only rather than exposing customer records or substituting an invented list."
      ],
      "controls": [
        {
          "name": "Users icon",
          "description": "The exact CentriPOS navigation icon for Contacts → Contacts."
        },
        {
          "name": "Matching contact count",
          "description": "Active records remaining after the current quick view and search."
        },
        {
          "name": "Search",
          "description": "Debounced multi-term query across identity, contact, address, source, role, code, and internal ID fields."
        },
        {
          "name": "Search term rule",
          "description": "Every parsed term must match some supported column; up to eight terms are applied."
        },
        {
          "name": "Phone-shaped search",
          "description": "Splits normalized digits into groups to tolerate displayed phone formatting."
        },
        {
          "name": "All",
          "description": "Removes the quick-view condition while retaining search."
        },
        {
          "name": "Has phone",
          "description": "Non-null primary customer_phone only; additional-phone arrays are not queried."
        },
        {
          "name": "Has email",
          "description": "Non-null primary customer_email."
        },
        {
          "name": "Companies",
          "description": "Non-null company_name; this is not the Associations Company list."
        },
        {
          "name": "Imported",
          "description": "Non-null source_external_id."
        },
        {
          "name": "Balances",
          "description": "Positive account balance or positive store-credit balance; row Balance still shows account balance only."
        },
        {
          "name": "Clear search",
          "description": "Removes q and returns to page 1."
        },
        {
          "name": "Contact row",
          "description": "Name/code/company, primary email/phone, address, and account balance; opens the profile outside the checkbox."
        },
        {
          "name": "profileCustomerId",
          "description": "URL state for the open authenticated customer profile."
        },
        {
          "name": "Page size",
          "description": "50 server-returned active contacts."
        },
        {
          "name": "Local page sort",
          "description": "Within-page tier ordering: named, email-only, phone-only, then unidentified."
        },
        {
          "name": "Prev / Next",
          "description": "Move through server pages and clear selection."
        },
        {
          "name": "Add Contact",
          "description": "Opens the New Customer sheet; existing-contact search and duplicate policy still apply."
        },
        {
          "name": "Export permission",
          "description": "customers.export capability required before Export renders."
        },
        {
          "name": "Export scope",
          "description": "Every active contact matching current search and quick view, fetched in 1,000-row batches; not the page or selection."
        },
        {
          "name": "Export fields",
          "description": "Codes, internal ID, identity/contact/address, balances, credit limit, tax flag, contact-only flag, created, and updated values."
        },
        {
          "name": "XLSX / CSV",
          "description": "Sensitive contacts-export-YYYY-MM-DD file formats."
        },
        {
          "name": "Bulk-action permission",
          "description": "Verified tenant manager, Owner, Store Owner, Super Admin, or Manager."
        },
        {
          "name": "Select row",
          "description": "Adds only that visible contact to the current page selection."
        },
        {
          "name": "Select all contacts on this page",
          "description": "Selects the current page only."
        },
        {
          "name": "Selection reset",
          "description": "Tenant, search, view, or page change clears selected IDs."
        },
        {
          "name": "Merge",
          "description": "Enabled for exactly two selected contacts."
        },
        {
          "name": "Add to group",
          "description": "Keeps existing membership and adds missing selected customer IDs to one existing group."
        },
        {
          "name": "Legacy group-email guard",
          "description": "Maps one unambiguous email-only membership or avoids adding duplicates when a shared email is ambiguous."
        },
        {
          "name": "Add to association",
          "description": "Keeps existing links and inserts missing member relationships into one existing household/company."
        },
        {
          "name": "Touch destination sheet",
          "description": "Phone bottom picker for group or association; desktop uses a dialog."
        },
        {
          "name": "Clear",
          "description": "Leaves bulk-selection mode without changing contacts."
        },
        {
          "name": "Duplicate scanner",
          "description": "Owner/admin-only pending shared-email/phone review queue."
        },
        {
          "name": "No contacts match your search",
          "description": "Search-empty active result."
        },
        {
          "name": "No contacts found",
          "description": "Unsearched current-view/source empty result."
        },
        {
          "name": "Sensitive screenshot boundary",
          "description": "The exact Harbor & Hearth customer list was rejected, so no screenshot is published."
        }
      ],
      "expectedResult": "The active Contacts count, 50-row page, quick view, and every multi-term search result reconcile to the documented query fields; export contains every permitted match rather than only the page or selection; bulk actions affect only the reviewed page-selected IDs with the required authority; profile URL state reopens the intended customer; and no sensitive customer record appears in public screenshots or uncontrolled exports.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "create-edit-customer",
      "url": "https://platform.getcentri.com/centripos/create-edit-customer",
      "title": "Create or edit a customer",
      "summary": "Create one clean customer identity, or safely update its receipt routing, labeled phones, company context, account fields, address, group, associations, tax status, and profile image.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "Search Contacts by more than one identity field before creating a record. Only Name is required in the current New Customer sheet; email and phone are optional. When duplicate customers are not explicitly allowed for the tenant, an exact case-insensitive email match or normalized phone match stops Save. The customer list and profile are sensitive surfaces, so this article intentionally has no Harbor & Hearth customer screenshot.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Contacts and search name, email, phone, company, address, contact code, and imported identifiers. Open a possible match and compare identity and history before choosing Add Contact. A missing email or different spelling does not prove the person is new.",
        "Choose Add Contact only when no correct profile exists. The New Customer sheet opens directly in editing mode and shows Details only; Activity, Store credit, Account, Payment methods, Notes, profile image controls, Associations, and generated profile identifiers become available only after the record exists.",
        "Enter Name. It is the only field that enables Save and is trimmed before storage. Email and Phone can be blank, but leaving both empty makes later duplicate detection, communication matching, receipt delivery, and contact lookup less reliable.",
        "Enter the primary Email only after confirming spelling and customer authorization. CC emails are additional visible recipients on supported receipts and account invoices; BCC emails receive private copies. CentriPOS parses, normalizes, deduplicates, and prevents the primary email from being repeated in CC or BCC. Keep routing recipients necessary and current.",
        "Choose the primary Phone label: Mobile, Office, Home, Main, Fax, or Other. Enter the number using the tenant’s country formatting. On save, CentriPOS normalizes the primary number for storage and creates a primary labeled phone-line entry when a usable number exists.",
        "Use Additional phones for separate labeled numbers. Choose Add, select Mobile, Office, Home, Main, Fax, or Other, and enter the number. Empty additional lines are discarded; duplicate numbers are removed from the saved phone-line array. Use X to remove only the draft additional line.",
        "Enter Company and Role when they describe this person’s business relationship. These text fields do not create a Company association, make the customer a company bill-to identity, or assign a billing/requester role. Use Contacts → Associations after creation for those relationship controls.",
        "Complete any Account fields shown. These are tenant-configured customer fields and render as text, date, or number inputs according to General setup. Blank entries are removed from the saved accounting-field object. Do not use them for payment credentials or unrelated sensitive data.",
        "Enter Street address manually or choose the exact Address suggestion. Selecting a suggestion replaces Street, City, State, and ZIP from the parsed result; it does not fill Street address 2. Verify apartment, suite, delivery location, city, state, and ZIP before saving.",
        "Choose Customer Group when groups exist. This sheet exposes one selector—No group or one group—even though other bulk or imported workflows can create multiple membership rows. Saving from this form replaces memberships in the known group scope with the selected single group, so review a multi-group customer before editing.",
        "For a new customer, Associations is intentionally absent. Save the customer first, reopen the profile, and use Associations to add one or more existing household/company links. Association membership remains separate from Company text and Customer Group.",
        "Turn on Tax exempt only with approved documentation and policy. The saved flag tells supported checkout not to charge sales tax for this customer; it does not validate a certificate, set an expiration, choose exempt products, or update prior sales.",
        "Choose Save once. CentriPOS compares the entered email case-insensitively and compares primary phone numbers using digits, including a leading-country-code-tolerant comparison. When duplicates are disallowed and a match exists, the warning names the likely customer and the save stops. Review that profile instead of altering punctuation merely to bypass the control.",
        "If the tenant’s Allow duplicate customers setting is enabled, the client duplicate check is skipped. That setting is permissioned business policy, not evidence that a second record is correct. Create separate people sharing an email or phone only with clear identity evidence, then use Associations if they are related.",
        "On successful creation, CentriPOS assigns a new internal customer ID, generates the customer code through the stored record, initializes account balance to zero, saves selected group membership, closes the sheet, and returns the created customer to the opening workflow when supported. Search again and open it before relying on the record.",
        "To edit, open the Customer Profile → Details and choose Edit contact. The form loads the current primary/CC/BCC emails, labeled phones, company, role, account fields, address, group, and tax status. Existing association links can be added or removed in the Associations manager while editing.",
        "Change only the intended fields. Updating Email also rewrites the selected group membership’s stored fallback email when group membership is being saved. Changing group selection or primary email can remove and recreate memberships within the groups known to this form; recheck the customer’s group state afterward.",
        "Choose Cancel to discard draft text, address, group, and tax changes. In New Customer mode Cancel closes the unsaved sheet; in an existing profile it exits editing. Association Add/Remove controls act immediately through their own relationship writes, so do not assume Cancel reverses an association change already confirmed.",
        "Choose Save to update the existing record under the current tenant and customer ID. The customer code, imported source identifiers, balances, history, associations, notes, payment methods, and activity are not replaced by ordinary field editing. Reopen Details and verify every intended value and routing recipient.",
        "Manage a profile image only after the customer exists. The image menu can Upload / take picture, Replace image, Edit crop, or Delete image. Images are stored under the customer’s tenant and ID in product-media storage. Confirm the photo is appropriate, authorized, and belongs to the right person.",
        "After creation or editing, test the actual dependent workflow: send a controlled receipt when email routing changed, confirm phone sender/matching behavior when phones changed, inspect fulfillment address, attach the customer in Sell to check tax and price-book behavior, and verify Groups and Associations from their dedicated screens.",
        "No real customer-record screenshot is published for this guide. The Harbor & Hearth screenshot manifest marks /contacts/list rejected-sensitive-customer, and no safe exact New Customer capture is assigned. The guide stays text-only rather than inventing a profile or exposing customer data."
      ],
      "controls": [
        {
          "name": "Add Contact",
          "description": "Opens New Customer directly in Details edit mode."
        },
        {
          "name": "Name",
          "description": "Only required field; trimmed and used as the customer display identity."
        },
        {
          "name": "Email",
          "description": "Optional primary routing and matching address."
        },
        {
          "name": "CC emails",
          "description": "Normalized additional visible recipients for supported receipts and account invoices."
        },
        {
          "name": "BCC emails",
          "description": "Normalized private recipients; primary and CC duplicates are removed."
        },
        {
          "name": "Phone label",
          "description": "Mobile, Office, Home, Main, Fax, or Other."
        },
        {
          "name": "Phone",
          "description": "Optional normalized primary number and primary phone-line source."
        },
        {
          "name": "Additional phones",
          "description": "Separate labeled numbers; blank and duplicate values are discarded on save."
        },
        {
          "name": "Company",
          "description": "Free-text affiliation; it does not create a Company association."
        },
        {
          "name": "Role",
          "description": "Free-text responsibility; it does not assign association billing or requester permissions."
        },
        {
          "name": "Account fields",
          "description": "Tenant-configured text, date, or number customer fields; blank values are omitted."
        },
        {
          "name": "Address suggestion",
          "description": "Replaces parsed street, city, state, and ZIP after selection; Street address 2 remains separate."
        },
        {
          "name": "Customer Group",
          "description": "Single No group/one group selector whose save can replace known-scope memberships."
        },
        {
          "name": "Associations",
          "description": "Existing-customer-only immediate relationship manager for one or more household/company links."
        },
        {
          "name": "Tax exempt",
          "description": "Customer checkout tax flag requiring verified business authority."
        },
        {
          "name": "Duplicate check",
          "description": "Stops save on case-insensitive primary email or normalized primary-phone match unless duplicates are tenant-enabled."
        },
        {
          "name": "Allow duplicate customers",
          "description": "Tenant setting that skips the client warning; it does not prove the records should be separate."
        },
        {
          "name": "Save new customer",
          "description": "Creates a UUID-backed tenant customer, zero account balance, generated code, and selected group link."
        },
        {
          "name": "Edit contact",
          "description": "Loads editable identity, routing, phone, account, address, group, association, and tax controls."
        },
        {
          "name": "Cancel",
          "description": "Closes an unsaved new record or exits field editing; it does not reverse an already completed association write."
        },
        {
          "name": "Save existing customer",
          "description": "Updates editable fields without changing the customer ID or intentionally replacing history and balances."
        },
        {
          "name": "Customer image",
          "description": "Existing-record upload/camera, crop, replace, or delete controls."
        },
        {
          "name": "Post-save verification",
          "description": "Reopen profile and test communication, fulfillment, tax, pricing, group, and association behavior affected by the change."
        },
        {
          "name": "Sensitive screenshot boundary",
          "description": "No customer-list or New Customer screenshot is published until an exact safe Harbor & Hearth capture exists."
        }
      ],
      "expectedResult": "One intended customer ID and code exist with the reviewed name, normalized email routing, labeled deduplicated phones, company/role, configured account fields, verified address, tax flag, group and association links; duplicate policy was respected; sensitive profile imagery and data remain private; and controlled communication, fulfillment, Sell pricing/tax, Group, and Association checks reflect the saved changes.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-profile",
      "url": "https://platform.getcentri.com/centripos/customer-profile",
      "title": "Understand the customer profile",
      "summary": "Use the customer profile’s six real tabs to review contact details, activity, store credit, account history, safe payment tokens, and internal notes.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "Open the profile only for the intended customer. The panel can expose customer contact information, purchase and balance history, communications, service context, saved payment tokens, and internal notes according to the signed-in user’s permissions and enabled integrations. CentriPOS does not currently provide a Files tab, a separate Sales tab, or a separate Conversations tab in this profile.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Open the intended customer from Contacts or from a supported customer action in Sell, receipts, reports, Customer Accounts, communications, or another customer-aware workspace. Confirm the name, avatar or initials, email or phone, and contact-record summary before acting.",
        "Use the profile header to close the panel, copy the contact record, or manage the customer image. The image menu can upload or take a picture, replace an uploaded image, edit its crop, or delete it. These image actions change this customer’s profile image; they do not change the business logo.",
        "On desktop, move among Details, Activity, Store credit, Account, Payment methods, and Notes in the tab row. On a phone, the active tab is shown in the sticky header and the menu lists the other tabs. A legacy request for Conversations opens Activity; there is no separate Conversations tab.",
        "Start with Details. Review email, CC and BCC routing addresses, labeled primary and additional phone lines, company, role, and address. The email, call, and map actions open the device’s supported email, phone, or Google Maps handler. The text shortcut beside a phone currently reports that CRM text messaging is coming soon; use the Activity composer for supported Dialpad SMS.",
        "Review the Details profile section for contact code, imported contact code, lead-versus-customer type, internal contact ID, group, associations, credit limit, and customer-since date. A record with completed sales is shown as Customer; otherwise it is shown as Lead. Associations identify linked household or company units without merging the individual record.",
        "Treat warning banners as operational signals. Review duplicates opens the duplicate-management flow when a possible duplicate exists. Internal-note and colored flag warnings indicate staff context attached to this customer; read the Notes tab before proceeding with a sensitive sale or service action.",
        "Choose Edit contact to change the name, customer-facing email routing, labeled phone lines, company, role, configured accounting fields, street address, customer group, associations, or Tax exempt status. Tax exempt means sales tax is not charged at checkout for this customer, so change it only from verified documentation. Duplicate-email or phone protection can stop the save unless the tenant explicitly allows duplicate customers.",
        "Use View sales only when that action is available from the screen that opened the profile. Use Start sale to begin a sale with this customer attached. These are actions below Details, not a Sales tab. If the customer is linked to QuickBooks and the user has permission, Open in the QuickBooks section opens that linked accounting customer.",
        "Review any customer-financing section on Details only when the tenant has a supported financing integration. Financing controls and QuickBooks links can be absent because of configuration or permission; their absence does not mean the customer record failed to load.",
        "Choose Activity for the newest-first customer timeline. It combines matched Dialpad calls and SMS, CRM activity, CentriPOS notices and receipt communications, service tickets, and interaction reports. Source badges and counts explain what contributed; matching is customer-specific but should still be checked against the displayed phone, email, receipt, or service context.",
        "Filter Activity with All, Calls, SMS, CRM, CentriPOS, Service, or Interactions. Open a timeline item for the available summary, transcript, recording, external source, receipt, service, or linked-note context. A filter with no rows means no matched activity in that category, not that the customer has never communicated with the business.",
        "Choose Refresh from CRM to request a fresh customer-activity sync when identity data is present. The result can import or enrich CRM and recent Dialpad events. Review any warning that the Dialpad portion did not complete; a successful general refresh message is not proof that every external provider returned data.",
        "Use the Activity composer for a supported Dialpad call or SMS. Verify Send to and Send from, especially when more than one business number is available. SMS can be sent immediately or scheduled where enabled; call and message controls remain disabled until Dialpad is connected, the customer has a usable phone number, and an allowed sender is selected.",
        "Choose Store credit to see the current balance and the latest 50 ledger entries. Each entry shows Issued, Redeemed, Refund, Adjusted, or Expired; amount direction; balance after; notes; date and time; and a Closure link when a register session is recorded. The current balance comes from the customer balance record, while the ledger explains the recorded changes.",
        "Use Add, Refund, or Reduce only after verifying the customer and reason. Enter a positive amount and a required note. Reduce is disabled when no balance is available and is capped at the displayed balance. When an active register session exists, the adjustment records that session; use the Closure link to trace it later.",
        "Choose Account to distinguish truly open customer-account debt from saved or resumable potential sales. Review Open account balance, Credit limit, Saved potential, Total spent, and Total sales, then inspect pending A/R invoices, unlinked on-account sales, resumable saved or parked sales, and recent completed sales. A stored-balance difference is a reconciliation warning, not a second amount due.",
        "Continue a saved or parked sale only after checking its customer, items, payments, fulfillment, and status. If the current cart already has items, CentriPOS asks for confirmation before replacing the working sale. Supported e-cart controls can create or reuse the branded customer cart link for that saved sale; do not expose an underlying database or function URL.",
        "Choose Payment methods to review tokenized payment references from CentriPay Online, NMI Gateway, or Payanywhere. Rows show a safe provider label, card brand or type, last four digits when available, origin, and default state—not a full card number or security code. Add Card appears only for the NMI tokenization flow when its key is configured.",
        "Set default only on a supported saved card that should be preferred for later authorized payments. Delete removes the saved token after confirmation; it does not refund a sale. If no payment connection is active, use Open CentriPay Hub to configure the supported provider rather than collecting card data in notes or another text field.",
        "Choose Notes for internal operational context. Add a normal note or one colored Flag note; a new flag clears the previous active flag for this customer. Notes can carry links back to a sale, receipt, interaction, CRM event, or other supported context, and CentriPOS attempts to sync created or edited notes through CRM Connect. Read any warning when the POS note saved but CRM sync needs review.",
        "Only an owner or admin can manage existing notes through the permission-gated edit and delete controls. Deleting a note can also remove its synchronized CRM copy. Never put full payment credentials, passwords, government identifiers, medical detail, or unrelated sensitive information in a customer note.",
        "Close and reopen the profile from the intended workflow. Confirm the selected customer, saved Details, association and tax status, activity source and sender, store-credit ledger, open-account records, safe payment-token label, and internal note or flag. If one integration-backed panel is empty, verify its connection and permission before assuming customer data is missing."
      ],
      "controls": [
        {
          "name": "Profile header",
          "description": "Customer name, image or initials, contact summary, copy-record action, image menu, and close control."
        },
        {
          "name": "Customer image menu",
          "description": "Upload or take picture, replace image, edit crop, or delete this customer’s profile image."
        },
        {
          "name": "Details",
          "description": "Contact information, customer identity, classification, associations, tax status, integrations, and profile actions."
        },
        {
          "name": "Email / phone / map action",
          "description": "Opens the supported device handler for the exact displayed address or number."
        },
        {
          "name": "Phone text shortcut",
          "description": "Currently reports CRM text messaging is coming soon; supported SMS is composed from Activity."
        },
        {
          "name": "Contact code / imported contact code",
          "description": "Copyable customer identifiers retained for local or imported records."
        },
        {
          "name": "Type",
          "description": "Customer after completed sales exist; otherwise Lead."
        },
        {
          "name": "Group",
          "description": "The customer’s selected contact group, used only by workflows that support that group."
        },
        {
          "name": "Associations",
          "description": "Links the person to household or company units without merging records."
        },
        {
          "name": "Tax exempt",
          "description": "Stops checkout sales tax for this customer; edit only from verified authority."
        },
        {
          "name": "Review duplicates",
          "description": "Opens duplicate-management when a possible matching record exists."
        },
        {
          "name": "Edit contact",
          "description": "Edits identity, routing emails, labeled phones, company, role, account fields, address, group, associations, and tax status."
        },
        {
          "name": "View sales",
          "description": "Context-dependent shortcut to the customer’s sales; there is no separate Sales tab."
        },
        {
          "name": "Start sale",
          "description": "Begins a sale with the selected customer attached when the opening context provides the action."
        },
        {
          "name": "QuickBooks linked customer",
          "description": "Permission- and configuration-dependent external accounting profile link."
        },
        {
          "name": "Activity",
          "description": "Unified newest-first timeline for Dialpad, CRM, CentriPOS, service, and interaction records."
        },
        {
          "name": "Activity filters",
          "description": "All, Calls, SMS, CRM, CentriPOS, Service, and Interactions with matched counts."
        },
        {
          "name": "Refresh from CRM",
          "description": "Imports or enriches customer activity and reports partial Dialpad refresh failure separately."
        },
        {
          "name": "Send to / Send from",
          "description": "Customer phone and authorized business number used for Dialpad calling or SMS."
        },
        {
          "name": "Call with Dialpad",
          "description": "Starts a connected CTI call only when customer and sender numbers are usable."
        },
        {
          "name": "Send / Schedule SMS",
          "description": "Sends now or schedules through the selected connected sender where supported."
        },
        {
          "name": "Store credit balance",
          "description": "Current customer store-credit amount."
        },
        {
          "name": "Add / Refund / Reduce",
          "description": "Manual store-credit changes requiring a positive amount and a note; Reduce cannot exceed the displayed balance."
        },
        {
          "name": "Transaction history",
          "description": "Latest 50 issued, redeemed, refunded, adjusted, or expired ledger entries with resulting balance."
        },
        {
          "name": "Closure link",
          "description": "Opens the register closure associated with a store-credit transaction when one was recorded."
        },
        {
          "name": "Account",
          "description": "Open debt, credit limit, saved potential, spend and sale totals, A/R invoices, resumable sales, and recent sales."
        },
        {
          "name": "Truly open",
          "description": "Pending A/R invoices plus unlinked open on-account sales, without double-counting linked sale rows."
        },
        {
          "name": "Saved potential",
          "description": "Amount represented by resumable saved or incomplete sales; it is not current account debt."
        },
        {
          "name": "Continue sale",
          "description": "Restores the selected resumable sale and can replace a nonempty current cart after confirmation."
        },
        {
          "name": "Payment methods",
          "description": "Safe token references from configured CentriPay Online, NMI Gateway, or Payanywhere connections."
        },
        {
          "name": "Add Card",
          "description": "NMI tokenization form shown only when a tokenization key is configured."
        },
        {
          "name": "Default payment method",
          "description": "Preferred supported token for later authorized payments."
        },
        {
          "name": "Delete payment method",
          "description": "Removes the saved token after confirmation; it does not refund or void a payment."
        },
        {
          "name": "Open CentriPay Hub",
          "description": "Takes the user to payment-provider setup when no supported connection is active."
        },
        {
          "name": "Notes",
          "description": "Internal staff notes and contextual links for this customer."
        },
        {
          "name": "Flag note",
          "description": "One color-coded pinned warning; creating another active flag clears the previous flag."
        },
        {
          "name": "CRM Connect note sync",
          "description": "Attempts to mirror created or edited POS notes and warns when external sync needs review."
        },
        {
          "name": "Owner/admin note controls",
          "description": "Permission-gated edit and delete actions for existing notes."
        },
        {
          "name": "Not available here",
          "description": "No Files tab, separate Sales tab, or separate Conversations tab exists in the current customer profile."
        }
      ],
      "expectedResult": "The six-tab profile belongs to the intended customer; Details, Activity, Store credit, Account, Payment methods, and Notes reconcile to the correct identity and permissions; communication sender, tax status, associations, open debt versus saved potential, store-credit ledger, safe payment-token label, and note/flag state are verified; and no nonexistent Files, Sales, or separate Conversations tab is implied.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "companies-households",
      "url": "https://platform.getcentri.com/centripos/companies-households",
      "title": "Use Customer Associations",
      "summary": "Connect separate customer records as households or companies, coordinate shared profile and billing details, and review their combined receipt context without merging anyone.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "Open Contacts → Associations with the same Home icon used in CentriPOS. An association is a relationship layer: every member remains a separate customer with a separate profile, store credit, account balance, payment methods, notes, and activity. Some optional sync settings intentionally copy selected association data into member records, so review them before Update.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Associations. The Harbor & Hearth screen heading is Customer Associations. Choose All, Household, or Company, then use Search associations or members before creating a record; the search covers association identity, contact and billing fields, notes, and linked-member identity fields.",
        "Read the list before editing. Each association card shows its Home or Building icon, name, Household or Company badge, member count, completed/refunded sales summary when present, and available address, company contact, billing, checkout, and note summaries. Click the card to expand it; use the pencil to edit without expanding or the trash action to delete.",
        "Choose New association only when the household or company does not already exist. Select Household for a shared family or residence, or Company for an organization with bill-to and checkout controls. Enter the required Name or Company name.",
        "Enter the Shared address for a household or Company address for a company: street, second line, city, state, and ZIP. Add Notes only for association-level operational context. These values do not automatically overwrite member profiles unless the matching Sync to members options are enabled and the existing association is updated.",
        "For a company, add Company email and Company phone as the organization’s general contact details. These are association fields; they do not replace a linked person’s own email or phone.",
        "In Bill-to and invoicing for a company, set Bill-to name, Invoice email, Billing phone, Terms, and Invoice delivery: Email, Mail, Portal, QuickBooks, or Other. Add comma-separated Invoice CC and BCC emails and Billing instructions only for approved recipients and routing requirements.",
        "Turn on Require authorization / PO / reference when staff must obtain a reference before billing or delivery. This creates a visible operational warning; it does not manufacture or validate the authorization number.",
        "Leave Use company address for bill-to on when the billing office uses the company address. Turn it off to enter a distinct bill-to street, second line, city, state, and ZIP. Verify the recipient and address before issuing an invoice.",
        "In Checkout, turn on Available at checkout only when the company may be selected on Sell as the bill-to identity. CentriPOS then maintains a dedicated bill-to customer record for that company. Turn on Require requested by to make the cashier select a linked contact when billing the company. Turning checkout off also clears the requester requirement.",
        "Use Sync to members deliberately. Keep member address aligned copies the association address into every current member’s customer profile when an existing association is updated. Keep member company name aligned copies the association name into the members’ Company field. These are real record updates, not display-only inheritance.",
        "Copy notes to members with an origin label inserts the association note into each current member’s Notes as “[Company note from …]” or “[Household note from …]”. CentriPOS avoids inserting the same exact origin-tagged text twice, but editing the association note can create a new distinct note. Do not enable this for private or irrelevant association context.",
        "Choose Create or Update. New associations save their profile, but member synchronization has no members to affect yet. For an existing association, enabled profile and note sync runs after the association update against the members linked at that time. Reopen the record and verify the intended fields.",
        "Expand the association and choose Add member. Search at least two characters by customer name, email, phone, company, contact code, or imported contact code, then choose the exact existing customer. This links the customer; it does not create, clone, or merge a customer record.",
        "Click a member’s name to open that customer’s full profile. Remove the member with X only when the relationship should end; removal deletes the association link, not the customer or their history. A customer can be linked to more than one association when the business relationship requires it.",
        "For company members, choose Role to enter free-text responsibility such as purchaser or accounts payable. Toggle Bill-to to mark a billing contact. Toggle Requester to allow or disallow order requests; the “No order requests” badge appears when the stored permission is off. These member attributes do not make one customer the owner of the others.",
        "Review the expanded association’s completed, refunded, and partially refunded sales summary. The total is built from matched member sales in the loaded association view, and the card shows up to five recent rows. Choose View history to open Receipts scoped to all current member customer IDs and labeled with the association name. This is a combined filter, not a combined receipt owner or account balance.",
        "For a checkout-enabled company, review QuickBooks customer. Find/link or Rematch is available only to permitted owners, finance leaders, or super admins. CentriPOS matches the dedicated company bill-to customer—not each member—to an existing QuickBooks customer or, with explicit approval, creates a new one.",
        "In Match QuickBooks customer, compare the CentriPOS company name, email, and phone with every candidate, choose the exact existing QBO ID, then Link selected QBO customer. If no confident match exists, Create new QBO customer requires explicit approval. Use Open to inspect an established link. Never create a second QBO customer merely because an expected candidate is absent.",
        "Delete an association only after reviewing members, checkout use, price books, receipt filters, billing setup, and the QBO link. The confirmation states that all member links will be removed. Customer records and their individual histories remain, but the association relationship and its configuration are deleted.",
        "Interpret empty states precisely. No customer associations yet means none exist for the tenant. No associations match the current filters means the type filter or search excluded every association; clear Search and return to All before assuming the record is missing.",
        "Verify from both sides: reopen the association, inspect each intended member profile’s Associations field, test the optional company bill-to selection and requester rule in Sell, and open View history. Confirm that individual customer identity and financial history remain separate."
      ],
      "controls": [
        {
          "name": "Home icon",
          "description": "The exact CentriPOS navigation icon for Contacts → Associations and the icon used for household records."
        },
        {
          "name": "Building icon",
          "description": "Identifies a Company association in the list and editor."
        },
        {
          "name": "All / Household / Company",
          "description": "Routes and filters the association list by relationship type."
        },
        {
          "name": "Search associations or members",
          "description": "Searches association profile, billing, notes, and linked-member identity fields."
        },
        {
          "name": "New association",
          "description": "Opens the Household or Company association editor."
        },
        {
          "name": "Household",
          "description": "Shared relationship record with name, address, notes, member links, and optional member synchronization."
        },
        {
          "name": "Company",
          "description": "Organization relationship record with contact, bill-to, checkout, QuickBooks, and member-role controls."
        },
        {
          "name": "Name / Company name",
          "description": "Required association identity."
        },
        {
          "name": "Company email / phone",
          "description": "Organization-level general contact fields; they do not replace member contact details."
        },
        {
          "name": "Shared / Company address",
          "description": "Association address and optional source for explicit member-address synchronization."
        },
        {
          "name": "Bill-to name / Invoice email / Billing phone",
          "description": "Company billing identity and destination fields."
        },
        {
          "name": "Terms",
          "description": "Free-text billing terms such as Net 30; CentriPOS displays the instruction but does not independently guarantee collection."
        },
        {
          "name": "Invoice delivery",
          "description": "Saved preference: Email, Mail, Portal, QuickBooks, or Other."
        },
        {
          "name": "Invoice CC / BCC emails",
          "description": "Additional billing recipients parsed from comma-separated input."
        },
        {
          "name": "Require authorization / PO / reference",
          "description": "Warns staff that a billing or delivery reference is required; it does not validate one."
        },
        {
          "name": "Use company address for bill-to",
          "description": "Uses company address or reveals a separate bill-to address."
        },
        {
          "name": "Billing instructions",
          "description": "Internal routing or document requirements displayed with the expanded company."
        },
        {
          "name": "Available at checkout",
          "description": "Creates or maintains a dedicated company bill-to customer and exposes the company in supported Sell checkout."
        },
        {
          "name": "Require requested by",
          "description": "Requires selection of a linked contact when the checkout-enabled company is billed."
        },
        {
          "name": "Keep member address aligned",
          "description": "On update, writes the association address into every current member customer record."
        },
        {
          "name": "Keep member company name aligned",
          "description": "On update, writes the association name into each current member’s Company field."
        },
        {
          "name": "Copy notes to members with an origin label",
          "description": "Copies nonempty association notes into current member profiles with a source label and exact-text duplicate guard."
        },
        {
          "name": "Association card",
          "description": "Shows type, members, relevant sales total, address/contact/billing summaries, checkout state, and notes."
        },
        {
          "name": "Expand card",
          "description": "Shows sync and billing badges, instructions, QBO status, members, and recent member-sale context."
        },
        {
          "name": "Add member",
          "description": "Searches existing customers after two characters and inserts a relationship link."
        },
        {
          "name": "Member name",
          "description": "Opens the member’s separate customer profile."
        },
        {
          "name": "Role",
          "description": "Free-text company-contact responsibility stored on the relationship."
        },
        {
          "name": "Bill-to",
          "description": "Marks or unmarks a company member as a billing contact."
        },
        {
          "name": "Requester",
          "description": "Allows or disallows the company member from requesting orders."
        },
        {
          "name": "Remove member",
          "description": "Deletes only the membership link, not the customer."
        },
        {
          "name": "Association sales",
          "description": "Recent completed, refunded, and partially refunded sales belonging to current members."
        },
        {
          "name": "View history",
          "description": "Opens Receipts with every current member ID as a combined association scope."
        },
        {
          "name": "QuickBooks Find/link / Rematch",
          "description": "Permission-gated matching for the checkout company’s dedicated bill-to customer."
        },
        {
          "name": "Link selected QBO customer",
          "description": "Links the exact reviewed QuickBooks customer candidate."
        },
        {
          "name": "Create new QBO customer",
          "description": "Explicitly approved fallback when no correct existing match is available."
        },
        {
          "name": "Delete association",
          "description": "Removes the association and all member links after confirmation, while leaving individual customers intact."
        },
        {
          "name": "No customer associations yet",
          "description": "No association records exist for this tenant."
        },
        {
          "name": "No associations match the current filters",
          "description": "Search or type filter produced an empty result."
        },
        {
          "name": "Relationship boundary",
          "description": "Associations do not merge customers, store credit, account balances, payment methods, notes, or activity histories."
        }
      ],
      "expectedResult": "The association has the intended Household or Company type, profile, billing and checkout configuration, member links and roles; optional address, company-name, and origin-tagged-note sync changed only the intended member records; association-scoped receipt history includes the current members without combining their individual financial records; and any QuickBooks link belongs to the reviewed dedicated company bill-to customer.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/contacts-associations.png",
        "alt": "Harbor & Hearth Customer Associations screen showing household and company filters, association search, and the New association action in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "contact-groups",
      "url": "https://platform.getcentri.com/centripos/contact-groups",
      "title": "Use Customer Groups",
      "summary": "Create and maintain simple customer membership lists for price-book targeting, exports, and other workflows that explicitly support groups.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Groups",
      "introduction": "Open Contacts → Groups with the same Clipboard List icon used in CentriPOS. A group stores a name, optional description, and customer membership links. It does not merge customers, create a company or household, synchronize profile fields, or automatically send a communication. Deleting a group also removes its links from customer price books, so inspect the displayed price-book count first.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Groups. The Harbor & Hearth screen heading is Customer Groups and explains that editable membership keeps Lightspeed imports useful while storefront staff can manage groups.",
        "Review the Groups panel before choosing Add group. Groups are alphabetized. Each card shows name, description or No description yet, member count, price-book count, and Open for the selected group. The first group is selected automatically when groups exist.",
        "Choose Add group. Enter a required Name that staff can interpret later, such as Wholesale, VIP, or Staff, and an optional Description that explains eligibility. Choose Create, then confirm the new group is selected.",
        "Choose a group to open its workspace. On desktop, use the left group list; on mobile, use the group picker above the detail panel. Review the group’s full description, member count, and linked price-book count before changing membership or deleting it.",
        "Choose Edit to update only the group Name and Description. Renaming preserves the group ID, current member links, and price-book links. Recheck downstream labels after a material rename so users do not mistake the old eligibility policy for the new name.",
        "Use Search [group name] members to filter only the selected group’s current members. It matches customer name, email, phone, company, contact code, imported contact code, and stored fallback email. Clearing this field restores every loaded member in that group.",
        "Choose Add members to search the tenant’s existing customers by name, contact or imported code, phone, email, or company. With no query, the picker returns the first 12 alphabetized eligible customers; with a query, it returns up to 25 matches. Customers already in the selected group are excluded.",
        "Review the result’s customer name and supporting code, company, email, phone, or Imported code, then choose the exact customer. The customer is linked immediately and remains available in Contacts under the same customer ID. Add members one at a time; this screen does not create a new contact.",
        "Click a member’s name to open their Customer Profile and confirm identity. Choose Remove to delete only that membership link from the selected group. Removing a member does not delete the customer, alter their other group memberships, or remove individual sales, balances, notes, payment methods, or activity.",
        "Understand downstream pricing. A group’s displayed price books are the customer price books directly assigned to that group. Membership can make a customer eligible when the price book is active, date-valid, channel-valid, and location-valid. Direct-customer and association-targeted price books outrank group targeting in the current Sell resolver.",
        "Treat group membership as explicit operational data. Imports or bulk actions can add memberships, but this screen does not continuously recalculate the group from customer attributes. Changing a customer’s company, spend, balance, or source does not automatically move them into or out of a group.",
        "Choose Delete only after checking the group name, member count, and price-book count. The confirmation explicitly says deletion removes the group from any linked price books. The customer records remain, but their group memberships and price-book targeting through this group end.",
        "Interpret empty states precisely. No customer groups yet means no group records exist. Choose a customer group means none is selected. This group is empty right now means the selected group has no membership rows. No members in this group match your current search means the local member search excluded them. No customers match that search refers only to eligible nonmembers returned by Add members.",
        "Verify one representative member from both directions: open the group and find the customer, then open the customer profile and confirm its Group field. If the group is used by a price book, attach the member in Sell and test the intended product at the intended location and date; also test a nonmember because membership alone does not prove the price resolver applied the book."
      ],
      "controls": [
        {
          "name": "Clipboard List icon",
          "description": "The exact CentriPOS navigation icon for Contacts → Groups."
        },
        {
          "name": "Groups panel",
          "description": "Alphabetized group list with selected state, description, member count, and linked price-book count."
        },
        {
          "name": "Add group",
          "description": "Creates a group from required Name and optional Description."
        },
        {
          "name": "Name",
          "description": "Required staff-facing group identity."
        },
        {
          "name": "Description",
          "description": "Optional explanation of membership purpose or eligibility."
        },
        {
          "name": "Open",
          "description": "Marks the group currently shown in the detail workspace."
        },
        {
          "name": "Member count",
          "description": "Number of customer membership links in the group."
        },
        {
          "name": "Price-book count",
          "description": "Number of customer price books directly linked to the group."
        },
        {
          "name": "Mobile group picker",
          "description": "Phone-sized replacement for the desktop Groups panel."
        },
        {
          "name": "Edit",
          "description": "Renames the group or changes its description without replacing its ID or links."
        },
        {
          "name": "Search group members",
          "description": "Filters current members by identity, contact, company, customer code, imported code, or fallback email."
        },
        {
          "name": "Add members",
          "description": "Opens the existing-customer picker and excludes current members."
        },
        {
          "name": "Add-member search",
          "description": "Returns 12 alphabetized eligible customers without a query or up to 25 matching eligible customers with a query."
        },
        {
          "name": "Member row",
          "description": "Shows the linked customer name and available code, company, email, phone, or imported code."
        },
        {
          "name": "Member name",
          "description": "Opens the separate Customer Profile for identity verification."
        },
        {
          "name": "Remove",
          "description": "Deletes the selected membership link only."
        },
        {
          "name": "Price-book eligibility",
          "description": "Group membership is one condition; active state, dates, channel, location, product, and higher-ranked customer or association targeting still affect the applied price."
        },
        {
          "name": "Delete",
          "description": "Deletes the group, membership links, and linked price-book assignments after confirmation; customer records remain."
        },
        {
          "name": "No customer groups yet",
          "description": "No group records exist for the current tenant."
        },
        {
          "name": "Choose a customer group",
          "description": "No group is selected for detail."
        },
        {
          "name": "This group is empty right now",
          "description": "The selected group has no members."
        },
        {
          "name": "No members in this group match your current search",
          "description": "The selected group has members, but its local search hides all of them."
        },
        {
          "name": "No customers match that search",
          "description": "The Add members picker found no eligible nonmember customer."
        },
        {
          "name": "Membership boundary",
          "description": "A group does not merge contacts, synchronize customer fields, create an association, send messages, or dynamically recalculate membership."
        }
      ],
      "expectedResult": "The named group appears once with the intended description and membership links; representative member identity is verified in the Customer Profile; displayed member and price-book counts reconcile; a supported price-book test distinguishes a member from a nonmember under the correct date, channel, location, and targeting precedence; and no merge, field sync, message send, or dynamic-membership behavior is inferred.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/contacts-groups.png",
        "alt": "Harbor & Hearth Customer Groups screen showing group membership guidance and the Add group action in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "contact-store-credit",
      "url": "https://platform.getcentri.com/centripos/contact-store-credit",
      "title": "Review and manage Store Credit Balances",
      "summary": "Reconcile the business’s positive customer store-credit liability, inspect each customer’s ledger, and make documented authorized adjustments.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Store credit",
      "introduction": "Open Contacts → Store credit with the Badge Dollar Sign icon. The index includes only customers whose stored store_credit_balance is greater than zero and sorts them from highest balance to lowest. Total liability is the sum of those positive balances for the active tenant; zero and negative records do not appear. Add, Refund, and Reduce change a financial liability immediately, so verify customer identity, amount, reason, and register context first.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Store credit. The Harbor & Hearth screen heading is Store Credit Balances. Confirm the active business before using the customer count or total as a liability figure. Location and register selectors in the shell do not filter this tenant-wide customer balance query.",
        "Read the summary. Customers with credit counts customer records with a balance greater than zero. Total liability adds those positive store-credit balances. If any listed customers also have a positive customer-account balance, the header separately shows their combined open account balance; that A/R amount is not netted against store credit.",
        "Use Search customers to match the loaded positive-balance rows by customer name, company name, local contact code, imported contact code, email, or phone. Search does not query address even though address is displayed in the result row. Clear Search before concluding a customer has no store credit.",
        "Read the row carefully. Customer shows name, optional different company, and imported code when available otherwise local contact code. Contact shows phone, email, and formatted address. Account is that customer’s stored account balance. Store Credit Balance is the positive liability represented by this index.",
        "Choose the customer name or Manage to open the Store Credit dialog. Confirm code, phone, email, and address in the identity strip before changing money. Choose View sales to open Receipts filtered to that customer when a receipt or return should support the balance explanation.",
        "Read Store credit balance, then review up to the 50 newest transaction rows. Each row shows Issued, Redeemed, Refund, Adjusted, or Expired; signed amount; balance after; note; date and time; and Closure when a register session ID was recorded. The ledger is ordered newest first.",
        "Interpret ledger signs. Positive Issue and Refund entries add liability. Redeem normally removes credit when used as payment. Reduce creates a negative Adjustment. Expired removes credit through its originating expiration workflow. Use the row’s balance-after value to trace the running result rather than relying only on the label color.",
        "Choose Closure on a transaction to open Register Closures for its recorded session. A missing Closure link means no register session ID was stored for that transaction; it does not mean the transaction is invalid or that no user performed it.",
        "Choose Add only for an authorized issuance or correction that should increase available store credit. Enter a positive Amount and required Notes explaining the business reason, receipt, approval, or correction reference.",
        "Choose Refund only when value is being returned to store credit through this manual action. Enter a positive Amount and required Notes. This action labels the ledger row Refund, but it does not itself reverse a processor transaction or amend the source receipt; complete the proper return/refund workflow when sale history must change.",
        "Choose Reduce only for an authorized liability reduction. It is disabled when the displayed balance is zero and the amount input is capped at the current displayed balance. Enter a required reason. Do not use Reduce to conceal an unexplained ledger discrepancy.",
        "Choose Confirm once. The adjustment calls the store-credit balance transaction with the selected customer, signed amount delta, transaction type, required notes, current active register session ID when one exists, and no sale ID. Wait for success, then the dialog refreshes the balance and transaction history.",
        "Understand register scope. Manual adjustments can record the current active register session and therefore appear in its Closure evidence, but the customer’s store-credit balance remains a tenant-level customer liability. Opening this page under another register does not create a separate balance for that register.",
        "Close the dialog and confirm the index count, row balance, and Total Liability changed by the same signed amount. Reopen the customer and match the new ledger row, note, balance after, timestamp, and Closure link when applicable.",
        "For a sale redemption, sale refund, expiration, or other automated change, use that originating supported workflow rather than recreating it with a manual label. Then return here to reconcile the positive balance and ledger.",
        "If a customer balance is zero after a full redemption or reduction, the customer disappears from this index because the query requires greater than zero. If Search shows No matching customers, clear it. No customers with store credit is the exact rendered empty state when the positive-balance source has no rows, as shown in the real Harbor & Hearth screenshot.",
        "For audit or accounting questions, compare this screen with Store Credit reporting, the customer ledger, representative receipts, closure evidence, and configured QuickBooks liability mappings. The table’s Total Liability is an operational sum of current positive customer balances, not by itself a complete general-ledger reconciliation."
      ],
      "controls": [
        {
          "name": "Badge Dollar Sign icon",
          "description": "The exact CentriPOS navigation icon for Contacts → Store credit."
        },
        {
          "name": "Customers with credit",
          "description": "Count of customer records whose store_credit_balance is strictly greater than zero."
        },
        {
          "name": "Total liability",
          "description": "Sum of all positive store-credit balances returned for the active tenant."
        },
        {
          "name": "Open account balance",
          "description": "Separate sum of positive customer-account balances only among the currently listed store-credit customers; it is not netted."
        },
        {
          "name": "Search customers",
          "description": "Client-side match on name, company, local/imported code, email, or phone; address is not searchable here."
        },
        {
          "name": "Customer",
          "description": "Name, optional company, and imported code preferred over local contact code."
        },
        {
          "name": "Contact",
          "description": "Phone, email, and formatted address when stored."
        },
        {
          "name": "Account",
          "description": "Stored customer account balance, distinct from store credit."
        },
        {
          "name": "Store Credit Balance",
          "description": "Current positive customer store-credit liability."
        },
        {
          "name": "Manage / customer name",
          "description": "Opens the customer-specific store-credit ledger and manual controls."
        },
        {
          "name": "View sales",
          "description": "Opens Receipts filtered to the selected customer."
        },
        {
          "name": "Transaction history",
          "description": "Up to 50 newest store-credit ledger rows."
        },
        {
          "name": "Issued",
          "description": "Positive liability created through issuance."
        },
        {
          "name": "Redeemed",
          "description": "Store credit consumed by a supported payment workflow."
        },
        {
          "name": "Refund",
          "description": "Positive store credit added with refund semantics."
        },
        {
          "name": "Adjusted",
          "description": "Manual adjustment; Reduce records a negative adjustment."
        },
        {
          "name": "Expired",
          "description": "Credit removed through an expiration workflow."
        },
        {
          "name": "Balance after",
          "description": "Stored customer balance immediately after that transaction."
        },
        {
          "name": "Closure",
          "description": "Opens the recorded register session when register_session_id exists."
        },
        {
          "name": "Add",
          "description": "Manual positive Issue requiring amount and notes."
        },
        {
          "name": "Refund action",
          "description": "Manual positive Refund requiring amount and notes; it does not independently reverse a sale or processor payment."
        },
        {
          "name": "Reduce",
          "description": "Manual negative Adjustment requiring amount and notes and limited to the displayed balance."
        },
        {
          "name": "Required Notes",
          "description": "Audit reason passed into the store-credit transaction."
        },
        {
          "name": "Active session context",
          "description": "Current register session ID recorded on a manual adjustment when one exists."
        },
        {
          "name": "Tenant liability scope",
          "description": "Balance is customer/tenant level even when an adjustment records a register session."
        },
        {
          "name": "No matching customers",
          "description": "Search excluded every loaded positive-balance row."
        },
        {
          "name": "No customers with store credit",
          "description": "No customer has a positive stored balance in the tenant query."
        },
        {
          "name": "Real screenshot",
          "description": "Harbor & Hearth fully rendered zero-customer, $0.00-liability empty state for this exact route."
        },
        {
          "name": "Accounting boundary",
          "description": "Operational positive-balance sum that still requires ledger, receipt, closure, report, and GL reconciliation."
        }
      ],
      "expectedResult": "The tenant-wide count and positive-balance Total Liability reconcile to the listed customers; the selected customer’s current balance reconciles to its newest-first ledger, receipts, and closure evidence; any manual Add, Refund, or Reduce has the intended signed amount, required note, and active-session context; and store credit remains distinct from customer-account debt and general-ledger reconciliation.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/contacts-store-credit.png",
        "alt": "Harbor & Hearth Store Credit Balances screen showing total liability, customer search, and the fully rendered empty state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "merge-duplicates",
      "url": "https://platform.getcentri.com/centripos/merge-duplicates",
      "title": "Review and merge duplicate customers",
      "summary": "Use the owner/admin duplicate scanner or an exact two-contact selection to distinguish true duplicate identities from related people, then consolidate supported records into one irreversible master profile.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "A shared email or phone creates a review candidate; it does not prove two records are the same person or organization. Merge deletes the secondary customer record and retires that customer code. Use Household for related people, Ignore for intentionally separate records, and cancel when accounting, CRM, vault-token, or legal identity is unclear. There is no Files field or Files tab in the current customer profile, and the merge flow does not claim to consolidate arbitrary uploaded files.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Go to Contacts → Contacts. The potential-duplicate banner appears only for an owner or administrator when pending candidates exist. CentriPOS runs a background scan on the first authorized load; Rescan requests another scan. The current scanner groups active customers by normalized primary email and by normalized primary or additional phone numbers.",
        "Open the banner. The count is all pending candidates, while the working queue loads at most the 500 most recently updated pending rows. Summary buttons show up to four shared-email or shared-phone groups, their contact count, and pair-review count. Choose one group to narrow the queue, or Show all queued pairs.",
        "Use Search duplicate matches by name, email, phone, address to narrow the loaded queue. Each pair displays Customer A and Customer B with available name, email, phone, address, match type, and shared-match detail. Compare customer codes and open the underlying Contacts or Customer Profiles separately when the card lacks enough evidence.",
        "Choose Ask CentriAI for a review of up to the first 12 currently filtered pairs. CentriAI receives the shown IDs, names, codes, emails, phones, companies, addresses, match reason, and queue summary. Treat its response as a prioritization aid—not authorization or proof—and verify every proposed action yourself.",
        "Choose Ignore when the two records are intentionally separate despite sharing contact information. Ignore resolves this candidate pair so it leaves the pending queue; it does not merge, edit, associate, or delete either customer. A later scanner implementation or newly generated candidate can still require review.",
        "Choose Household when the pair represents two related people who should remain separate. CentriPOS creates a household named from the two customer names, links both customer IDs as members, and resolves this candidate as household. Review and rename the association afterward; this shortcut does not copy address, roles, billing configuration, or notes into the new household.",
        "Choose Merge only when both records are the same identity. You can also check exactly two rows in the Contacts list and choose the bulk Merge action. More or fewer than two selected contacts cannot enter the comparison.",
        "In Merge Customers, review the automatically suggested master. The suggestion scores profile completeness—usable name, email, phone, additional phone lines, company, address, nonzero balance, and nonzero store credit—and penalizes Dialpad-generated source identities. This is only a default; choose the record whose customer code and external identity should actually survive.",
        "Choose the master profile. Its customer ID and customer code survive, and choosing it resets every field-selection row to that record. The secondary customer will be deleted and its code retired. Review any distinct CentriCRM, Dialpad, QuickBooks, financing, or payment-vault identity before proceeding because the dialog does not present every external identifier.",
        "Choose Contact A or Contact B separately for Name, Email, Phone, Company, Street address, Street address 2, City, State, ZIP code, Tax exempt, and Credit limit. A blank selected text field falls back server-side to an available master or secondary value, so do not assume choosing a visible dash guarantees a blank final value.",
        "Review phone consolidation. CentriPOS combines additional phone-line arrays from both records and inserts the selected primary phone as Primary, then removes duplicate numbers using their normalized last ten digits when possible. The selected primary phone remains the customer_phone field. Verify labels and primary status after the merge.",
        "Review the financial totals. Customer account Balance and Store credit balance are added, including negative values; they are not selectable field rows. This can double a liability if the two records already represent the same underlying amount. Reconcile the A/R invoices and store-credit transaction ledger before and after merging.",
        "Understand the current transactional reassignment. CentriPOS moves the secondary customer’s sales, customer notes, matched CRM external events, customer interactions, A/R invoices, store-credit transactions, parked sales, payment intents, financing applications and preapprovals, gift cards, recurring billing plans, storefront orders, inventory movements carrying customer context, and customer vault-card token rows to the master.",
        "Group memberships are copied to the master without duplicating an existing same-group link, then removed from the secondary. Household/company association memberships are changed to the master ID and merged name. If an existing relationship or another database constraint conflicts, the database merge fails as one transaction rather than intentionally completing a partial merge; read the error and leave both records unchanged for investigation.",
        "The merge changes matched CRM event ownership to the master, marks nondismissed rows Matched with high confidence and customer_merge reason, and updates interaction/preapproval identity snapshots from the merged fields. It does not prove that an external CentriCRM, Dialpad, QuickBooks, financing, or processor-side contact was independently deduplicated. Review those systems where separate identities existed.",
        "Read the irreversible warning naming the secondary contact and retired code, then choose Merge into [master name] ([customer code]). Do not refresh, close the browser, or repeat the action while Merging… is shown. A successful message names the surviving contact and confirms the secondary was deleted.",
        "After success, search Contacts by both names, both codes, email, and phone. The secondary should no longer be an active contact. Open the survivor and verify selected identity fields, all labeled phone lines, tax status, credit limit, associations, groups, Activity, Notes, Store credit, Account, Payment methods, financing, and representative receipts.",
        "Reconcile financial and operational evidence: Account balance against open A/R rows, Store credit balance against its combined transaction ledger, a representative receipt and parked sale, group and association membership, payment token labels, and any matched CRM/Dialpad activity. The merge result is not verified merely because only one Contact row remains.",
        "If the pair is missing a customer record by the time Merge opens, CentriPOS removes the stale candidate from the working queue as already resolved. If Rescan reports candidates found, that count is scanner output—not a count of confirmed duplicates. When no current screenshot exactly matches the live merge dialog, the help center intentionally omits one rather than displaying a fabricated or unrelated image."
      ],
      "controls": [
        {
          "name": "Potential-duplicate banner",
          "description": "Owner/admin-only Contacts alert shown when pending candidate pairs exist."
        },
        {
          "name": "Background scan",
          "description": "Runs once on the first authorized Contacts load and checks active customers for normalized shared email or phone values."
        },
        {
          "name": "Rescan",
          "description": "Requests the current duplicate scan again and refreshes the pending queue."
        },
        {
          "name": "Pending count",
          "description": "All pending candidate rows; the visible working queue is limited to the 500 most recently updated."
        },
        {
          "name": "Shared email / phone summary",
          "description": "Up to four candidate groups with contact and pair-review counts."
        },
        {
          "name": "Duplicate search",
          "description": "Searches the loaded pair cards by match detail and displayed customer name, email, phone, or address."
        },
        {
          "name": "Ask CentriAI",
          "description": "Advisory review of up to 12 currently filtered candidate pairs; human identity verification remains required."
        },
        {
          "name": "Ignore",
          "description": "Resolves only the candidate pair as intentionally separate."
        },
        {
          "name": "Household",
          "description": "Creates a minimal household association with both customer IDs and resolves the candidate; profiles stay separate."
        },
        {
          "name": "Merge",
          "description": "Loads both full customer records into the irreversible comparison."
        },
        {
          "name": "Bulk Merge",
          "description": "Contacts action available only when exactly two rows are selected."
        },
        {
          "name": "Suggested master",
          "description": "Completeness-based default with a penalty for Dialpad-generated identities; it is not authoritative."
        },
        {
          "name": "Master profile",
          "description": "Surviving customer ID and customer code. Changing it resets all field choices to that contact."
        },
        {
          "name": "Secondary contact",
          "description": "Deleted customer record whose customer code is retired after a successful merge."
        },
        {
          "name": "Field-by-field selection",
          "description": "Chooses A or B for Name, Email, Phone, Company, address fields, Tax exempt, and Credit limit."
        },
        {
          "name": "Blank-field fallback",
          "description": "A selected empty text value can fall back to the available master or secondary value in the database function."
        },
        {
          "name": "Phone-line consolidation",
          "description": "Combines both line arrays plus the selected primary phone and deduplicates normalized numbers."
        },
        {
          "name": "Balance",
          "description": "Exact sum of both stored customer account balances; verify against open A/R records."
        },
        {
          "name": "Store credit",
          "description": "Exact sum of both stored store-credit balances; verify against the combined liability ledger."
        },
        {
          "name": "Reassigned sales and operations",
          "description": "Sales, parked sales, storefront orders, payment intents, gift cards, recurring billing, financing, and customer-linked inventory movements move to the master."
        },
        {
          "name": "Reassigned customer context",
          "description": "Notes, interactions, A/R invoices, store-credit transactions, financing preapprovals, and matched CRM events move to the master."
        },
        {
          "name": "Payment methods",
          "description": "Customer vault-card token rows move to the master; full card credentials are not displayed or merged in the dialog."
        },
        {
          "name": "Groups",
          "description": "Secondary memberships are copied to the master without duplicate same-group links, then removed from the secondary."
        },
        {
          "name": "Associations",
          "description": "Household/company member links are repointed to the master and use the merged name."
        },
        {
          "name": "CRM event update",
          "description": "Repoints matched events and sets nondismissed rows to matched with customer_merge evidence; external-system deduplication is not guaranteed."
        },
        {
          "name": "Transactional boundary",
          "description": "A database error aborts the merge instead of intentionally retaining a partially completed reassignment."
        },
        {
          "name": "Merge into…",
          "description": "Irreversible confirmation naming the master and surviving code."
        },
        {
          "name": "Post-merge verification",
          "description": "Identity, phone lines, balances, ledgers, receipts, notes, activity, tokens, groups, associations, financing, and external identities must reconcile."
        },
        {
          "name": "No exact screenshot",
          "description": "The article omits a merge image until an exact safe Harbor & Hearth capture exists."
        }
      ],
      "expectedResult": "The verified master customer is the only remaining active contact; selected identity fields and deduplicated phone lines are correct; account and store-credit sums reconcile to their transferred A/R and ledger records; representative sales, notes, interactions, CRM events, groups, associations, tokens, financing, and other supported customer-linked rows point to the master; the secondary code is retired; and any distinct external CRM, accounting, financing, or processor identity has been reviewed separately.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "saved-cards",
      "url": "https://platform.getcentri.com/centripos/saved-cards",
      "title": "Use saved customer payment methods securely",
      "summary": "Review, collect, prioritize, remove, and use processor-tokenized customer payment references without storing full card credentials in CentriPOS.",
      "collection": {
        "id": "contacts",
        "title": "Contacts & accounts"
      },
      "section": "Contacts",
      "introduction": "Open the intended customer’s Payment methods tab. It can combine NMI Gateway vault cards, CentriPay Online card or ACH tokens, and Payanywhere terminal tokens. The row identifies a reusable token; it is not proof of current authorization, available funds, ownership, or successful future payment. Never put a full card number, bank account, CVV, PIN, password, or processor credential in customer notes or support screenshots.",
      "beforeYouBegin": "Search by more than one identity field before creating a record. Keep customer and payment information out of screenshots and free-form notes unless it is required.",
      "steps": [
        "Open the exact Customer Profile and choose Payment methods. Confirm the customer name and at least one independent identity field before reviewing or charging any saved method. A merge can reassign token rows to the surviving customer, so re-verify identity after duplicate cleanup.",
        "Read the Payment Methods source label. NMI Gateway Vault is a gateway vault card. CentriPay Online Card Token and CentriPay Online ACH Token come from supported online checkout. Payanywhere Terminal Token comes from an eligible in-person terminal save. One customer can have tokens from more than one connected provider.",
        "Identify a row by safe evidence: card brand or generic Card, last four digits when returned, expiration month/year when returned, provider label, and saved origin. “Card details pending” means the token row lacks last-four display data; do not guess which physical card it represents.",
        "Read origin text for CentriPay Online and Payanywhere tokens. It can show the source sale number and saved date, online-checkout date, or terminal-save date. NMI Gateway rows do not currently show equivalent origin text in this panel. Origin is audit context, not cardholder authentication.",
        "Understand connection states. With no active CentriPay payment connection and no saved rows, the panel says No CentriPay payment connection is active and offers Open CentriPay Hub. With connected providers but no customer tokens, it identifies NMI Gateway, Payanywhere, and/or CentriPay Online as active and explains what will appear after a method is saved.",
        "Choose Open CentriPay Hub or Review CentriPay setup only to inspect provider configuration. A visible saved token can outlive a current connection state; do not interpret a row by itself as proof that the provider is ready to process a new payment.",
        "Use Add Card only when it appears. This button is tied specifically to an NMI Gateway tokenization key; it does not manually create a Payanywhere or CentriPay Online token. The embedded Collect.js fields are supplied from secure.nmi.com for Card Number, Expiration, and CVV, then return a one-time token to the NMI vault workflow.",
        "Ask the customer for permission before collecting a new card. Enter Card Number, Expiration, and CVV only in the embedded provider fields and choose Save Card once. CentriPOS sends the returned token with the selected customer ID; it should not receive or display the full card credentials. Cancel closes the form without intentionally saving a method.",
        "Wait for Card saved to vault and reopen Payment methods. Verify brand, last four, expiration, NMI Gateway Vault label, and the correct customer. If tokenization or vault creation fails, read the error and retry only after correcting the provider or card-entry issue; never paste credentials into another field.",
        "Choose Make primary on the intended nonprimary row to set its is_default state. The filled star marks the current primary token. Primary is a CentriPOS preference for supported payment selection; it does not charge the method, move funds, make it valid, or override a workflow’s provider compatibility.",
        "At checkout or another authorized payment workflow, select the exact customer and supported saved payment method. Compare provider, brand/type, last four, expiration, amount, sale, and customer authorization before submitting. Follow every gateway, terminal, ACH, verification, or decline prompt; a saved token does not bypass processor controls.",
        "Do not assume every token works in every channel. NMI Gateway, CentriPay Online, and Payanywhere tokens have different providers and token types. The payment screen must explicitly offer the row for that transaction; otherwise use the supported provider path instead of copying or transforming the token.",
        "To remove a method, choose its trash icon and read Remove saved card?. The dialog names the provider and last four. For an NMI row, CentriPOS requests removal from the NMI Gateway vault. For a Payanywhere row, it removes the local reusable terminal token through the Cloud token workflow. Other non-NMI token rows use the gateway deletion workflow and should be verified after removal.",
        "Choose Remove only when the customer or authorized business process requires the token to stop being available. Removing a token does not void, refund, reverse, or erase prior payments, receipts, processor transactions, chargebacks, or accounting records. It also does not prove the underlying physical card or bank account was closed.",
        "After removal, wait for success and refresh the profile. Confirm the exact row is absent and that another intended primary token is marked when applicable. If removal fails, leave the row in place, capture only safe provider/last-four/error context, and resolve the provider connection; do not repeatedly submit destructive requests.",
        "After any save, primary change, customer merge, or removal, test only through an authorized controlled payment or the provider’s supported verification path. Confirm the resulting receipt and processor transaction reference without exposing full payment credentials.",
        "No exact safe Harbor & Hearth Payment methods screenshot is currently assigned to this article. The help center intentionally uses no screenshot rather than an invented card, fake last four, another tenant’s payment token, or a mismatched CentriPay screen."
      ],
      "controls": [
        {
          "name": "Payment methods tab",
          "description": "Customer Profile section listing safe reusable payment-token references."
        },
        {
          "name": "NMI Gateway Vault",
          "description": "NMI customer-vault token created through gateway tokenization."
        },
        {
          "name": "CentriPay Online Card Token",
          "description": "Saved online-checkout card token from the North/CentriPay Online provider."
        },
        {
          "name": "CentriPay Online ACH Token",
          "description": "Saved online-checkout bank token; it is not a card."
        },
        {
          "name": "Payanywhere Terminal Token",
          "description": "Reusable local reference captured from a supported in-person terminal payment."
        },
        {
          "name": "Brand / Card",
          "description": "Safe card-type label returned with the token."
        },
        {
          "name": "Last four",
          "description": "Safe identifying digits when returned; insufficient by itself to establish ownership."
        },
        {
          "name": "Card details pending",
          "description": "No usable last-four display value is stored on the token row."
        },
        {
          "name": "Expiration",
          "description": "Month and year shown only when returned with the saved method."
        },
        {
          "name": "Saved origin",
          "description": "Available sale/date or provider/date context for Payanywhere and CentriPay Online tokens."
        },
        {
          "name": "Provider-active badge",
          "description": "Indicates a configured active connection, not a successful future charge."
        },
        {
          "name": "Open CentriPay Hub",
          "description": "Opens payment-provider setup when no connection is active."
        },
        {
          "name": "Review CentriPay setup",
          "description": "Opens configuration when an additional or missing provider needs review."
        },
        {
          "name": "Add Card",
          "description": "Shown only when an NMI tokenization key exists."
        },
        {
          "name": "Collect.js fields",
          "description": "NMI-hosted embedded Card Number, Expiration, and CVV inputs that return a token."
        },
        {
          "name": "Save Card",
          "description": "Submits the NMI token for vault creation against the current customer."
        },
        {
          "name": "Make primary",
          "description": "Sets the selected token as CentriPOS’s preferred saved method."
        },
        {
          "name": "Primary star",
          "description": "Marks the row whose is_default state is true."
        },
        {
          "name": "Payment compatibility",
          "description": "A token is usable only where the active payment workflow supports its provider and token type."
        },
        {
          "name": "Trash",
          "description": "Opens provider-aware removal confirmation for the exact token row."
        },
        {
          "name": "Remove NMI card",
          "description": "Requests deletion from the NMI Gateway vault."
        },
        {
          "name": "Remove Payanywhere token",
          "description": "Removes the local reusable terminal token through the Cloud workflow."
        },
        {
          "name": "Remove other token",
          "description": "Uses the configured gateway deletion workflow; verify the row disappears and provider state is consistent."
        },
        {
          "name": "Removal boundary",
          "description": "Does not refund, void, reverse, delete receipts, or erase processor/accounting history."
        },
        {
          "name": "No active connection",
          "description": "Empty state when no supported provider connection and no saved token rows exist."
        },
        {
          "name": "No saved methods",
          "description": "Connected provider state with no customer token rows yet."
        },
        {
          "name": "Security boundary",
          "description": "Full card/bank credentials and CVV belong only in secure provider fields, never CentriPOS notes, screenshots, or support messages."
        },
        {
          "name": "No exact screenshot",
          "description": "The article remains text-only until a safe screen-matched Harbor & Hearth capture exists."
        }
      ],
      "expectedResult": "The token row belongs to the verified customer and shows only safe provider, type/brand, last-four, expiration, origin, and primary state; NMI collection occurs only in provider-hosted fields; an authorized controlled payment uses a compatible provider path; removal deletes only the intended reusable token without implying a refund or history deletion; and no protected credential appears in CentriPOS notes, screenshots, or support content.",
      "troubleshooting": [
        "Search by more than one identity field before creating or merging a customer.",
        "Confirm the selected customer, company, or household before changing balances or associations.",
        "Do not place payment credentials or unnecessary private information in notes."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "communications-inbox",
      "url": "https://platform.getcentri.com/centripos/communications-inbox",
      "title": "Use the Communications Inbox",
      "summary": "Review Dialpad calls and SMS, CentriCRM touchpoints, POS notices, and logged store interactions in one contact-centered workbench.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "Inbox is an operational aggregation screen—not yet a provider-neutral shared inbox. It reads the newest 150 Dialpad events, 100 CentriCRM journey events, 80 store interactions, and 80 POS sale-communication notices returned for the active CentriPOS account. Email inboxes are labeled Next via CRM, internal chat is Planned, and assignment, SLA, provider-neutral replies, and CentriAI actions are described on-screen as a future layer.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Open Communications in the primary navigation and choose Inbox beside the MessageSquareText speech-bubble icon. Inside the Communications workspace, the Inbox tab uses the tray-style Inbox icon. The default Open view includes any thread that is unread, open, or marked for review.",
        "Start with the four summary cards. Open work selects unread, open, and review threads. Dialpad selects threads containing Dialpad activity. CRM journey selects threads containing CentriCRM activity. Matched shows the All filter—it does not limit the list to matched records—even though its number counts threads with at least one matched event.",
        "Use the filter chips to choose All, Open, Dialpad, CentriCRM, Interactions, or POS. Source filters include a thread when any event in that thread has the selected source. Search checks the displayed contact name or detail, customer phone, operating-line proof, latest message or call body, latest activity title, and channel. The screen shows at most 80 filtered threads.",
        "Choose Refresh to reload all four connected feeds. Refresh does not bypass each source’s load limit, and it does not activate an unconfigured provider. Use Provider readiness to distinguish Connected Dialpad, the CentriCRM sync layer, email marked Next via CRM, and internal chat marked Planned.",
        "Read each row before acting: source icon and badge, contact, Unread/Open/Review/Matched/Sent state, latest communication type and direction, date and time, source detail or receipt, contact detail, message or call summary, customer phone, operating line, assignment, and unread-event count. A missing call transcript or message body is stated rather than inferred.",
        "Understand the grouping. Events are kept separate by source, normalized customer phone or contact name, business-side operating line, and channel. Items inside a thread are chronological. Pinned threads sort first, then unread threads, then newest activity. Because source and channel are part of the grouping key, one customer can correctly have several rows.",
        "Open a matched row or choose Activity to open that customer’s profile directly on the Activity tab. Opening an unread matched thread submits a read-state update for its supported imported events. If the row is not matched, choose Contact to search by the best available customer ID, phone, detail, or name; clicking the row itself explains that a contact link is required.",
        "Choose Call only after confirming the displayed customer number and operating-line context. This control opens the device’s tel link; the inbox does not choose a CentriPhone or Dialpad sender for you. Confirm the resulting provider activity before treating the call as logged.",
        "Use the eye control to toggle the entire thread read or unread. The update is written only to Dialpad or CentriCRM items backed by crm_external_events. Logged interactions and POS notices can appear in the thread but do not receive that imported-event state. The list refreshes after a successful update; an error toast means the state was not fully saved.",
        "To begin outreach, choose Start communication, enter a name, phone, or email, and choose SMS, Call, or Email. Find contact opens Contacts with that search. The chosen channel does not send, call, or preselect a provider—the contact profile owns the final sender, schedule, notes, and activity thread.",
        "Choose Log interaction to record an in-store interaction. Use Attribution intelligence for conversion analysis, Log a store interaction for a new operational record, or Dialpad mapping to manage the external provider mapping. These Work queues are links to specialist screens, not inbox filters.",
        "Verify the result in the system that owns it. A real call, SMS, email, customer activity, or saved interaction should appear once against the intended customer and operating line. A rendered row, Connected badge, or selected channel alone is not proof that communication occurred."
      ],
      "controls": [
        {
          "name": "Primary navigation icon",
          "description": "MessageSquareText—the speech bubble with text lines used by the actual Communications and Inbox entry in the main CentriPOS navigation."
        },
        {
          "name": "Workspace tab icon",
          "description": "Inbox—the tray-style icon used for Inbox inside the Communications workspace."
        },
        {
          "name": "Open work",
          "description": "Threads that are unread or whose latest item is Open or Review."
        },
        {
          "name": "Matched summary card",
          "description": "Displays the count of threads containing matched activity, but selecting it switches to All threads."
        },
        {
          "name": "Thread grouping",
          "description": "Source + normalized customer phone or contact name + operating line + channel. Different sources, lines, or channels remain separate rows."
        },
        {
          "name": "Unread",
          "description": "Inbound Dialpad and CentriCRM events default to unread unless their stored communication_state says otherwise."
        },
        {
          "name": "Pinned ordering",
          "description": "Pinned threads appear first, followed by unread threads, then newest activity. No pin control is exposed on this screen."
        },
        {
          "name": "Matched",
          "description": "An imported event, interaction, or notice is tied to a supported CentriPOS customer or activity record."
        },
        {
          "name": "Review",
          "description": "A CentriCRM journey event is new and still needs review."
        },
        {
          "name": "Line",
          "description": "The provider business-side number or other proof showing which operating identity handled the activity."
        },
        {
          "name": "Activity",
          "description": "Opens the matched customer profile directly on its Activity tab and marks supported unread imported events read."
        },
        {
          "name": "Contact",
          "description": "Opens Contacts using the customer ID or best available search value so an unmatched row can be resolved."
        },
        {
          "name": "Call",
          "description": "Opens a tel link for the displayed customer number; it does not select or prove a business sender."
        },
        {
          "name": "Eye control",
          "description": "Toggles read/unread state across supported Dialpad and CentriCRM records in the selected thread."
        },
        {
          "name": "Start communication",
          "description": "Finds a contact using the entered value. Channel selection is informational at this step and nothing is sent."
        },
        {
          "name": "Refresh",
          "description": "Refetches the four capped source feeds for the active tenant."
        },
        {
          "name": "Provider readiness",
          "description": "Describes current integration status and roadmap state. Connected Dialpad does not imply email inbox or internal-chat availability."
        },
        {
          "name": "Privacy-safe screenshot status",
          "description": "The Harbor & Hearth /interactions/inbox capture is intentionally rejected because it is a sensitive customer-message surface. No unrelated or invented screenshot is substituted."
        }
      ],
      "expectedResult": "The selected conversation belongs to the intended customer and operating line, new inbound and outbound activity appears once in chronological order, and unread or assignment state updates correctly.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "interaction-log",
      "url": "https://platform.getcentri.com/centripos/interaction-log",
      "title": "Log a customer interaction",
      "summary": "Capture a standalone customer touch or eligible receipt/saved-quote follow-up with the correct associate, timing, channel, outcome, identity, attribution, visit history, related receipts, and safe next-step context.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "Communications → Log Interaction uses the Clipboard List icon; the form heading uses Message Square Plus. Standalone /interactions/log displays Post-Interaction Form. A saleId opens Receipt Follow-Up Form only for an eligible open/saved sale; closed completed, account, completed-layaway, voided, refunded, cancelled, and return/exchange-group records are locked from new sale-interaction logging. The real Amelia Grant Harbor & Hearth screenshot is an untouched standalone form with only the signed-in associate and assigned location visible—no customer selected and nothing submitted.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Go to Communications → Log Interaction using the Clipboard List icon. Confirm the heading says Post-Interaction Form and the signed-in associate badge is correct before entering anything. Use this standalone mode for walk-ins, calls, messages, and online touches that are not already represented by a receipt/saved-sale follow-up.",
        "Choose Location from assigned locations. The form begins with the active register location when available; a receipt-linked form can prefer the receipt location unless you deliberately changed it. No assigned locations found means the current user has no selectable location evidence.",
        "Choose Worked with now. It defaults to the effective signed-in profile and can be changed to another listed team member. This field attributes the interaction; it does not switch the logged-in user or transfer ownership of an existing sale.",
        "For a standalone interaction, set When with the date plus hour, minute, and AM/PM. Editing timing enables Right now; choose it only to reset both date and time to the current moment. For receipt-linked mode, the timestamp is derived from completed, parked, or created receipt timing and is displayed read-only.",
        "Under What happened?, choose the exact enabled interaction-type tile configured for the tenant, such as Store visit, Phone call, SMS, Email, or Online. These values are configuration-backed; use the label actually displayed rather than forcing a convenient channel.",
        "For standalone/open context, choose What was the result?: Bought today, Saved quote / follow-up, or Left without buying. Do not choose Bought today unless the purchase completed during this touch. A saved receipt is forced to saved quote/follow-up so it does not count as a walk-away.",
        "Understand receipt-linked eligibility. A completed/closed receipt is locked for a new sale interaction and directs later work to service, claims, product questions, or customer notes. A saved/open sale can collect the eligible interaction. Return/refund/exchange child receipts must not receive a separate interaction when the initial receipt owns the group.",
        "When a permitted saleId is present, verify Receipt number, customer snapshot or No customer attached, total, status, short linked sale ID, and Submitted/Not submitted. View receipt opens sale history; do not use a similar receipt number without confirming the tenant and sale ID.",
        "In Related receipts / quotes, choose an attribution role: Alternate quote, Comparison quote, Related saved sale, Converted sale, Follow-up quote, or Primary quote. Search receipt # with at least two characters, or review Suggested same interaction receipts and Historical possible matches.",
        "Treat suggestions as candidates, not proof. Compare number, amount, status, customer, location, timing, and the displayed reason. Link as <role> only when the records truly belong to the same customer touch or quote chain. A candidate already carrying an interaction may link the current receipt to that existing interaction.",
        "Review Current receipt, pending-link, and linked-receipt badges. Expand Linked receipts / quotes to inspect existing and pending relationships. Remove a pending badge with X before saving if it is wrong. An already saved link requires the supported follow-up correction path; this form exposes no unlink action for it.",
        "Under Who was it?, choose No contact for a genuinely anonymous quick walk-in; Existing customer to link a known POS record; or New customer to create and attach one. Do not create a duplicate customer merely to satisfy attribution.",
        "For Existing customer, enter at least two characters and search by name, phone, email, or company. Resolve the exact result and choose it. The selected card shows the best available email, phone, company, or Existing customer label and X clears the selection.",
        "For New customer, enter required Customer name plus optional Email and Phone. Phone formatting follows the tenant country context. This is a real contact creation, not a temporary interaction-only label; search first and do not enter fake data.",
        "Channel contact requirements are enforced. Phone call and SMS require a linked/created customer with a phone number; Email requires a linked/created customer with an email address. Those channels automatically move No contact to an identity mode and block save until the required destination exists. Store visit/other noncontact channels do not require one.",
        "Under How did they find out about us?, choose an enabled customer source or Not captured. The searchable list shows enabled sources only. This attribution is optional and does not overwrite evidence that should come from an external campaign/integration without verification.",
        "Choose Main shopping reason from the configured searchable option list. The form stores its human-readable label on the interaction. Use the customer’s primary stated need, not a product category chosen merely for reporting convenience.",
        "If the result is Left without buying, select at least one reason in If they left without purchasing, why? Multiple configured reasons are allowed and are joined into the saved no-purchase reason. Save is blocked until one is selected.",
        "Choose Earlier contact for this purchase? from the configured visit options. When it is not First visit, Previously worked with appears; choose the correct associate or Not captured. This supports handoff attribution without changing the current Worked with now value.",
        "Read Sale journey as an automatic classification derived from receipt status, saved-sale history, selected outcome, prior-visit choice, and whether a customer is known. It can resolve to saved-sale conversion, open follow-up, return-visit sale, first-visit sale, or existing-customer repurchase. It is not directly editable.",
        "Select Needs follow-up only when another touch is actually expected. Enter Date, Time, and Follow-up note. These values are appended into interaction notes/metadata, including a calculated due timestamp when Date is present; this form does not itself create or prove a scheduled automation, assigned task, notification, email, SMS, or call.",
        "Use Staff notes for products discussed, objections, handoff information, or context another authorized associate needs. Keep notes factual and minimal; never include card data, credentials, health information, or unrelated sensitive details.",
        "Before saving, confirm Location, Worked with now, When, type, result, identity/contact requirement, source, shopping reason, walk-away reasons, prior contact/associate, derived journey, related receipts, follow-up, and notes. Save interaction is disabled while required conditions fail or a write is pending.",
        "Choose Save interaction once. A New customer is created first, the interaction is created second, its metadata/context is attached next, and pending receipt links are written afterward. Those writes are not one all-or-nothing operation; an error can leave the customer or interaction already saved. Search the activity/customer/receipt before retrying.",
        "Wait for Interaction logged or Saved quote interaction logged. The form then clears to the current location, current time, configured defaults, No contact, no links/follow-up/notes, and the effective current associate. Verify one new activity row with the intended customer and receipt relationships before starting another.",
        "Use Clear only when you intend to discard the current unsaved form and reset it. The page tracks dirty state for its container, but Clear performs the reset directly; review any pending receipt links and new-customer details before choosing it."
      ],
      "controls": [
        {
          "name": "Clipboard List icon",
          "description": "Exact Communications navigation icon for Log Interaction."
        },
        {
          "name": "Message Square Plus icon",
          "description": "Icon displayed beside Post-Interaction Form or Receipt Follow-Up Form."
        },
        {
          "name": "Post-Interaction Form",
          "description": "Standalone capture without a saleId."
        },
        {
          "name": "Receipt Follow-Up Form",
          "description": "Sale-linked mode for an eligible open/saved sale."
        },
        {
          "name": "Locked sale",
          "description": "Closed completed, account, completed-layaway, voided, refunded, cancelled, or return/exchange-group record that cannot receive a new sale interaction here."
        },
        {
          "name": "Location",
          "description": "Assigned operational location; may initialize from active register or receipt context."
        },
        {
          "name": "Worked with now",
          "description": "Associate attributed to the current customer touch."
        },
        {
          "name": "When",
          "description": "Standalone editable date and 12-hour time; receipt-linked timing is derived/read-only."
        },
        {
          "name": "Right now",
          "description": "Resets a manually changed standalone timestamp to the current date/time."
        },
        {
          "name": "What happened?",
          "description": "Configuration-backed interaction channel/type tiles."
        },
        {
          "name": "Bought today",
          "description": "Completed during this touch; receipt completion can force the purchase result in supported context."
        },
        {
          "name": "Saved quote / follow-up",
          "description": "Live opportunity with a continuing path; saved receipts are classified here."
        },
        {
          "name": "Left without buying",
          "description": "No completed purchase or clear saved path; requires at least one no-purchase reason."
        },
        {
          "name": "No contact",
          "description": "Anonymous interaction with no customer record, available only when the channel does not require contact data."
        },
        {
          "name": "Existing customer",
          "description": "Search by name, phone, email, or company after at least two characters and attach one exact customer ID."
        },
        {
          "name": "New customer",
          "description": "Creates a real customer before the interaction; Customer name is required."
        },
        {
          "name": "Phone/SMS requirement",
          "description": "Linked or new customer with a phone number."
        },
        {
          "name": "Email requirement",
          "description": "Linked or new customer with an email address."
        },
        {
          "name": "Customer source",
          "description": "Enabled source attribution or Not captured."
        },
        {
          "name": "Main shopping reason",
          "description": "Configured primary buying-reason label."
        },
        {
          "name": "No-purchase reasons",
          "description": "One or more required configured reasons when the customer left without buying."
        },
        {
          "name": "Earlier contact",
          "description": "Configured prior-visit choice controlling whether Previously worked with appears."
        },
        {
          "name": "Previously worked with",
          "description": "Prior associate or Not captured; separate from Worked with now."
        },
        {
          "name": "Sale journey",
          "description": "Read-only derived deal-path classification for reporting."
        },
        {
          "name": "Needs follow-up",
          "description": "Stores date/time/note context; does not itself prove task scheduling or notification."
        },
        {
          "name": "Staff notes",
          "description": "Private operational context subject to data minimization."
        },
        {
          "name": "Receipt status card",
          "description": "Number, customer snapshot, total, status, sale ID, View receipt, and Submitted state."
        },
        {
          "name": "Receipt link role",
          "description": "Alternate quote, Comparison quote, Related saved sale, Converted sale, Follow-up quote, or Primary quote."
        },
        {
          "name": "Suggested same interaction receipts",
          "description": "Higher-confidence candidates requiring human confirmation."
        },
        {
          "name": "Historical possible matches",
          "description": "Lower-confidence prior-submission candidates requiring human confirmation."
        },
        {
          "name": "Receipt search",
          "description": "At least two characters of receipt number and tenant/customer/location context."
        },
        {
          "name": "Pending link",
          "description": "Held in the current form until interaction save; removable with X."
        },
        {
          "name": "Saved link",
          "description": "Written immediately when an active interaction exists; no unlink control in this form."
        },
        {
          "name": "Save interaction",
          "description": "Sequential customer → interaction → context → receipt-link writes; inspect for partial success after an error."
        },
        {
          "name": "Clear",
          "description": "Resets the unsaved form to current/default state."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of the pristine standalone form showing only signed-in staff and assigned location, with no customer or submission data."
        }
      ],
      "expectedResult": "One intended interaction exists with the correct tenant/location, current and prior associate, timestamp, channel/contact requirement, outcome, customer or anonymous choice, source, shopping/no-purchase reasons, derived journey, receipt/quote links, follow-up metadata, and safe notes; any customer or link created before a later failure is detected rather than duplicated.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/interactions-log.png",
        "alt": "Harbor & Hearth Post-Interaction Form showing location, associate, time, interaction type, result, customer choice, source, and shopping reason in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "communications-intelligence",
      "url": "https://platform.getcentri.com/centripos/communications-intelligence",
      "title": "Use Communications Intelligence",
      "summary": "Analyze sale-linked interactions, imported form history, source quality, saved-quote conversion, and CRM-to-receipt matching with evidence behind every number.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "This screen is labeled Interactions Center inside the workspace. It analyzes logged interaction and sale-attribution records; it is not a response-time, live-inbox, or agent-workload dashboard. There is no generic Save or Export action: filters update the analysis in place, Refresh reloads its feeds, and Log Interaction opens a separate capture workflow.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Open Communications in the primary navigation, then choose Intelligence beside the Activity pulse-line icon. The Interactions Center heading repeats that same Activity icon. If reporting migrations are unavailable, the screen shows an explicit reporting-not-available message instead of trustworthy metrics.",
        "Set Range to Last 30 days, Last 90 days, Last 12 months, All history, or Custom range. Custom range exposes From and To dates. Then choose one Location, Register, and Associate with the searchable pickers, or leave each on All.",
        "Use Submission history to understand the loaded evidence. The dashboard requests as many as 5,000 interaction activity records through paged responses beyond Supabase’s 1,000-row response window. The box distinguishes imported rows currently in view from total activity records loaded; it is not a promise that the account has no older records beyond the request cap.",
        "Read the four metrics together. Tracked interactions splits the filtered activity into bought, saved, and left. Close rate is purchased interactions divided by all filtered interactions. Sale-linked revenue uses compatible receipt-attribution rows under the filters. Quote save rate measures saved quote/card/follow-up opportunities among filtered interactions.",
        "Use Intelligence workbench for coaching, saved-sale conversion, source leakage, and demand signals. These are synthesized from the current filter set. Treat low-volume rankings cautiously because some insight rules require minimum interaction volume before identifying a person or location.",
        "In Ask Centri interactions, type a question or choose a prompt such as source leakage, coaching, saved-quote follow-up, or interaction summary. The answer and Evidence list are recalculated from compact source, associate, quote, receipt-link, and CRM-match buckets. Ask Centri limited / Local proof means deterministic evidence mode; Ask Centri active / Gemini-ready means the plan is entitled for the governed AI path, not that every displayed conclusion is autonomous.",
        "Review Customer Journey / Activity. The feed requests up to 30 recent CRM journey rows for the selected date range and shows the first six cards. Matched activity counts rows with at least one receipt candidate. Open a card to inspect the source touchpoint, contact details, preferred receipt candidate, confidence and match reasons, and other candidates.",
        "Treat receipt confidence as a suggestion. Choose View receipt to inspect the proposed sale, or Log interaction to create the supported link. If a card lacks a source URL, opening it may silently attempt one customer-activity refresh using phone, email, or external contact ID. Refresh from CRM imports or enriches up to 50 matching activities; Open in CRM appears only when a source URL exists.",
        "Use Conversion story to compare first and return visits, purchases, no-purchases, and quote/card saves. Use Data coverage to separate imported form history from receipt-linked interactions. An imported record without a receipt link may be matched later, but it is not proven attributed revenue yet.",
        "Compare Sources, Associates, Left without buying, and Locations. Sources normalize imported history into the vocabulary managed in Settings. Associates hides inactive users unless All users is switched on; the signed-in effective profile is still retained where required. Lost-sale reasons combine historical values with current managed options.",
        "Read Hour and day heat as interaction volume by local day and hour. Desktop shows the 24-hour grid; mobile shows up to eight busiest nonzero slots as a percentage of the peak. It does not independently prove revenue, staffing need, or conversion quality.",
        "Owners and super-admins see Interaction Submissions. Its count reflects every matching filtered activity row, while the rendered review list is limited to the first 50. Open submitted card to inspect the record. Other compact activity lists farther down the screen may show only their first 20 rows.",
        "Choose Refresh to refetch conversion reporting, activity, and CRM journey intelligence. Choose Log Interaction to create a new operational interaction. After any new link or log, verify the submitted card, customer activity, and receipt independently before treating the attributed revenue as settled."
      ],
      "controls": [
        {
          "name": "Navigation and heading icon",
          "description": "Activity—the pulse-line icon used by the actual Intelligence entry and Interactions Center heading."
        },
        {
          "name": "Range",
          "description": "The interaction period: 30 days, 90 days, 12 months, all history, or explicit From and To dates."
        },
        {
          "name": "Location / Register / Associate",
          "description": "Searchable single-selection operational filters applied to logged interactions and compatible receipt-attribution rows."
        },
        {
          "name": "Activity load boundary",
          "description": "Up to 5,000 interaction activity records are requested through paging; the CRM journey request is capped at 30 rows for the selected date range."
        },
        {
          "name": "Tracked interactions",
          "description": "Filtered interaction count, split into bought, saved, and left outcomes."
        },
        {
          "name": "Close rate",
          "description": "Purchased interactions divided by all filtered interactions."
        },
        {
          "name": "Sale-linked revenue",
          "description": "Revenue from compatible conversion rows linked through the supported interaction/receipt chain."
        },
        {
          "name": "Quote save rate",
          "description": "Share of interactions that created a saved quote, card, or follow-up opportunity."
        },
        {
          "name": "Submission history",
          "description": "Imported records in the current view plus the activity records loaded through paged database responses."
        },
        {
          "name": "Ask Centri evidence",
          "description": "A compact proof packet made from source, associate, saved-quote, receipt-link, and CRM-match buckets under the active filters."
        },
        {
          "name": "Local proof",
          "description": "Deterministic evidence mode for a plan without the Ask Centri entitlement."
        },
        {
          "name": "Receipt confidence",
          "description": "A ranked candidate based on the available customer, timing, location, associate, status, and receipt evidence. A person should verify it."
        },
        {
          "name": "Matched activity",
          "description": "CRM journey rows with one or more receipt candidates—not rows whose match has necessarily been approved."
        },
        {
          "name": "Refresh from CRM",
          "description": "Attempts to import or enrich up to 50 customer activities using the current contact and receipt context."
        },
        {
          "name": "Data coverage",
          "description": "Separates imported history from receipt-linked records so unattributed activity is not presented as proven revenue."
        },
        {
          "name": "Hour and day heat",
          "description": "Interaction volume by local day and hour, not revenue or staffing demand by itself."
        },
        {
          "name": "Interaction Submissions",
          "description": "Owner/super-admin review of matching submitted interactions; count is complete for the filtered loaded set, list renders the first 50."
        },
        {
          "name": "Privacy-safe screenshot status",
          "description": "The Harbor & Hearth /interactions/overview route redirected to /intelligence/interactions and did not produce a verified screen match, so no invented or route-mismatched screenshot is used."
        }
      ],
      "expectedResult": "The communication metrics and drill-down records reconcile with the selected date, location, channel, line, user, direction, and outcome filters.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "service-ops",
      "url": "https://platform.getcentri.com/centripos/service-ops",
      "title": "Manage service jobs, visits, work and billing links",
      "summary": "Find the correct job, review its customer and linked estimate, schedule visits, record work and complete the job without duplicating billing.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Service",
      "introduction": "Service → Jobs brings the job’s customer, estimate/invoice, visits, work, follow-up and payment links together. Job rows open a detailed workspace with search and workflow filters. Customer pricing, internal job progress and payment evidence remain separate.",
      "beforeYouBegin": "Confirm the active business, service location, customer and authorization for scheduling, work records and billing. Use only the controls shown for the job’s current state and your business’s enabled service workflow.",
      "steps": [
        "Open Service → Jobs. Use Search jobs and All active jobs, Open · Unscheduled, Scheduled, Multi-visit, Pre-sale, Warranty, Follow-up or All to find the original record. A no-match result is different from no jobs existing.",
        "Review the job number, summary, customer, status, next visit, multi-visit completion count, owner and follow-up. Open the exact row. On a phone, use Back to jobs to return to the list.",
        "For new work, choose New job. The current primary action opens the estimate workflow in Money → Take payment with the job return context. Attach the correct customer, verify location and scope, then follow the offered estimate/acceptance steps. Do not assume that opening a job or saving an estimate collects money.",
        "If a job-creation dialog is opened from a request or another supported entry point, choose or create the customer, confirm the business location and describe what the customer needs. Review address, schedule, assignee, follow-up and More options. Link an existing invoice only by its verified invoice/receipt reference; Non-billable call must be deliberate.",
        "Open the job’s customer and details sections to verify contact, service address, concern, requested resolution, linked requests, warranty context and any CRM opportunity. Use the provided linked-request controls to inspect the request that led to this job.",
        "Use Review & send estimate or Build estimate only when offered. Review the saved document and delivery recipient before sending, and refresh acceptance when needed. A sent estimate and an accepted estimate are different states. Do not create another estimate merely because acceptance has not refreshed.",
        "Use Schedule job, Schedule a visit or Add another visit for an agreed appointment. Enter Start, Expected finish, Technician and Dispatch note. Verify the resulting visit list and next visit. A multi-visit job stays distinct from its individual completed visits.",
        "Use Start job or the permitted Next status controls only for the real work state. Scheduled is unavailable without a scheduled date. Complete job is a durable lifecycle change; follow the technician completion/signature flow and verify the result rather than using status to imply a payment.",
        "Under Job items, add the intended part, service, bundle or custom item when authorized. Track internal allocation/progress such as picked, installed or backordered. Editing job items does not rewrite a saved estimate or approved customer price; changes to approved work/pricing require the separate customer-approval workflow.",
        "In Work, use the job clock or Time entries to record actual work. Log manual minutes and notes accurately; where correction/removal controls are offered, use them only on eligible entries and verify the resulting total. Estimate-based time records do not set customer pricing.",
        "Use Add note for factual work performed, materials or follow-up. In Job costs, record an authorized purchase, PO-item usage or internal labor cost. Check source item, available quantity, amount and date; these costs are internal evidence, not an instruction to charge the customer again.",
        "Use the enabled visit, charge, warranty, project and service-plan tools only for the appropriate job. Where approved service charges can be posted to a receipt, review the amount and due date first: posting creates the linked receipt/invoice and does not itself charge a saved method.",
        "Use Open invoice & payment or the related sale link to inspect the authoritative financial record. Job completion can activate an on-completion payment path, while unresolved, declined or missing payment evidence must be investigated on the original invoice/payment.",
        "After each significant action, reopen the job and confirm customer, visits, status, estimate/invoice link, work evidence and current balance. If any result is uncertain, inspect the existing record before retrying creation, sending, posting or collection."
      ],
      "controls": [
        {
          "name": "Search jobs / queue filter",
          "description": "Finds jobs across active, unscheduled, scheduled, multi-visit, pre-sale, warranty, follow-up or all views."
        },
        {
          "name": "Job detail",
          "description": "Opens customer, scope, visits, linked requests, job items, execution and financial links."
        },
        {
          "name": "New job",
          "description": "Primary entry opens the service estimate workflow in Money → Take payment."
        },
        {
          "name": "Schedule job / Add another visit",
          "description": "Creates a verified appointment window and technician assignment."
        },
        {
          "name": "Review & send estimate / Refresh acceptance",
          "description": "Uses the saved estimate and its actual acceptance state."
        },
        {
          "name": "Job items",
          "description": "Tracks parts/services/work progress without silently changing approved billing."
        },
        {
          "name": "Work / Time entries / Add note",
          "description": "Records execution evidence; eligible manual-time correction depends on job state and ownership."
        },
        {
          "name": "Job costs",
          "description": "Internal purchases, PO usage and labor-cost evidence, separate from customer prices."
        },
        {
          "name": "Complete job / Next status",
          "description": "Lifecycle transition; does not itself prove tender or settlement."
        },
        {
          "name": "Open invoice & payment",
          "description": "Authoritative linked financial record for balance and collection."
        }
      ],
      "expectedResult": "The original job accurately links its customer, approved scope, visit schedule, work and financial record, with completion and payment verified separately and no duplicate job, estimate or charge.",
      "troubleshooting": [
        "If the expected job is missing, select All, clear search and check the original job/request reference before creating another.",
        "If a scheduling or status action is unavailable, inspect the job’s current state, required date/technician and enabled workflow.",
        "If job items or work data fail to load, use the offered retry and preserve the original job; do not replace it to bypass the error.",
        "If customer pricing must change after acceptance, use the approved change-order path and customer authorization instead of relying on internal job-item edits."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "communications-settings",
      "url": "https://platform.getcentri.com/centripos/communications-settings",
      "title": "Configure Interaction Settings and Receipt Prompts",
      "summary": "Control where sale-linked interaction suggestions appear, run a bounded CentriCRM synchronization, maintain customer-source attribution, and understand the current limits of shopping/no-purchase option management.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "Communications → Settings uses the Settings icon and is distinct from Admin → Communications telephony/messaging configuration. The top Save persists only receipt-prompt enablement and location/register exclusions. Sync now runs immediately. Embedded Customer Sources and reason managers use separate writes. Current shopping-reason create/edit is defective because the save handler references undefined sortOrder before mutation; do not promise those edits until product code is corrected and retested.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Go to Communications → Settings, identified by the Settings icon. Confirm the Interaction settings heading and intended business; this page manages interaction-study prompts/options, not phone-number ownership, call routing, inboxes, recording, or SMS compliance.",
        "Understand the four save boundaries before editing: Show receipt interaction suggestion plus location/register switches are drafts saved by the top Save; Sync now is an immediate server action; Customer Sources create/edit/order/deactivate independently; shopping/no-purchase option actions write independently when functional.",
        "Show receipt interaction suggestion defaults on when no stored setting exists. Turning it off globally suppresses the configured receipt suggestion regardless of location/register lists, but the change remains local until Save.",
        "Receipt suggestions are eligibility helpers, not automatic interaction submissions. The completed-sale dialog can offer one-tap Log interaction for completed, parked, saved, on-account/bill-to-account, layaway completed, and limited layaway states when the sale has an ID and an interaction callback.",
        "The same helper also influences receipt badges and Dashboard → Interaction reports to finish. Disabling a prompt changes visibility/queue inclusion, not existing interaction records, primary_interaction_id, receipt data, or report history.",
        "Under Locations and registers, only active locations are displayed, with all registers attached to those locations. Search matches a location name or any register name; when only the register matches, the parent location remains visible with matching registers. Search is display-only.",
        "Turn a location off to suppress receipt suggestions for every receipt at that location. Its register switches become disabled and display off, while their individual disabled IDs remain in the draft; re-enabling the location restores the prior per-register state.",
        "Turn an individual register off only when the parent location is enabled. Prompt resolution checks global enabled first, then disabled location ID, then disabled register ID. A receipt without a location/register ID cannot be excluded by that missing scope and follows the remaining settings.",
        "Inactive locations are hidden from this editor but are still part of the loaded known-location set used when Save filters IDs. Save removes stored IDs that no longer correspond to any known location/register, then writes the full enabled and disabled-ID lists through the receipt-prompt settings operation.",
        "Choose the top Save once and wait for Interaction receipt suggestions updated. It invalidates settings, receipt print context, and prompt caches. Reopen the page and confirm the global, location, and register state before testing a receipt.",
        "Test with representative receipt states at an enabled location/register and each excluded scope. Confirm the completed-sale receipt prompt, Sales History interaction badge/action, and Dashboard Interaction reports to finish. A hidden suggestion does not prevent staff from opening the Post-Interaction Form directly.",
        "Under CentriCRM sync, read the direction carefully: link POS customers; post receipt history as CRM notes; mirror editable customer notes; import CRM notes back into POS; and keep receipt-created notes outbound-only. This is data synchronization, not merely a status check.",
        "Sync now immediately invokes sync_pos_to_crm with caps of 100 customers, 25 receipts, 50 outbound customer notes, and 50 inbound notes. It also requests delete_missing_crm_notes true, allowing local imported CRM notes missing from the CRM result to be deleted. Confirm integration ownership, data retention, and backups before running it.",
        "Choose Sync now once and wait. The result reports linked contacts, posted receipt notes, posted customer notes, imported CRM notes, and a count needing review. “Finished” can include per-record errors; inspect the detailed integration/activity evidence rather than treating the toast as complete reconciliation.",
        "Do not click Sync now repeatedly while pending. A bounded run may not cover every customer/receipt/note in a large tenant; use approved operational tooling/support to continue or diagnose rather than assuming one click is exhaustive.",
        "After sync, verify sample POS customer ↔ CRM contact linkage, receipt-note direction, editable customer-note mirroring, inbound CRM-note import/deletion behavior, attribution, timestamps, and duplicates. Never expose CRM tokens or private note content in screenshots/support messages.",
        "The embedded Customer Sources section is the same attribution system documented under Admin → Contact sources: names, descriptions, enabled state, ordering, deactivation, and Post-Interaction picker behavior use separate database writes and are not saved by the top Save.",
        "Review Customer Sources before changing them. Disabled sources remain historical but disappear from supported new-selection pickers; reordering/editing has known sort-order caveats. Verify the Post-Interaction Customer source picker after each independent change.",
        "Main shopping reasons populate the Main shopping reason field. Left without purchasing reasons populate the reason field for no-purchase outcomes. Rows can display Name, Description, Enabled/Disabled, Default, order, Pencil, and Trash/deactivate controls.",
        "Current defect: New/Edit reason handleSave passes an undefined sortOrder variable. The resulting ReferenceError is caught and shown as Failed to save <reason>; no create/update mutation is sent. Do not keep retrying, claim success, or work around it with duplicate entries. Escalate the product defect and retest after code repair.",
        "Existing reason rows can still be reordered by drag when they have database IDs. Drag end writes manual order values beginning at 10,000 in 10-point increments; failures restore the prior local order and show Failed to save display order. Verify the actual form order.",
        "Trash on an existing shopping/no-purchase reason does not hard-delete. It immediately sets is_enabled false and shows deactivated; there is no confirmation. Historical references remain, but the option is removed from enabled form choices.",
        "The reason dialog’s Default behavior is intended to clear other defaults in the same group before saving the selected one. Because create/edit currently fails before mutation, do not assume a newly selected Default persisted. Existing stored defaults remain as loaded.",
        "If the page shows No active locations found, No locations/registers match, no sources, or no options, treat each as a scoped completed empty state after loading. Do not infer tenant-wide absence from a search-filtered result.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully loaded /interactions/settings page at 1440×900 with visible location/register prompt configuration only. No switch, Save, CRM sync, source, option, or reorder action was invoked; no customer, receipt, CRM note, token, or private content is exposed."
      ],
      "controls": [
        {
          "name": "Settings icon",
          "description": "Exact Communications navigation icon for Interaction settings."
        },
        {
          "name": "Top Save",
          "description": "Persists only receipt-prompt global/location/register settings."
        },
        {
          "name": "Show receipt interaction suggestion",
          "description": "Global draft gate; defaults on when absent."
        },
        {
          "name": "Disabled location IDs",
          "description": "Suppress prompts for every register/receipt at that location."
        },
        {
          "name": "Disabled register IDs",
          "description": "Suppress prompts for one register when its location is enabled."
        },
        {
          "name": "Prompt resolution",
          "description": "Global enabled → location exclusion → register exclusion."
        },
        {
          "name": "Eligible receipt dialog",
          "description": "Supported completed/saved/account/layaway receipt states with sale-linked interaction action."
        },
        {
          "name": "Sales History badge",
          "description": "Uses prompt settings but existing submitted interactions remain visible."
        },
        {
          "name": "Interaction reports to finish",
          "description": "Dashboard queue filtered by prompt scope and missing primary interaction."
        },
        {
          "name": "Search locations or registers",
          "description": "Display-only parent/register matching."
        },
        {
          "name": "Inactive location boundary",
          "description": "Hidden in UI; Save still validates IDs against all loaded known records."
        },
        {
          "name": "Sync now",
          "description": "Immediate bounded CentriCRM sync, separate from top Save."
        },
        {
          "name": "Sync caps",
          "description": "100 customers, 25 receipts, 50 outbound notes, 50 inbound notes."
        },
        {
          "name": "delete_missing_crm_notes",
          "description": "Manual sync requests deletion of imported local CRM notes no longer returned from CRM."
        },
        {
          "name": "Outbound-only receipt notes",
          "description": "Receipt-created CRM notes are not imported back into POS."
        },
        {
          "name": "Customer Sources",
          "description": "Embedded independent attribution manager; not part of top Save."
        },
        {
          "name": "Main shopping reasons",
          "description": "Options for the interaction form’s primary buying reason."
        },
        {
          "name": "No-purchase reasons",
          "description": "Options used when the customer leaves without buying."
        },
        {
          "name": "Current reason-save defect",
          "description": "Undefined sortOrder causes create/edit to fail before database mutation."
        },
        {
          "name": "Drag reorder",
          "description": "Existing database rows saved at manual sort values beginning 10,000."
        },
        {
          "name": "Trash/deactivate",
          "description": "Immediate is_enabled=false, not hard delete."
        },
        {
          "name": "Default option",
          "description": "Intended one-per-group behavior; new edits cannot currently persist due defect."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant Interaction settings capture; read-only visible scope with no customer/CRM data or mutations."
        }
      ],
      "expectedResult": "The intended receipt prompts, CentriCRM sync behavior, and per-location or register settings are saved and reflected in one controlled interaction.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/interactions-settings.png",
        "alt": "Harbor & Hearth Interaction settings showing receipt prompts, CentriCRM sync, and per-location and register settings in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "dialpad",
      "url": "https://platform.getcentri.com/centripos/dialpad",
      "title": "Use Dialpad with CentriPOS",
      "summary": "Connect an assigned Dialpad line, opt this browser into calling or incoming-call screen pops, call a customer, send or schedule SMS, and verify the communication in customer activity.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "Dialpad availability is tenant-, location-, user-, and browser-specific. Browser Calling switches are stored only in the current browser and are off until that user opts in. Calls require an assigned Dialpad sender; SMS may also offer an assigned CentriCRM / LC sender. Never assume a connected integration means every user has a callable line, recording, transcript, or permission.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Ask an authorized administrator to open Admin → Integrations → Dialpad and confirm the tenant connection, connected user, company, and assigned numbers. Reconnect only when authorization is genuinely required; do not use OAuth as a status-refresh button.",
        "In the Dialpad integration screen, find Browser Calling. Turn on Dialpad browser dialer to show the embedded Dialpad dock when CTI is configured. Turn on Incoming call screen pop only for the current browser when this workstation should listen for incoming-call events. These choices do not enable another user or browser.",
        "Open the operating-context bar and confirm the intended business, location, register, and signed-in user. Then open the customer from Sell or the supported customer profile surface and verify the customer name and phone number before communicating.",
        "In the customer communication card, choose the recipient number when the customer has more than one. SMS can target multiple selected customer numbers; confirm every checked recipient because each number receives the message. Calling uses the customer’s primary normalized phone.",
        "Open the sender picker and choose an assigned line. Read both the provider and number: Dialpad and CentriCRM / LC senders can appear together. A profile-default or location-default badge helps prioritize a line but does not replace your confirmation. Only assigned numbers are offered.",
        "To call, select a Dialpad sender and choose Call. CentriPOS enables the browser dialer and submits the customer number, selected Dialpad sender, and customer context to the Dialpad dock. Complete and end the call in the embedded Dialpad experience; a CentriCRM / LC sender cannot be used for this call button.",
        "To text now, enter the message, recheck recipients and sender, choose Send now, and submit. Wait for the sent confirmation before retrying. A blank message, missing sender, disconnected provider, or missing recipient keeps Send unavailable.",
        "To send later, choose Schedule and enter a local date/time at least one minute in the future. Review the Scheduled SMS list. Select a scheduled item to edit its text, time, or compatible sender; use its cancel control only when the message should not send. Wait for the updated or cancelled confirmation.",
        "Open customer activity after the interaction. Dialpad calls and SMS can be imported into the timeline and live events can update it. Refresh activity only when needed and wait for completion. Confirm direction, participants, time, status, and message/call identity; recording, transcript, AI recap, and review details appear only when Dialpad actually supplies them.",
        "For an incoming call, keep this browser open with Incoming call screen pop enabled. When Dialpad sends a supported event, CentriPOS shows a call card with matched customer context when available. Verify the caller before opening or creating a customer; do not create a duplicate merely because formatting prevented a match.",
        "If the dock or screen pop does not appear, return to Browser Calling in this same browser and confirm the switch, CTI configured badge, assigned sender, integration connection, and browser/session state. If another workstation works, remember the preferences are local rather than tenant-wide. Escalate with the user, location, browser, time, direction, and affected number—never with OAuth tokens or credentials."
      ],
      "controls": [
        {
          "name": "Connect Dialpad / Reconnect Dialpad",
          "description": "Starts tenant OAuth authorization. Reconnect is a credential action, not a harmless refresh."
        },
        {
          "name": "Connected user, Company, Numbers",
          "description": "Integration status summary; Numbers is the count available through the connection, not proof that every user is assigned a line."
        },
        {
          "name": "Dialpad browser dialer",
          "description": "Browser-local switch that allows the Dialpad dock to render when CTI and sender availability support it."
        },
        {
          "name": "CTI configured / Needs CTI client ID",
          "description": "States whether the embedded calling client has the required client configuration."
        },
        {
          "name": "Incoming call screen pop",
          "description": "Browser-local opt-in that listens for supported Dialpad incoming-call events and displays a CentriPOS call card."
        },
        {
          "name": "Recipient picker",
          "description": "Selects one or more saved customer phone numbers for SMS. Calling continues to use the primary normalized number."
        },
        {
          "name": "Sender picker",
          "description": "Shows only assigned Dialpad or CentriCRM / LC senders, including provider, line kind, number, and supported default badges."
        },
        {
          "name": "Default badge",
          "description": "Marks the profile-preferred sender; location default can be used when no profile default applies. Always confirm the actual provider and number."
        },
        {
          "name": "Call",
          "description": "Available only with a connected assigned Dialpad sender and a valid customer phone; opens/enables the Dialpad dock with customer context."
        },
        {
          "name": "Send now",
          "description": "Submits the message immediately through the selected sender provider to every checked recipient."
        },
        {
          "name": "Schedule",
          "description": "Requires a time at least one minute ahead and creates a scheduled SMS entry."
        },
        {
          "name": "Scheduled SMS",
          "description": "Lists pending or failed scheduled messages with time, provider/line, recipient, body, and an error when present."
        },
        {
          "name": "Edit scheduled SMS",
          "description": "Loads an item back into the composer so its supported message, time, or sender can be updated."
        },
        {
          "name": "Cancel scheduled SMS",
          "description": "Cancels a still-scheduled item; it cannot recall a message already sent."
        },
        {
          "name": "Customer activity",
          "description": "Timeline that can show imported/live Dialpad calls and SMS. Treat status and provider evidence as authoritative."
        },
        {
          "name": "Recording / transcript / AI recap",
          "description": "Conditional call evidence shown only when returned by Dialpad; connection alone does not guarantee any of it."
        },
        {
          "name": "Refresh activity",
          "description": "Requests recent Dialpad import and inbox indexing. Do not repeatedly refresh while a prior request is pending."
        },
        {
          "name": "Screen-pop customer match",
          "description": "Uses incoming caller context to find a customer; verify identity before opening or creating a record."
        },
        {
          "name": "No exact workflow screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains a safe Admin Communications readiness image, but no exact customer Dialpad call/SMS workflow image. This guide intentionally uses no unrelated or invented screenshot."
        }
      ],
      "expectedResult": "The Dialpad action opens or logs against the intended CentriPOS customer and line context, and completed activity appears once without duplicating the contact.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "email-text-receipt",
      "url": "https://platform.getcentri.com/centripos/email-text-receipt",
      "title": "Email or text a receipt and customer link",
      "summary": "Choose between the full receipt-email workflow and the lightweight customer-link dialog, then send the correct branded receipt, fulfillment slip, return review, or eCart checkout path.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "A full receipt email and an Email Link are different actions. Every public URL is a bearer link: anyone who receives it may be able to open the customer-visible content. Confirm the sale, artifact, recipient, and consent before sharing.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "Open the exact completed sale or customer workflow. For a formatted receipt email with template, style, policies, and recipient controls, choose Email receipt. For a public URL by SMS, lightweight email, copy, or QR, choose the receipt/customer-link action.",
        "In Email receipt, enter at least one To address. Multiple To recipients can be separated by commas, semicolons, or new lines; review CC and BCC independently. Confirm Subject and the optional Message before sending.",
        "Choose the required Receipt style: Standard receipt, Gift receipt, or Delivery sheet. Choose Store policies from Storefront, Register, or None, then select the intended active receipt template. The template list can be searched by name, type, or assigned register.",
        "Choose Send receipt once. CentriPOS prepares a public receipt URL when possible and sends the formatted receipt using the selected template and options. Wait for the success message naming the receipt; if the template context is missing or delivery fails, correct that issue before retrying.",
        "For a customer link, read the dialog title before sharing: Receipt Link opens the public receipt and PDF; Fulfillment Slip opens pickup or delivery details, signature capture, and a PDF without payment totals; Send Return Review lets the customer review and acknowledge a return before refund finalization; E-Cart Checkout Link lets the customer complete a live cart whose edits can continue to synchronize.",
        "Confirm the receipt number and the displayed Receipt Total, Cart Total, Paid, Balance, Refund, or Fulfillment slip badge. Opening the link dialog may automatically copy its URL to the browser clipboard, so do not open it while an untrusted clipboard manager, shared remote session, or unrelated paste destination is active.",
        "Choose the external-link control to preview the current customer page. The production destination must remain on pos.getcentri.com; never replace it with a Supabase, storage, Edge Function, or other internal service URL. Copy link only for an approved channel.",
        "Choose Text Link, or Text Checkout for eCart. Confirm the phone number and actively verify that the customer agreed to transactional CentriPOS texts on behalf of the business even if the consent control already appears selected. Review or replace the prepared notice; CentriPOS appends the branded link and STOP opt-out language.",
        "Keep the editable SMS portion within its displayed segment allowance. Choose Send once and wait for Text sent. CentriPOS uses the configured business sender when available; without an eligible sender or enabled fallback, the message does not send and the configuration error must be resolved.",
        "Choose Email Link for a lightweight link email. Confirm the one recipient address and editable message, then choose Send. This path keeps the email button and customer link attached to the system template; it does not expose the full receipt email’s CC, BCC, style, policy, or receipt-template controls.",
        "When no send mode is selected, the dialog can show a QR code for the receipt, fulfillment slip, return review, or eCart. Display or print it only where the intended customer can scan it. Customer Display (Tablet/iPad), when available, reveals a separate pairing QR and persistent display URL for the selected register; do not give that setup URL to a shopper as their transaction link.",
        "Use Refresh link only when the current workflow supplies that control and a replacement URL is actually needed. Re-preview and redistribute the returned URL; do not make assumptions about the prior URL’s lifetime that the screen does not confirm.",
        "After sending, verify the customer received the intended artifact and review communication activity when available. A warning that the message sent but the communication log did not save means delivery may have succeeded even though the activity record failed; investigate the log instead of sending a duplicate."
      ],
      "controls": [
        {
          "name": "Email receipt",
          "description": "Full formatted-receipt workflow with To, CC, BCC, Subject, Message, receipt style, policy source, and receipt-template selection."
        },
        {
          "name": "To",
          "description": "Requires at least one valid recipient; accepts multiple addresses separated by commas, semicolons, or new lines in the full receipt-email workflow."
        },
        {
          "name": "CC / BCC",
          "description": "Additional visible or hidden recipients for a full receipt email; verify each independently."
        },
        {
          "name": "Standard receipt",
          "description": "Normal customer receipt variant using the selected receipt template."
        },
        {
          "name": "Gift receipt",
          "description": "Gift-oriented receipt variant selected for the full email."
        },
        {
          "name": "Delivery sheet",
          "description": "Delivery-oriented receipt variant selected for the full email."
        },
        {
          "name": "Storefront / Register / None policies",
          "description": "Chooses which supported policy source is included with the formatted receipt."
        },
        {
          "name": "Receipt template",
          "description": "Active printable/email layout; search can match its name, type, or assigned register."
        },
        {
          "name": "Send receipt",
          "description": "Sends the full formatted receipt once the sale, tenant, recipient, and template context are ready."
        },
        {
          "name": "Receipt Link",
          "description": "Public customer receipt with item details and access to its receipt PDF."
        },
        {
          "name": "Fulfillment Slip",
          "description": "Customer-facing pickup or delivery detail, signature capture, and a PDF that omits payment totals."
        },
        {
          "name": "Send Return Review",
          "description": "Remote return-review and acknowledgement path used before refund finalization."
        },
        {
          "name": "E-Cart Checkout Link",
          "description": "Live checkout path where the customer can complete the purchase while supported cart changes synchronize."
        },
        {
          "name": "Automatic clipboard copy",
          "description": "The customer-link dialog can copy its URL when it opens; treat the clipboard as customer-sensitive."
        },
        {
          "name": "Receipt / cart / refund badges",
          "description": "Sale-specific identifiers and amounts used to confirm the artifact before sharing."
        },
        {
          "name": "Open link in new tab",
          "description": "Previews the exact current customer page on the branded production host."
        },
        {
          "name": "Text Link / Text Checkout",
          "description": "Opens the SMS destination, editable notice, consent, length, and send controls."
        },
        {
          "name": "Transactional-text consent",
          "description": "Staff confirmation that the customer agreed to receive the transaction message; verify it actively even when preselected."
        },
        {
          "name": "STOP language",
          "description": "System opt-out language appended with the branded link to the final SMS."
        },
        {
          "name": "Email Link",
          "description": "Lightweight one-recipient customer-link email with an editable message; it is not the full Email receipt workflow."
        },
        {
          "name": "Clear / Use template",
          "description": "Removes the editable message or restores the prepared mode-specific wording."
        },
        {
          "name": "QR code",
          "description": "Encodes the current customer transaction link for controlled scanning."
        },
        {
          "name": "Customer Display (Tablet/iPad)",
          "description": "Separate persistent register-display pairing workflow; its setup URL is not a shopper receipt or checkout link."
        },
        {
          "name": "Copy link",
          "description": "Copies the customer-sensitive branded URL for an approved sharing channel."
        },
        {
          "name": "Refresh link",
          "description": "Requests a replacement link only on workflows that expose the control."
        },
        {
          "name": "Communication activity warning",
          "description": "Delivery may have succeeded even when its activity-log write failed; verify before repeating the send."
        },
        {
          "name": "No substituted screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no exact safe capture for this multi-dialog workflow, so this guide intentionally publishes without a mismatched or fabricated image."
        }
      ],
      "expectedResult": "The intended recipient receives exactly one verified branded pos.getcentri.com full receipt or customer link for the correct sale; the chosen receipt variant, template, policies, destination, and consent are correct, no internal service URL is exposed, and delivery is distinguished from communication-log success.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "centrireviews",
      "url": "https://platform.getcentri.com/centripos/centrireviews",
      "title": "Use and configure CentriReviews Pro",
      "summary": "Connect each store to its review-provider location, send consented requests from completed sales, and monitor the provider data mirrored into CentriPOS.",
      "collection": {
        "id": "communications",
        "title": "Communications"
      },
      "section": "Communications",
      "introduction": "CentriReviews Pro is location-specific. A saved connection alone does not make a store ready: its mapping, provider IDs, delivery mode, status, and review link or provider-delivery setting must also be correct.",
      "beforeYouBegin": "Confirm the operating line or sender, the customer match, and the intended recipient before sending or calling.",
      "steps": [
        "If you are an administrator, open Settings → Integrations → CentriReviews Pro. Enter the shared provider API key and Agency and Client API base URLs, save the connection, then use Test & sync theme to verify the provider connection.",
        "Create or edit a mapping for each CentriPOS location. Choose the CentriPOS location and enter the provider business ID and provider location ID; both IDs are required. Add the display name, provider default template ID, HTTPS review link, delivery mode, email subject, contact-sync mode, send delay, dedupe window, automation setting, dry-run setting, and mapping status as needed. Save the mapping.",
        "Treat Default template ID as a reference to a template managed by the connected provider. This screen does not contain a template editor. Use CentriPOS SMS / email when CentriPOS should deliver requests, or CentriReviews provider when the provider should deliver them. Keep a new or changed automation in Dry run until its recipients and routing have been checked.",
        "Open Communications → CentriReviews Pro to use the command center. Select one mapping when you intend to run a sync. The start and end dates are sent to the provider import; they do not filter the already mirrored rows shown in the tables. If All mappings is selected, a sync currently uses the first mapping, not every mapped location. Run each location separately when complete coverage matters.",
        "Use Location review link to choose a mapped location. Only a valid HTTPS link can be copied, opened, or turned into the downloadable QR PNG. A location showing No link must be corrected in integration settings before those controls work.",
        "To request a review from a completed sale or receipt, open Request review. CentriPOS resolves the receipt’s exact location to an active mapping. Confirm the customer gave permission, then choose Text when a phone number is present or Email when an email address is present. A mapped review link is required unless the mapping uses provider delivery.",
        "After sending, verify the latest attempt rather than relying only on the success message. The receipt can show Sent, Opened, and total sends; resending creates another tracked attempt. In the command center, Invites shows the recipient, request type, contact method, status, error, date, and Dry run badge. Pending, sent, suppressed, and failed are distinct outcomes, and a dry run is not a delivered request.",
        "Use Reviews for imported public reviews and provider replies, Private feedback for rescue follow-up, Employees for review and visit snapshots, and Google profile for metric snapshots. Reply opens a simple text prompt and sends the response through the provider. Refresh reloads the mirrored CentriPOS rows; use the matching Sync action when you need to import newer provider data.",
        "Before enabling automation, test one location end to end: correct sale location, customer consent and destination, expected dedupe behavior, successful delivery, tracked open where available, correct public-review destination, and the resulting provider activity. Paused or disabled mappings must not be treated as request-ready."
      ],
      "controls": [
        {
          "name": "Active mapping",
          "description": "The location-specific provider connection CentriPOS may use for review requests."
        },
        {
          "name": "Provider business ID",
          "description": "The connected review provider’s business identifier; required to save a mapping."
        },
        {
          "name": "Provider location ID",
          "description": "The provider identifier paired with the exact CentriPOS location; required to save a mapping."
        },
        {
          "name": "Review link",
          "description": "The HTTPS destination used by copy, open, QR, and CentriPOS-delivered request controls."
        },
        {
          "name": "Default template ID",
          "description": "A provider-side template reference, not an editable CentriPOS template."
        },
        {
          "name": "Delivery mode",
          "description": "Whether CentriPOS communications or the connected review provider sends the request."
        },
        {
          "name": "Contact sync mode",
          "description": "Whether CentriPOS sends only the invite, creates the contact before inviting, or synchronizes contacts."
        },
        {
          "name": "Send delay",
          "description": "The configured wait before an automated request is sent."
        },
        {
          "name": "Dedupe window",
          "description": "The number of days used to avoid repeating an automated request for the same eligible recipient or event."
        },
        {
          "name": "Automation",
          "description": "The mapping setting that allows configured POS activity to create requests without a staff member manually sending each one."
        },
        {
          "name": "Dry run",
          "description": "A test attempt that records what would happen without representing a real delivered request."
        },
        {
          "name": "Invite attempt",
          "description": "A tracked request event with recipient, channel, status, errors, and delivery metadata."
        },
        {
          "name": "Opened",
          "description": "The tracked request link was opened; it does not prove a public review was submitted."
        },
        {
          "name": "Public review",
          "description": "A provider review imported into the Reviews tab, with rating, text, match state, and reply data."
        },
        {
          "name": "Private feedback",
          "description": "A private provider response imported for rescue follow-up rather than publication as a public review."
        },
        {
          "name": "Employee snapshot",
          "description": "Imported provider totals for reviews, visits, and conversion over a reported period."
        },
        {
          "name": "Google profile snapshot",
          "description": "Imported location-profile metrics for a reported period."
        }
      ],
      "expectedResult": "The review request uses the intended location identity and recipient, and delivery and response state appear in the supported reputation workflow.",
      "troubleshooting": [
        "Confirm the operating line, sender identity, customer match, and recipient before sending.",
        "Review the conversation or interaction log before repeating an outbound message.",
        "Check browser microphone and notification permissions when calls or alerts do not work."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-sales",
      "url": "https://platform.getcentri.com/centripos/network-sales",
      "title": "Review Network Sales",
      "summary": "Use the permission-tiered Network Sales workspace to interpret date-scoped KPIs separately from transaction filters, inspect permitted receipts, and avoid relying on currently inactive Search and Export buttons.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Sales",
      "introduction": "Network → Network Sales uses the Receipt icon. This screen has different visibility tiers, and its headline metrics do not use the same filter set as its transaction list. Network KPI cards and charts currently respond only to Date; Store, Customer, receipt/note/product search, and Status filter only the transaction query. The exact Amelia Grant Harbor & Hearth /network/sales capture was rejected because it remained loading and the surface can expose customer and receipt data. No fabricated or mismatched screenshot is published.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Network Sales using the Receipt icon. Confirm the current operating tenant and whether it is an Enterprise HQ, child organization, Agency/Platform context, or proxied storefront before interpreting anything. A child organization queries its parent HQ network identity.",
        "Understand the access tier. A non-agency user can access permitted network transactions. HQ Owners and platform super admins in a non-agency HQ context can also see network KPI cards and charts. Agency/Platform owners see anonymized Platform Metrics and no individual transaction rows; a platform super admin can see the permitted platform metrics and transaction surface.",
        "Do not infer broader access from a hidden card or missing row. Role, tenant type, parent relationship, and server policies determine visibility. Agency users are told that individual transactions are not accessible at platform level and to proxy into a specific store for transaction details.",
        "Set Date first. Presets are Today, 7 days, 30 days, 90 days, and 1 year; the custom picker provides separate From and To calendars plus Clear dates and Apply. With no dates, the query passes no explicit date boundary. Verify the displayed dates and reporting timezone before comparison.",
        "For HQ KPI access, read Total Revenue, Total Sales, Avg Ticket, and Active Stores. These values come from the network-stats query for the HQ identity and current Date only. They do not recalculate for Store, Customer, receipt/note/product, or Status filters below.",
        "Read Payment Types as date-scoped tender amount, or No payment data yet when empty. Read Top Stores by Revenue as the first five returned store rows in its date-scoped chart, or No store data yet. The display formats KPI currency as USD with no cents; reconcile exact amounts from source receipts/reports before financial use.",
        "For Agency/Platform metrics, read the Anonymized badge and the visible Platform Revenue, Platform Sales, Avg Ticket, Active Stores, Total Storefronts, Unique Customers, CentriPay Volume, and CentriPay Txns cards when returned. Payment Methods (Platform-wide), Revenue Trend, and Sales by Status are aggregate-only. The period buttons apply only the date range and clear selected stores.",
        "Treat KPI and transaction evidence as separate scopes. A transaction Store filter can narrow the rows while KPI cards remain unchanged because the KPI request receives only Date. Never claim the filtered rows reconcile to a card unless you independently run a matching report with the same exact scope.",
        "Under Transactions on desktop, choose one or more permitted Stores, one Customer, optional Receipt, note or product text, and Status. Status choices are All statuses, Completed, Returned, Exchanged, Layaway, On Account, Saved, and Voided.",
        "Transaction filters update the URL and refetch as each value changes. The visible desktop Search button currently has no click handler and does not perform a separate submission. Do not tell users they must click it, and do not use the button as evidence a fresh query ran.",
        "On mobile, type in Search receipt, product, customer and open the Sliders Horizontal filter sheet for Date, Customer, Store, and Status. Apply Filters only closes the sheet; the selections already update the query as they change.",
        "Use Clear all filters to restore Status to All and Stores to none while also dropping Customer, search text, and dates from the filter object. Confirm the visible result afterward; clearing filters broadens the request only within the user’s permitted network.",
        "Read Displaying <n> sales on desktop or <n> sales on mobile as the number currently loaded, not necessarily the total matching the server. Results load in pages of 50. Choose Load more until the required result appears; realtime sale changes can invalidate and refresh the query.",
        "On desktop, each row shows Receipt and date/time, Store, Customer, Sold by, Total, Status, optional note, expand chevron, and a return icon. A missing customer, seller, or store displays a dash rather than proving the source record never had that relationship.",
        "Choose a customer name to open the customer profile panel. This exposes customer data and is not a harmless navigation preview; verify the correct network/store customer before editing or communicating.",
        "Choose a row to open Sale Detail. Desktop writes the sale ID into /network/sales/<saleId>, retains current query parameters, and scrolls the row into view. Mobile opens the detail in a bottom sheet without changing to that sale-detail route.",
        "Review the full sale detail before any action: tenant/store, location/register/session, receipt, customer, seller, line items, payments, totals, status, note, fulfillment, returns, integrations, and other evidence available to the role. Network context does not make every receipt action appropriate.",
        "Use the return icon, Process Return, or Edit only when the receipt is eligible and the effective user has authority. These launch the same operational return/edit workflows used by receipt detail; verify tenant, location, register, quantities, payment/refund path, and post-action audit evidence.",
        "Treat No sales found across the network as a result for the current filters and permissions. Clear the likely filter, confirm the network identity/date, and load the appropriate storefront context before reporting missing data.",
        "Do not use Export. The desktop Export button is presently rendered without a click handler, so it does not download the filtered result. Use an approved working report/export surface instead and recheck this guide after the product implements an export action.",
        "Protect customer and financial data. Do not place transaction rows, customer profiles, receipt details, returns, or exported network data in public screenshots. The approved manifest intentionally contains no exact Network Sales image."
      ],
      "controls": [
        {
          "name": "Receipt icon",
          "description": "Exact CentriPOS navigation icon for Network → Network Sales."
        },
        {
          "name": "Network identity",
          "description": "HQ tenant used for stats and permitted transaction search; a child organization resolves through its parent HQ."
        },
        {
          "name": "Permission tier",
          "description": "Controls whether the user sees network KPIs, anonymized platform aggregates, individual transactions, or a combination."
        },
        {
          "name": "Anonymized",
          "description": "Agency/Platform aggregate label; individual transactions remain unavailable to non-super-admin agency users."
        },
        {
          "name": "Date",
          "description": "Only filter shared by the KPI/stat query and transaction query."
        },
        {
          "name": "Today / 7 days / 30 days / 90 days / 1 year",
          "description": "Preset date ranges applied immediately and stored in the URL."
        },
        {
          "name": "Custom From / To",
          "description": "Separate calendar boundaries for the query; verify displayed dates and timezone."
        },
        {
          "name": "Total Revenue",
          "description": "Date-scoped network aggregate formatted as whole-dollar USD in this view."
        },
        {
          "name": "Total Sales",
          "description": "Date-scoped sale count returned by network stats."
        },
        {
          "name": "Avg Ticket",
          "description": "Date-scoped network average formatted as whole-dollar USD."
        },
        {
          "name": "Active Stores",
          "description": "Date-scoped contributing-store count returned by network stats."
        },
        {
          "name": "Payment Types",
          "description": "Date-scoped payment-amount chart; it does not follow transaction-only filters."
        },
        {
          "name": "Top Stores by Revenue",
          "description": "Date-scoped chart showing up to the first five returned store aggregates."
        },
        {
          "name": "Platform Metrics",
          "description": "Agency/Platform aggregate cards for revenue, sales, stores, customers, and CentriPay activity when authorized."
        },
        {
          "name": "Payment Methods (Platform-wide)",
          "description": "Aggregate platform tender amounts without transaction disclosure."
        },
        {
          "name": "Revenue Trend",
          "description": "Date-scoped platform daily revenue bars."
        },
        {
          "name": "Sales by Status",
          "description": "Platform aggregate counts for Completed, Returned, Voided, Layaway, and Account Sales."
        },
        {
          "name": "Store",
          "description": "Multi-store transaction filter only; it does not recalculate KPI cards."
        },
        {
          "name": "Customer",
          "description": "One customer-ID transaction filter and profile-panel entry point."
        },
        {
          "name": "Receipt, note or product",
          "description": "Transaction search sent to the network-sales search routine."
        },
        {
          "name": "Status",
          "description": "All, Completed, Returned, Exchanged, Layaway, On Account, Saved, or Voided transaction filter."
        },
        {
          "name": "Desktop Search button",
          "description": "Currently inert; filters already update and refetch on change."
        },
        {
          "name": "Mobile Apply Filters",
          "description": "Closes the filter sheet; selections already applied while changing."
        },
        {
          "name": "Clear all filters",
          "description": "Resets the transaction and date filter object to All statuses with no stores."
        },
        {
          "name": "Displaying / sales count",
          "description": "Currently loaded rows, not guaranteed full match count."
        },
        {
          "name": "Load more",
          "description": "Fetches the next page of up to 50 permitted sales."
        },
        {
          "name": "Sale row",
          "description": "Receipt/time, store, customer, seller, total, status, note, detail toggle, and return entry point."
        },
        {
          "name": "Desktop sale route",
          "description": "/network/sales/<saleId> with current query parameters preserved."
        },
        {
          "name": "Mobile sale sheet",
          "description": "Bottom-sheet detail without the desktop expanded-sale route."
        },
        {
          "name": "Customer profile",
          "description": "Sensitive customer detail panel opened from the linked name."
        },
        {
          "name": "Process Return / Edit",
          "description": "Permission- and lifecycle-sensitive receipt actions from Sale Detail."
        },
        {
          "name": "Export button",
          "description": "Currently rendered without a download handler; do not rely on it."
        },
        {
          "name": "No exact screenshot",
          "description": "The Amelia Grant Harbor & Hearth /network/sales capture was rejected for an unresolved loading state and sensitive transaction exposure; no invented replacement is used."
        }
      ],
      "expectedResult": "The network totals and storefront rows match the selected organization, date, timezone, locations, channels, and statuses, and drill-down sales explain the aggregate.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-reports",
      "url": "https://platform.getcentri.com/centripos/network-reports",
      "title": "Use Reports from the Network area",
      "summary": "Use the full Sales report workspace from the Network tab while keeping its actual data boundary clear: today it reports only the active CentriPOS tenant, not every related storefront.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Reports",
      "introduction": "Network → Reports uses the Bar Chart 3 icon but mounts the same SalesReportView used by the main Reports area, with its default Sales report title and “Analyze your sales with personal or company-wide report views” subtitle. No network-mode or parent-HQ identifier is passed. Every report, breakdown, receipt drill-down, saved view, column layout, export, print, and email operation uses the current active tenant ID. A parent/child relationship or the Network tab itself does not aggregate child businesses. The exact Harbor & Hearth capture was rejected because multiple report metrics remained loading; no fabricated replacement is published.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Reports using the Bar Chart 3 icon. Confirm the active CentriPOS business in the operating-context bar before interpreting the page. The route location does not change the data tenant.",
        "Read the heading carefully. The component displays Sales report—not Network report—and the same subtitle used by the ordinary Sales Reports workspace. This is the clearest visible indication that the shared report builder is mounted unchanged.",
        "Understand the tenant boundary. The report hooks send the active tenantId to the sales-report RPC. An Enterprise HQ sees that HQ tenant’s own sales rows; a child organization sees its own tenant rows; a proxied context uses the proxied tenant. Related child storefronts are not automatically unioned.",
        "Do not treat a Location filter as a storefront/network selector. Location IDs belong to the active tenant’s report scope. They narrow that tenant’s locations and cannot add another child business.",
        "For an actual cross-business question, use a verified network-aware screen/report or run the same saved configuration separately in each authorized storefront and reconcile the exports with explicit tenant labels. Never sum overlapping or differently scoped totals without confirming definitions.",
        "Choose Report type from Sales summary, Receipt status, User, Location, Register, Customer, Customer group, Product, SKU name, Brand, Supplier, Product category, or Tag. These are the same choices and computations as the main Sales report.",
        "Choose one or more supported Measures. Available values depend on the report type and include revenue variants, counts, averages, discounts, returns, customer attachment, tax, tips, cost/gross profit/margin, first/last sale, items, and supported e-cart measures. Cost-sensitive values remain subject to role visibility.",
        "Set the exact Date preset or custom range and confirm the time boundaries. Choose a comparison only when the selected report and period support it; a comparison is not a second tenant/network scope.",
        "Use Include and Exclude chips for the supported active-tenant dimensions. Location is handled as report location IDs; other chips are passed as include/exclude filter maps. An exclusion can materially change receipt and line visibility, so read every chip before sharing a result.",
        "Use Advanced report controls to arrange period columns, rows, nested rows, selected receipt/detail columns, gift-card inclusion, and required row details as supported. Month breakout is offered when the range spans months. Sort rules affect presentation, not tenant scope.",
        "Switch between Table and Chart only for supported chartable measures. Read selected range, comparison, row groups, time buckets, totals, and empty/unassigned groups together; a chart is a rendering of the same active-tenant result.",
        "Open a total/row receipt drill-down to inspect the underlying permitted sales. It reuses the report’s date, location, include/exclude, time bucket, period, parent group, and group filters and returns only a limited receipt set. Use receipt detail to validate a representative amount without assuming it proves an entire network.",
        "Use Saved Views to store the current report query for this tenant and route. Personal views belong to their creator; Shared view management requires authority. A saved view re-runs against current data and is not a frozen result or cross-store template by itself.",
        "Use saved Column layouts only for the active tenant/profile and compatible report type. A column layout changes selected detail columns, not measures, filters, ownership, or tenant scope.",
        "Use Export CSV only after verifying business, report type, measures, dates, comparison, include/exclude chips, location scope, arrangement, gift-card setting, and data columns. The generated export represents the current report model, not an automatic network consolidation.",
        "Use Print to review orientation, margins, optional chart, business label, selected range, view status, measures, columns, prepared-by identity, table, and totals before the system print dialog.",
        "Use Email only with approved recipients and current tenant data. The workflow sends a branded https://pos.getcentri.com report link and supports immediate or scheduled delivery where configured. Review saved schedules separately; do not send one storefront’s private report as if it were an anonymized network report.",
        "If the report remains loading or errors, do not substitute data from Network Sales, a local report, or an invented screenshot. Preserve the active tenant, route, report type, date range, filters, and safe error state for support.",
        "To compare the shared component itself, open Reports → Sales Reports with the same active tenant and query. The results should match because both routes use the same report implementation; any difference should be investigated as URL/saved-view/context state, not presumed network aggregation."
      ],
      "controls": [
        {
          "name": "Bar Chart 3 icon",
          "description": "Exact Network navigation icon for Reports."
        },
        {
          "name": "Sales report heading",
          "description": "Default heading of the shared SalesReportView mounted at /network/reports."
        },
        {
          "name": "Active tenant boundary",
          "description": "Every report RPC receives the current tenantId; no parent-HQ or network-union argument is supplied."
        },
        {
          "name": "Network tab boundary",
          "description": "Navigation placement only; it does not change the report’s data plane."
        },
        {
          "name": "Location",
          "description": "Active-tenant location IDs only, not child-storefront selection."
        },
        {
          "name": "Report type",
          "description": "Sales summary, Receipt status, User, Location, Register, Customer, Customer group, Product, SKU name, Brand, Supplier, Product category, or Tag."
        },
        {
          "name": "Measures",
          "description": "Report-type-dependent calculations such as revenue, counts, averages, discounts, returns, customer, tax, tips, costs, profit, margin, items, dates, and supported e-cart metrics."
        },
        {
          "name": "Date / comparison",
          "description": "Current and optional comparison periods within the same active tenant."
        },
        {
          "name": "Include / Exclude",
          "description": "Supported active-tenant receipt and line filters; no relationship-based network expansion."
        },
        {
          "name": "Advanced report controls",
          "description": "Period columns, row/nested-row grouping, detail columns, gift-card inclusion, and row-detail requirements."
        },
        {
          "name": "Table / Chart",
          "description": "Two presentations of the same scoped report result."
        },
        {
          "name": "Receipt drill-down",
          "description": "Limited underlying sale set using the current report’s date, location, filter, period, and grouping state."
        },
        {
          "name": "Saved View",
          "description": "Reusable current-tenant report query with Personal/Shared ownership and fresh data."
        },
        {
          "name": "Column layout",
          "description": "Reusable active-tenant/profile detail-column selection for a compatible report type."
        },
        {
          "name": "Export CSV",
          "description": "Working export of the current report model; not a network consolidation."
        },
        {
          "name": "Print",
          "description": "Printable branded report model with reviewed chart, layout, metadata, table, and totals."
        },
        {
          "name": "Email / schedule",
          "description": "Branded report-link delivery for the active tenant; recipients and schedules remain sensitive."
        },
        {
          "name": "Cross-business method",
          "description": "Use a verified network-aware surface or separately labeled per-store reports and reconcile deliberately."
        },
        {
          "name": "No exact screenshot",
          "description": "The Harbor & Hearth /network/reports capture was rejected because revenue, payment, customer-balance, and lead metrics remained loading; no invented image is used."
        }
      ],
      "expectedResult": "The route is correctly treated as the ordinary Sales report for the active tenant—not a network union—and its report type, measures, dates, comparison, active-tenant locations, include/exclude filters, arrangements, receipt drill-down, saved view, export, print, and email evidence reconcile with the equivalent main Reports route.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-inventory",
      "url": "https://platform.getcentri.com/centripos/network-inventory",
      "title": "Review Network Inventory",
      "summary": "Compare the same master products and variants across participating storefronts and locations, inspect stock-on-hand, reorder exceptions, inventory value, and HQ-versus-local retail pricing.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Inventory",
      "introduction": "This screen aggregates recorded stock_on_hand from the network data source. It does not show committed, available-to-promise, incoming, or in-transit quantities, and it does not create a transfer or inventory adjustment. Cost value and retail comparison are hidden when the role has Hide product costs.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Network Inventory, or Inventory → Network Inventory when your network-enabled role exposes that route. The navigation uses the product’s Network Inventory icon and the screen heading says Network Inventory.",
        "Confirm the network context before interpreting the totals. An enterprise, agency, or platform account uses its own network identity; a participating child storefront uses its parent network identity. The data is therefore broader than one active location when access is configured.",
        "Read the summary cards before filtering: Franchisees is the count of participating tenant records represented by products; Products is the number of grouped master products; Network Units is the sum of recorded stock-on-hand; Below Reorder is the count of location-level reorder exceptions; Network Value is stock-on-hand multiplied by the grouped product supply price.",
        "If costs are hidden for the role, Network Value displays dots and the HQ Retail and local retail comparison badges are also omitted. Changing the page URL or expanding a row does not bypass that permission.",
        "Use All, In Stock, Below Reorder, Zero, or Negative. In Stock means the product’s aggregated total is greater than zero; Zero and Negative use the aggregated total. Below Reorder includes a product when at least one represented location has positive stock below its reorder point. A location at exactly zero is not counted by this screen’s below-reorder rule and appears under Zero instead.",
        "Use Search product name or SKU. Search matches the grouped product name or master SKU; it does not search brand, franchise, location, variant name, or variant SKU on this screen. The count at the right shows filtered products out of the full product count.",
        "When more than one participating business appears, open Franchise and select one or more businesses. The product totals, below-reorder count, and value are recalculated from only those selected tenant rows. Choose Clear all inside the filter to return to the full represented network.",
        "Read a collapsed product row. It shows product name, master SKU, brand on wider screens, participating-business count, variant count when applicable, location-level below-reorder count, HQ Retail when allowed, aggregated units, and aggregated cost value when allowed. Discontinued means the HQ/master record has a deprecation date; it does not erase the participating businesses’ stock.",
        "Expand a product without variants to see each participating business. The business row shows its local retail comparison when allowed, number of locations, below-reorder exception count, and total units. Expand the business to see each location’s stock-on-hand and reorder point.",
        "For a product with variants, expand the product, then expand the intended variant. The variant row shows its name, SKU, network units, business count, below-reorder exceptions, and HQ retail when available. Expand a business beneath that variant to reach location stock. Always compare the exact variant rather than relying only on the product total.",
        "Interpret the retail badge only as a price comparison. Green means the business retail matches HQ retail within one cent. Amber shows the local retail above HQ with a positive difference; red shows it below HQ with a negative difference. It is not an inventory-health or profit badge.",
        "Interpret Network Value as an operational cost aggregation, not a financial statement or available-to-sell value. The grouped product value uses total stock multiplied by its captured supply price; tenant filtering prorates that grouped value from the same unit basis. Negative stock can therefore reduce the total.",
        "No products found across the network can mean the search or tab excludes all rows, selected franchisees have no matching product, or the network source returned no products. Clear Search, set All, and clear Franchise filters before treating it as missing network data.",
        "Use Network → Transfers when one storefront needs to request or move stock. Use the appropriate local inventory count or adjustment workflow to correct a location quantity. Network Inventory itself is read-only and does not show movement history, open purchase orders, incoming supply, commitments, or transfer-in-transit quantities.",
        "Before promising inventory to a customer, open the relevant storefront, variant, and location detail in the operational workflow and confirm the current sellable/fulfillment state. A positive Network Units number alone is not an available-to-promise guarantee."
      ],
      "controls": [
        {
          "name": "Franchisees",
          "description": "Distinct participating businesses represented across the loaded network products."
        },
        {
          "name": "Products",
          "description": "Grouped master-product count returned by the network inventory source."
        },
        {
          "name": "Network Units",
          "description": "Sum of recorded stock-on-hand across represented product, business, and location rows."
        },
        {
          "name": "Below Reorder summary",
          "description": "Total number of represented locations with stock greater than zero and below their reorder point."
        },
        {
          "name": "Network Value",
          "description": "Aggregated stock-on-hand multiplied by grouped supply price; hidden when costs are restricted."
        },
        {
          "name": "All",
          "description": "Shows every product remaining after Search and Franchise filters."
        },
        {
          "name": "In Stock",
          "description": "Products whose filtered aggregate stock is greater than zero."
        },
        {
          "name": "Below Reorder tab",
          "description": "Products with at least one positive-stock location below its reorder point."
        },
        {
          "name": "Zero",
          "description": "Products whose filtered aggregate stock equals zero."
        },
        {
          "name": "Negative",
          "description": "Products whose filtered aggregate stock is below zero."
        },
        {
          "name": "Search product name or SKU",
          "description": "Matches only grouped product name or master SKU."
        },
        {
          "name": "Franchise filter",
          "description": "Recalculates rows and totals for one or more selected participating businesses."
        },
        {
          "name": "Filtered count",
          "description": "Number of currently visible products compared with the unfiltered loaded product count."
        },
        {
          "name": "Master product row",
          "description": "Network grouping built from the source product when available, otherwise the local product identity."
        },
        {
          "name": "Discontinued",
          "description": "HQ/master product has been deprecated; stock records can still remain visible."
        },
        {
          "name": "Participating-business badge",
          "description": "Number of tenant rows represented for the product or variant."
        },
        {
          "name": "Variant badge",
          "description": "Number of grouped active or returned variant identities under the master product."
        },
        {
          "name": "HQ Retail",
          "description": "Recommended or captured HQ retail reference shown only when cost/price visibility is permitted."
        },
        {
          "name": "Retail comparison badge",
          "description": "Local business retail versus HQ retail: green match, amber above, red below."
        },
        {
          "name": "Business total",
          "description": "Sum of that business’s represented location stock for the product or variant."
        },
        {
          "name": "Location stock",
          "description": "Recorded stock_on_hand for the exact location."
        },
        {
          "name": "Reorder point",
          "description": "Location threshold shown as reorder ↓ value when configured."
        },
        {
          "name": "Reorder exception",
          "description": "Positive location stock below its reorder point; zero stock is classified separately."
        },
        {
          "name": "No stock data",
          "description": "The grouped product or business has no represented location quantity rows."
        },
        {
          "name": "Read-only screen",
          "description": "No adjustment, commitment, purchasing, movement, or transfer action is performed here."
        },
        {
          "name": "Available-to-promise boundary",
          "description": "Network Units is recorded on-hand aggregation, not proof that units are uncommitted and ready for a new customer."
        }
      ],
      "expectedResult": "The selected master product and exact variant expand through the intended participating business to its location-level stock-on-hand and reorder point; the filtered aggregate, visible cost value, and HQ-versus-local retail comparison reconcile to those represented rows without being mistaken for committed, incoming, or available-to-promise inventory.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-transfers",
      "url": "https://platform.getcentri.com/centripos/network-transfers",
      "title": "Coordinate Network Transfers",
      "summary": "Create and follow the current cross-business request record while independently controlling physical shipment, inventory adjustments, received quantities, and any resulting intercompany charge.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Transfers",
      "introduction": "Network → Network Transfers uses the Arrow Left Right icon. The current screen is a request/status tracker, not a complete inventory-movement workflow: creating, sending, or receiving a network transfer does not change stock-on-hand in this component. The UI moves directly Requested → Sent → Received, does not capture sent or received quantities, and creates a pending at-cost invoice on receipt from the stored quantity_received values. Use separate verified inventory and accounting controls before treating the transfer as reconciled. The exact Harbor & Hearth history capture was rejected because it exposed private businesses, transfer IDs, quantities, dates, statuses, and values.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Network Transfers using the Arrow Left Right icon. Confirm the active business and whether it is the intended source, destination, Enterprise HQ, or Agency context before opening or changing a record.",
        "Use All for every permitted status. Active excludes Received and Cancelled. Completed currently includes Received only—not Cancelled—even though cancelled records still exist in All. Read the count shown only on the active tab as the server total for that filter.",
        "Use Search transfers only for a transfer number. The field waits about 400 milliseconds before querying and does not search source business, destination business, location, product, SKU, requester, note, date, or status.",
        "Results load newest first in pages of 50. Choose Load more (<loaded> of <total>) until the intended transfer is present. No network transfers yet can mean the current filter/search returned none, not that no record exists in another permitted scope.",
        "Choose Request Transfer. Recheck Deliver to (your location) every time. The dialog lists active locations belonging to the current tenant; the selected destination state can persist between dialog openings, so never assume the visible prior choice is still appropriate.",
        "In Search network inventory, enter at least two characters from the grouped master product name or master SKU. Results exclude the current tenant, include only source-location rows with recorded stock greater than zero, and show at most 20 matches.",
        "Read each result’s product name, source business, source location, and displayed <n> in stock. The result does not offer a variant selector and the request stores the master product with variant ID null, even when the network product has variants. Do not use this workflow for a variant-sensitive item unless the exact identity and downstream correction process have been approved.",
        "Choose a result once. The same master product/source business/source location combination cannot be added twice. The line shows product name, master SKU, quantity, and remove X; it does not continue to show the source name or available stock after selection, so resolve each line before adding several similar sources.",
        "Enter a whole requested quantity of at least 1. The input clamps values below 1 but does not cap the request to the displayed stock, reserve inventory, or recheck availability at submission. Independently confirm the exact sellable quantity with the source before sending.",
        "Read Items to request, number of source stores, and Est. cost. Unit cost is calculated from the grouped network product’s total value divided by total stock, not necessarily the selected source location’s actual cost. Treat it as an estimate, not an approved intercompany price or financial document.",
        "Add Notes (optional) with an operational reason and safe handling context. Do not include customer details, payment data, credentials, or other information unnecessary for the source and destination teams.",
        "Choose Submit Request once. CentriPOS groups lines by source tenant plus source location and creates one Requested transfer per group, with pricing model at cost and HQ approval not required. The success message reports how many requests were created.",
        "Submission is not transactional across every group or even across a transfer header and its item rows. A later failure can leave earlier transfer requests—or a header without all intended items—already saved. If an error occurs, close the dialog, search by recent transfer number/time, and inspect every created record before retrying.",
        "Open each transfer card. It shows transfer number, status, From and To business names, item count, total requested units, estimated cost, and creation date. The detail shows From/To locations, each product/master SKU, requested quantity, unit cost each, Total cost basis, Notes, request time, and requester.",
        "For the source business, a Requested record offers Decline and Mark as Sent. There is no approval step or confirmation dialog in this UI; although Approved exists in the status model, this screen does not expose an Approve action. Decline writes Cancelled immediately.",
        "Choose Mark as Sent only after the exact physical items and quantities have left the source and a separate source inventory movement/adjustment has been recorded. The action writes status and shipped-by/time but this dialog captures no shipping note, carrier, tracking, quantity sent, or source stock decrement.",
        "For the destination business, a Sent record offers Mark as Received. Inspect the physical shipment first and record shortage, overage, damage, wrong item/variant, and destination stock through the approved operational workflows before choosing it. There is no confirmation dialog or received-quantity field here.",
        "Mark as Received writes Received plus receiver/time and attempts to create a pending network-transfer invoice. The invoice subtotal is calculated from each item’s stored quantity_received multiplied by unit cost; this screen never sets quantity_received. Do not rely on the generated amount until accounting verifies item quantities, cost basis, invoice existence, subtotal, and both businesses.",
        "Enterprise HQ or Agency context can Cancel another source’s Requested transfer; the source itself sees Decline. Platform is treated as HQ by the data hook but not by this component’s HQ-action flag, so do not assume a platform context exposes Cancel here.",
        "Cancelled records do not appear under Completed in the current query. Find them under All, using their transfer number when known. There is no reopen, edit, delete, print, export, attachment, tracking, or exception-resolution action on this screen.",
        "Reconcile the full path outside this status tracker: source stock before/after and movement ledger; physical shipment evidence; destination count and stock movement; exact product/variant identity; requested versus actually sent/received quantities; pending intercompany invoice and approved cost; and both tenant histories. Received status alone is not proof of inventory or accounting reconciliation."
      ],
      "controls": [
        {
          "name": "Arrow Left Right icon",
          "description": "Exact CentriPOS navigation and page icon for Network Transfers."
        },
        {
          "name": "All",
          "description": "Every permitted transfer status, including Cancelled and Received."
        },
        {
          "name": "Active",
          "description": "Any status except Received or Cancelled."
        },
        {
          "name": "Completed",
          "description": "Received only in the current query; Cancelled is not included."
        },
        {
          "name": "Active-tab count",
          "description": "Exact server count for the selected All, Active, or Completed filter."
        },
        {
          "name": "Search transfers",
          "description": "Debounced transfer-number search only."
        },
        {
          "name": "Load more",
          "description": "Fetches the next page of up to 50 newest-first transfer records."
        },
        {
          "name": "Request Transfer",
          "description": "Opens the destination, network-product search, requested items, estimate, and notes dialog."
        },
        {
          "name": "Deliver to (your location)",
          "description": "Active current-tenant destination location; recheck because dialog state can persist."
        },
        {
          "name": "Search network inventory",
          "description": "Requires two characters; matches master product name/SKU, excludes own-tenant and nonpositive source-location stock, and returns at most 20 rows."
        },
        {
          "name": "Displayed in stock",
          "description": "Recorded source-location stock at search time; not reserved, capped, or revalidated by submission."
        },
        {
          "name": "Variant boundary",
          "description": "No variant picker is exposed and request lines store variant ID null."
        },
        {
          "name": "Requested quantity",
          "description": "Integer-like input clamped to at least 1 but not capped to displayed stock."
        },
        {
          "name": "Duplicate boundary",
          "description": "Same master product/source tenant/source location cannot be added twice in one dialog."
        },
        {
          "name": "Estimated cost",
          "description": "Requested quantity multiplied by grouped product value-per-unit; not proven source-location cost."
        },
        {
          "name": "Notes",
          "description": "Optional request context shared with the transfer record."
        },
        {
          "name": "Submit Request",
          "description": "Creates one transfer per source-tenant/source-location group with Requested status."
        },
        {
          "name": "Partial-create boundary",
          "description": "Grouped transfers and their item inserts occur sequentially without one encompassing transaction."
        },
        {
          "name": "Transfer card",
          "description": "Number, status, From/To businesses, item count, requested units, estimated cost, and date."
        },
        {
          "name": "Transfer detail",
          "description": "From/To locations, items, master SKUs, requested quantities, unit cost, total cost basis, notes, requester, and time."
        },
        {
          "name": "Requested",
          "description": "Destination request exists; no inventory is reserved or moved."
        },
        {
          "name": "Approved",
          "description": "Status supported by the model but no Approve action appears in this screen."
        },
        {
          "name": "Decline",
          "description": "Source-business immediate transition from Requested to Cancelled."
        },
        {
          "name": "Mark as Sent",
          "description": "Source-business immediate status write with shipper/time; no quantity, tracking, or inventory mutation."
        },
        {
          "name": "Mark as Received",
          "description": "Destination-business immediate status write with receiver/time and pending-invoice attempt; no received-quantity or inventory mutation."
        },
        {
          "name": "HQ / Agency Cancel",
          "description": "Can cancel another source’s Requested record from eligible component context."
        },
        {
          "name": "Cancelled",
          "description": "Terminal request status visible under All, not Completed."
        },
        {
          "name": "Received",
          "description": "Terminal tracker status; not proof that stock or accounting reconciled."
        },
        {
          "name": "Pending invoice",
          "description": "Attempted on receipt at unit cost using stored quantity_received, which this UI never captures."
        },
        {
          "name": "No exact screenshot",
          "description": "The Harbor & Hearth /network/transfers capture was rejected because it disclosed private network, identifier, quantity, date, status, and cost information."
        }
      ],
      "expectedResult": "The intended grouped request records exist once with the correct source, destination, master-product identity, requested quantities, and safe notes; status matches the physical handoff; and separate source stock, destination stock, movement-ledger, actually sent/received quantity, cost basis, and pending intercompany invoice evidence are independently reconciled because this screen does not perform those inventory controls.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-master-catalog",
      "url": "https://platform.getcentri.com/centripos/network-master-catalog",
      "title": "Use the Network Master Catalog",
      "summary": "Review the active HQ product book, see which organization products link back to each HQ source, inspect variant pricing, and mark a product discontinued or restore it.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Master Catalog",
      "introduction": "The screen is titled Master Product Book and is available only to enterprise, agency, or platform tenant types. It is not a full product editor or publisher: the current controls search, expand variants, and toggle the HQ deprecation flag.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Master Catalog. If the account is not an HQ-capable tenant, CentriPOS displays that the Master Product Book is available only for franchise HQ accounts.",
        "Read Total, Active, and Discontinued. These counts come from active, non-deleted products owned by the current HQ tenant; Discontinued means deprecated_at is set, not that the product record was deleted.",
        "Search products by HQ product name or SKU. The search does not currently match variant SKU, brand, or organization name.",
        "Read the HQ product name, SKU, brand, retail price, optional Suggested price, variant count, and franchisee count. Organization names appear only where child products link to the HQ product through source_product_id.",
        "Expand a product with variants to review each variant name, SKU, retail price, and optional Suggested price. This view does not edit variant fields.",
        "Choose Discontinue only after reviewing the confirmation’s organization count. Confirming sets the HQ product’s deprecation timestamp and tells linked organizations it is Discontinued by HQ; they can still sell remaining stock.",
        "Choose Restore to clear the HQ deprecation timestamp. Confirm the Discontinued badge disappears and the Active/Discontinued counts update.",
        "Do not interpret a franchisee count of zero as unpublished inventory everywhere; it means this query found no child product linked through source_product_id. Use the actual product publish workflow and a controlled organization check to prove distribution."
      ],
      "controls": [
        {
          "name": "Master Product Book",
          "description": "The current HQ tenant’s active, non-deleted product records plus linked-organization distribution evidence."
        },
        {
          "name": "Active",
          "description": "HQ products without a deprecation timestamp."
        },
        {
          "name": "Discontinued",
          "description": "HQ products with deprecated_at set. They are flagged network-wide but are not deleted and remaining stock can still be sold."
        },
        {
          "name": "Franchisee count",
          "description": "Number of child-tenant product rows linked to the HQ product by source_product_id."
        },
        {
          "name": "Organization names",
          "description": "Names returned for child tenants holding those linked product rows."
        },
        {
          "name": "Suggested price",
          "description": "Recommended retail shown only when present and different from the HQ retail price."
        },
        {
          "name": "Variant drill-down",
          "description": "Read-only variant name, SKU, retail price, and recommended retail detail."
        },
        {
          "name": "Discontinue",
          "description": "Sets the HQ product deprecation timestamp after confirmation."
        },
        {
          "name": "Restore",
          "description": "Clears the HQ product deprecation timestamp."
        },
        {
          "name": "Publishing boundary",
          "description": "This screen observes existing links; it does not provide create, edit, publish, field-control, or location-availability actions."
        }
      ],
      "expectedResult": "The shared product exists once in the master catalog and approved storefronts receive the intended master values while retaining supported local overrides.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-billing",
      "url": "https://platform.getcentri.com/centripos/network-billing",
      "title": "Review Franchise Billing Safely",
      "summary": "Inspect franchise invoices, fee structures, billing contacts, and masked saved-payment summaries while the launch-safety read-only lock is active.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Billing",
      "introduction": "The live Harbor & Hearth screen is deliberately read-only. Invoice history, fee structures, contacts, and masked payment summaries can be reviewed, but generating, editing, sending, collecting, refunding, deleting, or changing vault records is temporarily paused.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Billing. Confirm the page heading is Franchise Billing and read the amber launch-safety notice before using any displayed information.",
        "Use All Franchisees to view every permitted child business or narrow the page to one franchisee. This filter applies to Invoices, Fees, Contacts, and Vault; an empty result may simply mean the selected franchisee has no records of that type.",
        "On Invoices, optionally choose All Statuses, Draft, Sent, Paid, Overdue, Void, or Refunded. Read invoice number, franchisee, billing period, total, status, and due date together. A status or total is a summary—not proof of a processor settlement or accounting entry—so reconcile through the approved payment and accounting records when the distinction matters.",
        "Use Draft for an invoice not yet issued, Sent for one delivered for payment, Paid only when the billing record reports collection, Overdue when an issued balance passed its due date, Void for a cancelled invoice, and Refunded when the recorded payment was returned. Do not attempt to change a status from this locked screen.",
        "If No invoices found appears, wait for loading to finish, then check both filters. Try All Franchisees and All Statuses. If the empty state remains, it means no permitted invoice records matched; it does not mean Network Billing or every franchise relationship is unconfigured.",
        "Open Fees to inspect each configured charge. A row can show its label, franchisee, fee type, billing cycle, percentage rate or flat amount, effective start/end dates, and Inactive state. Percentage of Sales, Flat Fee, Tiered %, Marketing Fund, and Custom describe calculation intent; confirm the governing agreement before treating any displayed structure as contract authority.",
        "Open Contacts to review the people assigned to franchise billing communication. A row can show name, contact type, Primary badge, franchisee, title, email, and phone. Use this data only for authorized billing work, verify the recipient before sharing an invoice, and correct contact information through an approved administrator while editing is paused.",
        "Open Vault only when your role permits payment-summary access. The page may show Card or Bank Account, masked last four digits, franchisee, expiration, and Default. CentriPOS does not display a full card or bank number here. Never copy masked payment details into notes or infer that a saved method is valid, chargeable, or authorized for a particular invoice.",
        "Treat No fee structures configured, No contacts added yet, and No payment methods on file as completed empty results for the active franchisee filter. They are different from a spinner, permission error, or failed request.",
        "Do not look for Auto-Generate, New Invoice, Add Fee, Add Contact, edit, send, copy-payment-link, refund, void, delete, or vault-update controls during launch-safety mode. Their absence is intentional. Do not work around the lock through customer-facing links, direct database changes, or dormant application paths.",
        "For an urgent correction or collection, capture the franchisee, invoice number when present, visible status, expected outcome, and safe supporting context, then contact an authorized CentriPOS/network billing administrator. Do not include full payment credentials or unrelated customer data.",
        "The article screenshot is the real Amelia Grant Harbor & Hearth capture at 1440 × 900. It shows the launch-safety notice, Invoices tab, All Franchisees and All Statuses filters, and a loaded No invoices found state; it does not expose fees, contacts, payment methods, or invoice records."
      ],
      "controls": [
        {
          "name": "DollarSign navigation icon",
          "description": "Matches the Billing section icon used in the CentriPOS Network navigation."
        },
        {
          "name": "Launch-safety notice",
          "description": "Production boundary stating that billing mutations and collection actions are temporarily paused."
        },
        {
          "name": "All Franchisees",
          "description": "Shows records for every permitted child tenant; selecting one scopes all four tabs."
        },
        {
          "name": "All Statuses",
          "description": "Invoice-only filter for Draft, Sent, Paid, Overdue, Void, or Refunded."
        },
        {
          "name": "Invoice number",
          "description": "Network billing document identifier to include in an authorized support or reconciliation request."
        },
        {
          "name": "Billing period",
          "description": "Start and end dates represented by the invoice."
        },
        {
          "name": "Total",
          "description": "Invoice total in the tenant currency; it is not independently proof of cash settlement."
        },
        {
          "name": "Due date",
          "description": "Date the issued invoice is expected to be paid."
        },
        {
          "name": "Draft",
          "description": "Prepared but not issued."
        },
        {
          "name": "Sent",
          "description": "Issued for payment."
        },
        {
          "name": "Paid",
          "description": "Billing record reports payment received; reconcile externally when settlement proof is required."
        },
        {
          "name": "Overdue",
          "description": "Issued balance is past its due date."
        },
        {
          "name": "Void",
          "description": "Cancelled invoice that should not be collected."
        },
        {
          "name": "Refunded",
          "description": "Recorded payment has been returned."
        },
        {
          "name": "Fees",
          "description": "Read-only summaries of franchise charge structures, cycles, rates, dates, and active state."
        },
        {
          "name": "Contacts",
          "description": "Read-only billing-recipient summaries with contact type and Primary designation."
        },
        {
          "name": "Vault",
          "description": "Permission-limited masked card or bank-account summaries; never a source of full credentials."
        },
        {
          "name": "Default payment method",
          "description": "Preferred saved summary, not blanket authorization or a guarantee that a charge will succeed."
        },
        {
          "name": "Loaded empty state",
          "description": "No records matched the active tab and franchisee/status filters after loading completed."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real read-only Amelia Grant capture with no invoices or sensitive billing records exposed."
        }
      ],
      "expectedResult": "The billing period, participating storefronts, assessed amounts, status, and source activity reconcile without exposing unrelated tenant financial data.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/network-billing.png",
        "alt": "Harbor & Hearth Franchise Billing screen showing launch-safety read-only status, invoice filters, billing tabs, and the fully rendered empty invoice list in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "network-settings",
      "url": "https://platform.getcentri.com/centripos/network-settings",
      "title": "Manage Network Settings",
      "summary": "Administer the network hierarchy, network retail-price policy, role templates, organizations, owners, users, and inherited roles according to the current tenant type.",
      "collection": {
        "id": "network",
        "title": "Network"
      },
      "section": "Network Settings",
      "introduction": "This is an enterprise-management screen, not a collection of generic shared preferences. Its contents change for Platform, Agency, Enterprise HQ, child Organization, and Independent tenants. Child tenants cannot see Master Catalog, Billing, or Network Settings in Network navigation.",
      "beforeYouBegin": "Confirm the organization and participating locations. Network actions may affect more than one storefront.",
      "steps": [
        "Go to Network → Settings and confirm the identity card: Platform (Master), Agency, Enterprise (HQ), Organization, or Independent. Stop if the tenant type or parent relationship is not the one you intend to administer.",
        "For Enterprise HQ, review Network Pricing. Suggested Only lets organizations set retail while showing HQ recommended retail; Hard Sync overwrites organization retail on each product publish and hides suggested retail. Vendor cost remains flexible in either mode.",
        "Use Role templates to create or edit network role templates and permissions. Push templates only when approved: the push runs each current template through the child-role propagation routine for all organizations. Verify inherited copies in a selected organization.",
        "Search Organizations by organization or owner. The list shows owner, location count, and user count. Choose an organization row to open its detail rather than entering a proxy tenant.",
        "In organization detail, review the owner account and other users. Authorized actions can disable/enable access, send a password-reset email, and reassign the owner role to another listed non-owner. Each action has a confirmation and affects that child tenant’s user access.",
        "Review the organization’s roles as System, Inherited, or Custom. An Inherited role shows its HQ source; absence of a role in this list means the template propagation must be checked rather than assumed.",
        "Platform can add agencies, list all agencies, and enter an agency context. Platform and Agency can list enterprise networks, add a storefront, and Enter an HQ context. Enter changes the proxied operating tenant; verify the tenant banner before any further work.",
        "Enterprise HQ can add an Organization. Platform/Agency can add Storefronts. These dialogs create real tenant and owner structures, so confirm names, hierarchy, and owner details before submission.",
        "Treat Delete as irreversible. The confirmation states that the organization/storefront and associated users, locations, products, receipts, and roles are permanently deleted. Do not use it as deactivation or troubleshooting.",
        "For a child Organization, this screen is read-only network context plus Inherited from HQ roles. Manage its physical stores under Admin → Locations & Registers, not by creating more enterprise children here. Independent tenants see that they are not part of an enterprise network."
      ],
      "controls": [
        {
          "name": "Tenant identity",
          "description": "The current control-plane scope: Platform, Agency, Enterprise HQ, child Organization, or Independent."
        },
        {
          "name": "Hard Sync retail",
          "description": "HQ retail overwrites organization retail on every product publish; suggested retail is hidden."
        },
        {
          "name": "Suggested Only",
          "description": "Organizations set their own retail and see HQ recommended retail as Suggested Retail."
        },
        {
          "name": "Vendor cost",
          "description": "Always remains flexible per organization regardless of retail-price mode."
        },
        {
          "name": "Role template",
          "description": "HQ-defined custom role marked as a template for propagation to child organizations."
        },
        {
          "name": "Push templates",
          "description": "Runs current HQ templates through the child-role propagation function; verify inherited copies afterward."
        },
        {
          "name": "Organization detail",
          "description": "Child tenant counts, owner and user access controls, and its System, Inherited, and Custom roles."
        },
        {
          "name": "Disable Access",
          "description": "Deactivates the selected child-tenant user and prevents login."
        },
        {
          "name": "Reset Password",
          "description": "Sends the selected user a password-reset email."
        },
        {
          "name": "Reassign Owner",
          "description": "Transfers the owner role to another selected user in the organization."
        },
        {
          "name": "Enter",
          "description": "Starts a proxied operating context for an agency or enterprise tenant; it is not the same as opening organization detail."
        },
        {
          "name": "Add Agency / Storefront / Organization",
          "description": "Creates a tenant at the hierarchy level allowed by the current account type."
        },
        {
          "name": "Delete Permanently",
          "description": "Irrecoverably deletes the selected tenant and its associated operational data after confirmation."
        },
        {
          "name": "Inherited from HQ",
          "description": "Read-only role copies visible to a child Organization."
        },
        {
          "name": "Navigation boundary",
          "description": "Child organizations retain Network Sales, Reports, Inventory, and Transfers but do not receive Catalog, Billing, or Settings tabs."
        }
      ],
      "expectedResult": "Only the intended organization-level setting changes, participating storefront scope remains correct, and a controlled local check reflects the shared behavior.",
      "troubleshooting": [
        "Confirm the organization and participating locations before comparing, publishing, or transferring.",
        "Keep local and network-level records distinct when reviewing inventory or catalog values.",
        "Check whether your network role allows the action shown in the guide."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "dashboard",
      "url": "https://platform.getcentri.com/centripos/dashboard",
      "title": "Read the CentriPOS Dashboard",
      "summary": "Scope the retail dashboard correctly, distinguish billed, collected, open, and excluded lifecycle buckets, finish missing interaction reports, and drill into the customer, product, payment, staff, and receipt evidence that is actually linked.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Dashboard",
      "introduction": "Reports → Dashboard uses the Gauge icon. It is an RPC-backed current-data summary for the active tenant, the signed-in user’s visible locations, the selected Day/Week/Month/Year, and URL-backed product filters. It is not scoped to the operating-context register: excludedRegisterIds is null. Most KPI cards display an “Open … report” button that currently has no navigation handler; only the explicit Open status report, Open center, customer-account collection rows, product quick view, customer profile, and recent-receipt links are working drill paths on this screen. The approved Harbor & Hearth Dashboard capture was rejected because it remained in a missing-report/location loading state.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Go to Reports → Dashboard, identified by the Gauge icon. Confirm the active business in the app context. Do not assume the selected operating register limits the dashboard; the dashboard sends the permitted location IDs but no register exclusion/filter.",
        "Wait for the initial dashboard response. A full-page spinner means the first retail-dashboard RPC is loading. Dashboard data did not load prints the request error and offers Retry dashboard. Dashboard is loading means no normalized response exists yet and offers Load dashboard. Dashboard needs a retry is a render-error boundary, not a data conclusion.",
        "Set View to Day, Week, Month, or Year. Day covers the selected local day; Week starts Monday; Month covers the selected calendar month; Year covers a prior full year or the current year through today. Comparisons use Previous day, Previous week, Previous month, or Previous year respectively.",
        "Use the left/right arrows to move one period. Next is disabled for the current period. Choose the date label to pick a day inside the desired period, jump by month/year from 2000 through the current month, or choose Today to return the anchor to now without changing Day/Week/Month/Year mode.",
        "Use Location to select among locations visible to the signed-in user. With no selection, the RPC receives null and represents all visible locations. Invalid or unauthorized location IDs from a shared URL are removed after the location list loads. Confirm the displayed location count/name before comparing totals.",
        "Understand the URL state. View, anchor date, selected locations, Product movement sort/direction, and product Brand/Category/Supplier/Tag filters are written into the dashboard URL. Clear filters resets to Day, today, all visible locations, Product Revenue descending, and no product attributes. It does not change tenant or register context.",
        "Wait for Updating to finish after a filter change. The query can temporarily retain the previous response as placeholder data while fetching the new scope. Never copy a number mid-update without rechecking the final date/location label. Desktop prefetches adjacent periods; mobile does not.",
        "Review Interaction reports to finish before using interaction conversion metrics. The queue selects up to 40 newest tenant sales with no primary interaction, excludes only voided and refunded statuses at the query level, applies location scope and configured receipt-prompt rules, then shows at most 20. It is a work queue, not a complete exception report.",
        "For each missing-report row, confirm receipt number, customer/no customer, location, register, updated time, status, and total. Choose Log to open the sale-linked interaction form. Save one accurate interaction, close the dialog, and verify the queue/sales data refresh. Do not log a made-up interaction merely to clear the badge.",
        "Choose Refresh in the missing-report panel to refetch both prompt settings and queued sales. No missing interaction reports means none survived this limited/configured query; it does not prove every historical receipt has interaction context.",
        "Read Interactions for the selected period and location scope: Logged, Won, Lost or left without buying, Sale / save, No sale/save, and recent visible activity with owner/location and Won/Lost/Saved/Open classification. Choose Open center for the working detailed route. An interaction-summary error is isolated and does not invalidate the retail RPC totals.",
        "Read Revenue status first. Billed revenue is Completed + completed layaway revenue plus open Customer Account/on-account and layaway balances. Completed / collected is closed new-sale revenue plus Customer Accounts payments collected by payment date; it can therefore differ from billed revenue.",
        "Open customer balances is revenue from on-account and layaway receipts still open. Excluded is calculated as the nonnegative remainder of the maximum of current KPI revenue or summed receipt-status revenue, less billed and collected-account components; it is labeled saved, voided, cancelled, or incomplete activity. Reconcile unusual residuals in Sales Reports rather than treating the label as exact row-level proof.",
        "Choose Open status report for the working status/revenue Report Center route. When Customer Accounts payments collected is positive, expand it to see linked receipts with customer, location, payment methods/count, and collected amount; choose a row to open that receipt. If collection detail is unavailable, the aggregate can still be included above.",
        "Review primary KPIs: Revenue, Sales, Customers, and Gross profit. Each shows current, previous-period value, absolute movement, and percentage change when calculable. A zero previous value with positive current displays +100%; two zeros display No change. This is a display convention, not an infinite-growth calculation.",
        "On desktop, Revenue can show up to six location contributions and a sparkline. Switch its two-dot panel to Receipt status to view status breakdown; on mobile use the bottom dots or swipe horizontally at least 36 pixels. The headline Revenue value remains the current KPI while the panel changes.",
        "Treat each KPI’s Open revenue/sales/customers/gross profit/discount/average report text carefully: these are plain buttons with no click handler in the current component. They do not open Report Center. Use the explicit Open status report or go to Reports → Report Center manually with the same date/location scope.",
        "Review Discounts given, Discount rate, Average ticket, and Avg. items / sale against the previous period. Gross profit depends on the cost basis returned by the dashboard RPC; missing/zero product cost can distort it. Validate finance decisions in the detailed report and source product costs.",
        "Use Product movement only when products_sold is returned. Summary tiles show filtered Units sold, Product revenue, Avg item revenue, and Discounts. Sort by Revenue, Qty Sold, or Discounted; choosing the active sort reverses direction. Results are paged ten at a time.",
        "Filter Product movement by Brand, Category, Supplier, and Tag. The dashboard matches the RPC product row to the current catalog by SKU for filtering; rows lacking a matching catalog SKU can disappear when any attribute filter is active. Product quick view resolves by product ID, then SKU, then normalized name. Verify the exact product/variant before editing elsewhere.",
        "Read each product row as Qty Sold, Revenue, Revenue lost/discount, and average discount percent derived from discount divided by revenue plus discount. Product filters affect Product movement totals/list only; they do not refetch or narrow the top Revenue/Sales/Customer KPIs.",
        "On desktop only, Revenue by day renders when trend rows exist. Mobile intentionally suppresses the daily chart and KPI sparklines. A chart render failure can leave an empty bounded area while other dashboard sections continue; do not infer zero revenue from a missing chart.",
        "Payment methods appears only when rows exist and shows transaction/use count by method; although the RPC also returns amount, this dashboard section displays count only. Do not reconcile tender dollars from these tiles. Use payment/register reports.",
        "Top salespeople appears only when rows exist and shows user, revenue, sale count, items sold, and average sale value. It reflects the returned selected period/location scope and is not commission/payroll authority. Confirm effective user attribution, returns, account collections, and report rules before compensation decisions.",
        "Recent transactions appears only when rows exist, ten per page. Choose the receipt number to open /sales/receipts/<sale ID>. Choose a named non-walk-in customer to open the customer profile. Walk-in, item count, transaction time, total, and cashier are summary evidence; opening a receipt must not change the surrounding receipt list’s scope.",
        "Use Clear filters and reconstruct the intended scope when totals look wrong. Then compare Revenue status with the explicit status report, Customer Accounts collection receipts, source receipts, register reports, payment reports, product costs, and interaction center. Record tenant, date mode/anchor, location IDs, URL filters, update state, and receipt IDs when escalating.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Dashboard inspection remained in a missing-interaction/location loading state, so the invalid capture was removed rather than shown as a completed dashboard or replaced with another screen."
      ],
      "controls": [
        {
          "name": "Gauge icon",
          "description": "Exact CentriPOS Reports navigation and mobile-header icon for Dashboard."
        },
        {
          "name": "Day / Week / Month / Year",
          "description": "Calendar scope; weeks begin Monday and current year runs through today."
        },
        {
          "name": "Previous period comparison",
          "description": "Previous day, Monday-based week, month, or year aligned to the selected mode."
        },
        {
          "name": "Date picker",
          "description": "Choose an anchor date and jump from 2000 through the current month; future dates are unavailable."
        },
        {
          "name": "Location",
          "description": "Signed-in user’s visible locations; no selection means all visible locations."
        },
        {
          "name": "No register filter",
          "description": "Dashboard RPC receives no excluded-register IDs and is not limited by the operating-context register."
        },
        {
          "name": "URL filters",
          "description": "View, date, locations, product sort/direction, brands, categories, suppliers, and tags."
        },
        {
          "name": "Updating",
          "description": "New scope is fetching while prior placeholder data may remain visible."
        },
        {
          "name": "Clear filters",
          "description": "Day/today/all visible locations/product revenue descending/no product attributes."
        },
        {
          "name": "Interaction reports to finish",
          "description": "Limited prompt-configured queue of missing primary interactions, at most 20 from 40 queried sales."
        },
        {
          "name": "Log",
          "description": "Opens the sale-linked interaction capture dialog and refreshes queue/sales after close."
        },
        {
          "name": "Interactions",
          "description": "Logged, won, lost, sale/save, no sale/save, and recent classified activity."
        },
        {
          "name": "Open center",
          "description": "Working link to Communications interaction overview."
        },
        {
          "name": "Billed revenue",
          "description": "Completed and completed-layaway revenue plus open on-account/layaway revenue."
        },
        {
          "name": "Completed / collected",
          "description": "Closed new-sale revenue plus Customer Accounts collections by payment date."
        },
        {
          "name": "Open customer balances",
          "description": "Open on-account and layaway revenue."
        },
        {
          "name": "Excluded",
          "description": "Nonnegative residual labeled saved/voided/cancelled/incomplete; validate in status report."
        },
        {
          "name": "Open status report",
          "description": "Working Report Center link for status measured by revenue."
        },
        {
          "name": "Customer Accounts payments collected",
          "description": "Expandable receipt-level collection rows when available."
        },
        {
          "name": "Revenue / Sales / Customers / Gross profit",
          "description": "Current and previous-period KPI cards."
        },
        {
          "name": "Revenue card panels",
          "description": "Location contribution or receipt-status detail selected with dots/swipe."
        },
        {
          "name": "Open … report KPI buttons",
          "description": "Currently inert plain buttons with no navigation handler."
        },
        {
          "name": "Discounts given / Discount rate / Average ticket / Avg. items per sale",
          "description": "Secondary period KPIs and comparisons."
        },
        {
          "name": "Product movement",
          "description": "RPC products_sold summary, sorting, catalog-SKU attribute filtering, ten-row pagination, and quick view."
        },
        {
          "name": "Product filters boundary",
          "description": "Narrows Product movement only, not headline dashboard KPIs."
        },
        {
          "name": "Revenue by day",
          "description": "Desktop-only bar chart."
        },
        {
          "name": "Payment methods",
          "description": "Count only on this screen even though amount exists in returned data."
        },
        {
          "name": "Top salespeople",
          "description": "Revenue, sale count, items, and average sale; not payroll authority."
        },
        {
          "name": "Recent transactions",
          "description": "Ten-row pages with working receipt and eligible customer-profile links."
        },
        {
          "name": "Dashboard data did not load",
          "description": "RPC error with Retry dashboard."
        },
        {
          "name": "Dashboard is loading",
          "description": "No successful normalized response yet with Load dashboard."
        },
        {
          "name": "Dashboard needs a retry",
          "description": "Render-error boundary with retry that remounts the view."
        },
        {
          "name": "No public screenshot",
          "description": "Rejected real Harbor & Hearth loading-state capture; no substitute or fabrication."
        }
      ],
      "expectedResult": "The dashboard has finished updating and its tenant, Day/Week/Month/Year, anchor date, and visible-location scope are confirmed; billed, collected, open, excluded, KPI, interaction, product, payment-count, staff, and recent-receipt summaries reconcile to the working detailed routes and source records, while product-only filters and inert KPI report buttons are not mistaken for global filters or drilldowns.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sales-reports",
      "url": "https://platform.getcentri.com/centripos/sales-reports",
      "title": "Build a Sales Report",
      "summary": "Turn CentriPOS sales into a focused table or chart, then save, share, print, export, or open the exact receipts behind a result.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Reports",
      "introduction": "Sales Reports is the full reporting workspace behind both the standalone Sales Reports screen and Report Center. Your date range, report type, measures, filters, receipt scope, breakdowns, and permissions all affect what appears.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Open Sales → Sales Reports. The Bar Chart icon and Sales Reports label take you to the standalone reporting workspace; Report Center uses the same report engine inside a broader reports home.",
        "Start with Report type. Choose Sales summary or Receipt status, or group results by User, Location, Register, Customer, Customer group, Product, SKU name, Brand, Supplier, Product category, or Tag.",
        "Set the date range. Use a quick period such as Today, This week, Year to date, Last 30 days, or Last month, or choose a specific custom range and time.",
        "Choose the Measures you need. Revenue is always available; other choices include sale and customer counts, items sold, tax, tips, discounts, returns, average sale values, gross profit, margin, markup, cost of goods, and e-cart measures. On a chart, the measure marked Chart is the primary plotted measure.",
        "Set Comparison to No comparison, Previous period, Same dates in previous year, or Same period in previous year. The last option aligns matching weekdays rather than identical calendar dates.",
        "Add Include or Exclude filters. The filter picker supports product, SKU, variant value or attribute, brand, category, supplier, tag, receipt status, payment type, customer, customer group, user, location, and register.",
        "For a product-related filter, choose whether a receipt qualifies because it contains the item or whether only matching line items contribute to the result. This receipt-scope choice can change revenue and quantity totals even when the visible filter chip is the same.",
        "Decide whether to include gift card sales. Keep the setting consistent when you compare this report with another total.",
        "Open the advanced report controls when you need a different layout. Split date columns by month, week, weekday, or hour; add product, SKU, brand, category, or location detail beneath each row; select extra row data; and set the table sort.",
        "Read the summary cards, chart, and table together. Click a sortable table heading to change order. Receipt status reports use lifecycle buckets, while other report types group the same eligible sales by the dimension you selected.",
        "Open a value or row drill-down to see the exact receipt set behind it. CentriPOS passes that saved receipt set to Receipts, so the resulting receipt list should explain the aggregate without changing to a broader location or register search.",
        "Select Save view to keep the full setup. Personal views are visible only to you; shared views are visible to your company and require permission to create or manage. Pin frequently used views above the filters.",
        "Use Share to copy a link to the current configuration. The recipient still needs a Centri Account, access to the tenant, and permission to see the underlying locations and financial data.",
        "Use Print / PDF to choose layout, margins, and whether to include the chart. Use Export CSV to download the current table rows; it exports the report as configured, not every possible sales field.",
        "Before reconciling a total, confirm the displayed date and time range, comparison, location and register scope, receipt statuses, product receipt-scope rule, gift card setting, and active saved view. Cost, profit, margin, and other protected values appear only when your role allows them."
      ],
      "controls": [
        {
          "name": "Report type",
          "description": "Chooses the main question and first row grouping: summary, receipt status, people, locations, customers, or product dimensions."
        },
        {
          "name": "Date range",
          "description": "Accepts quick periods or a precise custom date-and-time range. CentriPOS calculates the report in the applicable business and location time context."
        },
        {
          "name": "Measures",
          "description": "Selects the numeric or date columns shown. The measure carrying the Chart badge drives the chart."
        },
        {
          "name": "Comparison",
          "description": "Places the chosen range beside a prior range or one of two previous-year alignments."
        },
        {
          "name": "Include / Exclude filters",
          "description": "Narrows eligible sales with searchable chips for merchandise, receipts, payments, customers, users, locations, and registers."
        },
        {
          "name": "Receipt scope",
          "description": "For merchandise filters, decides between qualifying the whole receipt and counting only matching sale lines."
        },
        {
          "name": "Include gift card sales",
          "description": "Controls whether gift card sales participate in the report totals."
        },
        {
          "name": "Date columns",
          "description": "Shows the selected range as one total or separates it by month, week, weekday, or hour."
        },
        {
          "name": "Row breakdown",
          "description": "Adds product, SKU, brand, category, or location detail under the main report rows."
        },
        {
          "name": "Extra row data",
          "description": "Adds supported identifying or descriptive fields beside the selected breakdown."
        },
        {
          "name": "Sort controls",
          "description": "Orders the current table by its label or an available measure; table headings can also be used to sort."
        },
        {
          "name": "Saved Views",
          "description": "Reopens a stored report configuration. Views can be personal or company-shared, and pinned views stay close to the filters."
        },
        {
          "name": "Share",
          "description": "Copies a link containing the current report setup; it does not bypass sign-in or data permissions."
        },
        {
          "name": "Print / PDF",
          "description": "Builds a printable version with orientation, margin, and chart options."
        },
        {
          "name": "Export CSV",
          "description": "Downloads the rows and columns in the current table."
        },
        {
          "name": "Receipt drill-down",
          "description": "Opens the precise receipts contributing to the selected result so the aggregate can be audited."
        }
      ],
      "expectedResult": "The chart, table, and totals reflect the same report type, measures, date and time range, comparison, filters, receipt-scope rule, gift card setting, breakdowns, saved-view state, and user permissions; opening a drill-down produces the exact receipt set behind the selected result.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "report-center",
      "url": "https://platform.getcentri.com/centripos/report-center",
      "title": "Use Report Center",
      "summary": "Choose the right sales or operational report, carry only compatible scope between report families, and verify every total before saving, sharing, printing, or exporting it.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Reports",
      "introduction": "Reports → Report Center uses the BarChart3 icon. Report Center is a selector wrapped around two full report engines: Sales reports and Operational reports for payments, cash movements, users, tax, gift cards, and store credit. A report is only as accurate as its active business, permitted locations, date/time, measures, grouping, receipt rules, and include/exclude scope. Switching report families deliberately preserves only parameters the engines share.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Open Reports → Report Center beside the BarChart3 vertical-bars icon. Confirm the active CentriPOS business and the user’s authorized location scope before interpreting any total. The default family is Sales unless the URL selects a supported operational family.",
        "Open Report. The button shows the current report’s friendly label and description. Choose a report opens a searchable menu grouped into Start here, Sales drilldowns, and Operations drilldowns. The group containing the current selection is expanded; Start here is also expanded by default, while unrelated deeper groups begin collapsed.",
        "Use Search reports to match a report label, description, internal report type, report family, group label, or group description. Search temporarily shows every matching group expanded. No reports match that search is a completed selector result, not evidence that reporting data is absent. Closing the selector clears the search.",
        "Use Start here for everyday questions: Sales summary; Receipt status; Payment types; Cash movement; Team performance; Tax; Gift Cards; and Store credit. The selector’s short description tells you what the report is designed to answer; it does not override the filters and permissions in the report engine below.",
        "Use Sales drilldowns to group eligible sales by a supported sales dimension such as user, location, register, customer, customer group, product, SKU name, brand, supplier, product category, or tag. Use Operations drilldowns for nondefault breakdowns offered by the selected payment, cash, user, tax, gift-card, or store-credit family.",
        "Understand what changes when you choose a report. Selecting another report in the same family calls that report engine’s type-change control. Selecting a different family rebuilds the Report Center URL and carries only preset, from, to, comparison, include, exclude, and showExclude when present, then sets the selected type. Family-specific measures, breakdowns, columns, sorts, saved-view state, and other parameters are not promised to transfer.",
        "After any family change, recheck the selected report label and every visible control. Confirm the date preset or exact From/To times, comparison, authorized locations and registers, receipt status/scope, gift-card treatment, measures, breakdown/grouping, sorting, and any family-specific choices. Do not assume a visually similar chip means identical sales-versus-operational semantics.",
        "Review Include and Exclude chips before reconciling. Show exclusions means intentionally omitted matches are visible for review; it does not disable those exclusions. Merchandise filters can also change whether the whole receipt qualifies or only matching sale lines contribute. Reconfirm that receipt-scope rule in Sales reports.",
        "Wait for loading/updating states to finish. Read headline cards, chart, and table together. A headline that cannot be traced through the current rows, receipt set, payment/cash ledger, tax detail, credit/gift-card movement, or user detail should be treated as unresolved until the source records explain it.",
        "Use a working drill-down to open the exact receipt or operational record set behind a value. Confirm representative rows from different dates, locations, statuses, and payment/record types when the result will drive reconciliation, tax, payroll, purchasing, or customer action. Do not rely on an inert or absent drill-down control.",
        "Save a report view only after the selector, dates, scope, filters, exclusions, measures, and grouping are correct. A saved view stores configuration and reruns against current permitted data; it is not a frozen copy of today’s totals. Personal and Company-wide visibility remain subject to the report engine’s permissions.",
        "Use Share only after reviewing the URL-backed state. The recipient must sign in to the same authorized Centri business and can see only permitted data. Do not assume the link grants access or that every transient control was encoded; reopen the copied link in an authorized test session when the exact setup matters.",
        "Use Print / PDF or Export CSV only where the selected report engine provides it. The output reflects the active table/configuration rather than every possible field. Inspect filenames, date labels, columns, totals, exclusions, customer detail, financial detail, and page layout before distributing it.",
        "If a result changes unexpectedly after switching families, return to the prior report and compare the URL/control state. The cross-family handoff preserves only seven shared keys—preset, from, to, comparison, include, exclude, and showExclude—plus the new type. Rebuild any dropped family-specific choices deliberately.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth /dashboard/reports inspection remained on metric skeletons and a loading spinner, so the invalid capture was removed instead of being presented as a completed report or replaced with a different screen."
      ],
      "controls": [
        {
          "name": "BarChart3 icon",
          "description": "Exact CentriPOS navigation icon for Reports → Report Center."
        },
        {
          "name": "Report",
          "description": "Current report selector showing the chosen friendly label and its purpose."
        },
        {
          "name": "Choose a report",
          "description": "Searchable popover containing Start here, Sales drilldowns, and Operations drilldowns."
        },
        {
          "name": "Search reports",
          "description": "Matches report/group labels, descriptions, internal type, and family; it clears when the selector closes."
        },
        {
          "name": "Start here",
          "description": "Sales summary, Receipt status, Payment types, Cash movement, Team performance, Tax, Gift Cards, and Store credit."
        },
        {
          "name": "Sales drilldowns",
          "description": "Sales report types grouped by one supported sales dimension."
        },
        {
          "name": "Operations drilldowns",
          "description": "Nondefault report types from payment, cash-movement, user, tax, gift-card, and store-credit families."
        },
        {
          "name": "Same-family selection",
          "description": "Changes the type inside the current Sales or Operational report engine."
        },
        {
          "name": "Cross-family selection",
          "description": "Navigates to the new family and type while copying only compatible shared URL parameters."
        },
        {
          "name": "Shared cross-family parameters",
          "description": "preset, from, to, comparison, include, exclude, and showExclude."
        },
        {
          "name": "Date preset / From / To",
          "description": "Relative or exact reporting period. Reconfirm time boundaries after changing report family."
        },
        {
          "name": "Comparison",
          "description": "Supported prior-period context interpreted by the active report engine."
        },
        {
          "name": "Location / register scope",
          "description": "Authorized operating records included in the result; exact controls vary by family."
        },
        {
          "name": "Measure",
          "description": "Value calculated, such as revenue, count, tax, margin, or movement amount."
        },
        {
          "name": "Grouping / breakdown",
          "description": "Dimension organizing table or chart values."
        },
        {
          "name": "Include / Exclude",
          "description": "Matching rules carried between families only when the active engine can interpret them."
        },
        {
          "name": "Show exclusions",
          "description": "Displays active exclusion context for review; it does not remove the exclusion."
        },
        {
          "name": "Receipt scope",
          "description": "For supported merchandise filters, whole-receipt qualification versus matching-line-only contribution."
        },
        {
          "name": "Row detail / drill-down",
          "description": "Underlying receipts or operational records when the active report implements a working path."
        },
        {
          "name": "Save view",
          "description": "Stores configuration for a current-data rerun, not a historical snapshot."
        },
        {
          "name": "Share",
          "description": "Copies supported URL state without granting tenant or financial permission."
        },
        {
          "name": "Print / PDF / Export CSV",
          "description": "Engine-specific output of the active configuration; review sensitive and financial content before distribution."
        },
        {
          "name": "No substituted screenshot",
          "description": "The Harbor & Hearth route remained in a skeleton/loading state and was rejected rather than misrepresented."
        }
      ],
      "expectedResult": "The selected report opens with the intended dimensions and measures, and its total can be traced through drill-down rows to source records.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "register-reports",
      "url": "https://platform.getcentri.com/centripos/register-reports",
      "title": "Review register reports and closures",
      "summary": "Find a live or closed register session, reconcile receipts and tender, inspect every transaction, understand CentriPay deposit readiness, and control the report’s QuickBooks lifecycle.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Reports",
      "introduction": "Open Reports → Register Reports with the Lock Keyhole icon. A register report is one register session: operational receipt activity, tender counted at close, cash movements, processor evidence, accounting status, and later corrections must all be read in that same session scope. Closing a drawer is not proof that its processor deposit has settled or that QuickBooks has received the report.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Go to Reports → Register Reports. Search can match report number, notes, MM/DD/YYYY dates, amounts, users, registers, and receipt-related terms. Use the Register and Location multi-selects together, set a Date range, and choose All, Open, or Closed.",
        "Understand the date rule before filtering: the date range uses closed date for closed reports and opened date for live drawers. Selected locations narrow the available registers, and selected registers narrow the available locations; an incompatible selection can be removed automatically.",
        "Sort by Register, Report #, Opened, or Closed. Selecting the active sort again reverses it; Date order offers Newest and Oldest. The default optimized list loads recent closed-date results in pages, while search or another sort loads the matching result set for client-side processing.",
        "Read each report card before opening it: location, register, Report #, opened time, Open now or closed time, Live state, Net, Variance, activity chips, notes, and applicable processor or QuickBooks status. Variance is the saved counted-tender difference when tender rows exist; it is not simply total sales minus cash.",
        "Interpret accounting/processor badges carefully. QBO Synced means CentriPOS has a linked posted QuickBooks record. Send to QBO is a manual action for an eligible closed report. Needs resync means sale activity changed after the accounting checkpoint. Awaiting EPX Deposit means CentriPay tender is waiting for matching deposit evidence; Open EPX Batch means settlement has not reached the required closed/deposit state; EPX Review Needed means processor evidence conflicts with the register totals.",
        "When authorized CentriPay reporting is connected, choose Check for New Deposits only after a deposit is visible in the bank statement or processor reporting and the expected scheduled refresh has not resolved it. The check refreshes scoped deposits, batches, and transactions; it deliberately skips automatic QBO sync in this manual operation.",
        "Choose Export CSV to export every report matching the current register, location, date, status, search, and sort—not just the currently loaded page. The file includes report identity, lifecycle dates, totals, variance, payment columns, activity, and QuickBooks status. Stop if No register reports match the current export filters appears.",
        "Open the exact report. Register Report Summary begins with View full details and print/export actions, then identifies the location, register, report number, open/closed lifecycle, opener/closer, opening float, notes, and relevant audit or accounting notices.",
        "Review Closure Reconciliation first. Receipt total, collected tender, and counted tender should agree after the report’s rounding and supported adjustments. Read any receipt/tender adjustment, the last QuickBooks payload when shown, and reconciliation warnings before relying on a headline total.",
        "Review Receipt Activity by lifecycle rather than treating every row as a new completed sale. The report separates completed receipt activity, returns/refunds, voided or excluded activity, layaway payments, incomplete-sale payments, and Customer Accounts payments. Account payments collected during the session are activity for this closure but are not a second new sale.",
        "Review Payment Types. Expected is the tender derived for that session; Counted is what was recorded at close; Difference is Counted minus Expected. Total collected summarizes closure tender. Customer-account payments can be displayed separately and explicitly are not added again to Total collected.",
        "For CentriPay/EPX, follow View batch or View deposit when available. A matched batch, initiated deposit, fee evidence, and reconciliation can arrive after the register closes. Gateway EPX Deposit is tracked separately where shown. Do not force QuickBooks sending merely because the report status is Closed.",
        "Review Cash Movements for opening float context, pay-ins, pay-outs, and their user/time evidence. Reconcile the Cash tender with the drawer formula used at close rather than comparing it only with receipt cash lines.",
        "Choose View full details to inspect the source transaction rows. Use this view to identify completed sales, refunds/returns, voids, layaway activity, account completions, payment mismatches, and individual payment summaries that explain the report totals. Open the specific receipt when supported instead of changing the report scope.",
        "Use Send to QBO only when the report is eligible and the intended QuickBooks connection/mappings are verified. CentriPay reports can remain blocked until EPX settlement evidence is reconciled. If QBO Synced is linked, open the saved QuickBooks document; do not send a duplicate because an external page is slow.",
        "If Needs resync appears, inspect which sale changed after close and the last edit time. Resend only after confirming the corrected receipt and closure totals. Authorized users can dismiss the resend notice through the displayed checkpoint; a newer sale edit will create another notice.",
        "Use report correction controls only with authorization and a written Correction note. The editor can correct session-owned timestamps, opener/closer, opening float, opening/closing notes, and counted tender rows. Ledger-driven sales totals are recalculated, every change is audited, and corrected tender rows update the list variance and future accounting payload.",
        "Disconnect QuickBooks link is a finance-level exception. It removes only the saved CentriPOS link for the exact report after typed confirmation; it does not delete, void, or edit the invoice or payments already in QuickBooks. Reconcile the external records before using it.",
        "After any correction, deposit refresh, or accounting action, reload the same report and verify its report number, session scope, receipt total, expected/counted tender, variance, processor evidence, accounting badge, and correction history. Never move or correct sales between closures merely to make totals look balanced without source evidence."
      ],
      "controls": [
        {
          "name": "Lock Keyhole icon",
          "description": "The exact CentriPOS navigation icon for Reports → Register Reports."
        },
        {
          "name": "Search",
          "description": "Matches report identity, notes, dates, amounts, users, registers, and receipt-related search terms."
        },
        {
          "name": "Register / Location filters",
          "description": "Multi-select filters that narrow one another to compatible operating contexts."
        },
        {
          "name": "Date range",
          "description": "Filters closed reports by closed date and live drawers by opened date."
        },
        {
          "name": "All / Open / Closed",
          "description": "Limits reports by register-session lifecycle."
        },
        {
          "name": "Register / Report # / Opened / Closed sort",
          "description": "Controls report ordering; selecting the active field reverses direction."
        },
        {
          "name": "Newest / Oldest",
          "description": "Explicit date order for Opened or Closed sorting."
        },
        {
          "name": "Report card",
          "description": "Location, register, report number, lifecycle, net, variance, activity, notes, and accounting/processor readiness summary."
        },
        {
          "name": "Live",
          "description": "The register session is still open; counted tender and closing evidence are not final."
        },
        {
          "name": "Net",
          "description": "Session receipt activity after the report’s included returns/refunds and lifecycle rules."
        },
        {
          "name": "Variance",
          "description": "Saved counted tender minus expected tender across closure-payment rows; a zero is not proof of processor settlement."
        },
        {
          "name": "QBO Synced",
          "description": "A posted QuickBooks closure record is linked and can open the saved external document when its URL is available."
        },
        {
          "name": "Send to QBO",
          "description": "Manual action for an eligible closed report without an existing linked QuickBooks record."
        },
        {
          "name": "Needs resync",
          "description": "One or more sale records changed after the relevant close/accounting checkpoint."
        },
        {
          "name": "Awaiting EPX Deposit",
          "description": "CentriPay tender exists, but matching initiated-deposit reconciliation is not ready."
        },
        {
          "name": "Open EPX Batch",
          "description": "Processor batch remains open, so deposit-backed QuickBooks sending must wait."
        },
        {
          "name": "EPX Review Needed",
          "description": "Processor gross, transactions, batch, deposit, or fee evidence does not reconcile with the closure and requires review."
        },
        {
          "name": "Check for New Deposits",
          "description": "Authorized manual processor refresh for the displayed date/location scope; it does not automatically send reports to QBO."
        },
        {
          "name": "Export CSV",
          "description": "Exports the entire current filtered/sorted report result, including dynamic payment-type columns and accounting status."
        },
        {
          "name": "View full details",
          "description": "Opens transaction-level evidence for the selected register session without broadening the report."
        },
        {
          "name": "Closure Reconciliation",
          "description": "Compares receipt total, collected tender, counted tender, adjustments, and available QuickBooks payload evidence."
        },
        {
          "name": "Receipt Activity",
          "description": "Lifecycle-aware completed, return/refund, voided, layaway, incomplete, and account-payment activity."
        },
        {
          "name": "Expected tender",
          "description": "Payment total CentriPOS derives for the exact session from eligible payment activity."
        },
        {
          "name": "Counted tender",
          "description": "Value physically counted or otherwise confirmed when the register was closed."
        },
        {
          "name": "Difference",
          "description": "Counted minus Expected for a payment type or the total closure tender."
        },
        {
          "name": "Total collected",
          "description": "Closure tender total; separately identified Customer Accounts payments are not added a second time."
        },
        {
          "name": "EPX batch / deposit link",
          "description": "Opens the matching processor evidence when the report has a supported linked record."
        },
        {
          "name": "Cash Movements",
          "description": "Opening float context plus pay-in/pay-out records, amounts, people, timestamps, and notes."
        },
        {
          "name": "Correction note",
          "description": "Required audit explanation for an authorized report correction."
        },
        {
          "name": "Correction history",
          "description": "Permanent before/after evidence for corrected session-owned fields or counted-tender rows."
        },
        {
          "name": "Disconnect QuickBooks link",
          "description": "Removes only CentriPOS’s saved link after privileged typed confirmation; it does not alter QuickBooks records."
        }
      ],
      "expectedResult": "The register report belongs to the intended session and reconciles opening float, sales, tender totals, cash movements, expected cash, counted cash, variance, and closing status.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "close-register",
      "url": "https://platform.getcentri.com/centripos/close-register",
      "title": "Close a register session",
      "summary": "Reconcile every tender against physical or independent evidence, record the actual drawer count, explain differences, and create one durable register report without masking processor or accounting exceptions.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Session control",
      "introduction": "Register → Session control uses the Banknote icon, and Close Register uses the Lock icon. Closing requires pos.register_open permission and is a one-time financial operation on the currently selected register session. Blank counted fields are parsed as zero, signed values are accepted by the input sanitizer, and a mismatch warning can be overridden, so accuracy depends on a deliberate independent count and documented approval—not merely reaching the closed state.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Before opening the close dialog, confirm the active business, location, register, OPEN badge, opening time, and effective user. The Close Register control appears only with pos.register_open permission. Stop if another register or user context is selected.",
        "Finish or deliberately resolve active selling work first. Review Receipt Activity across Completed, Saved, Incomplete, Layaways, Layaway Payments, Account Balance Open, Account Paid, Layaway Completed, Returns, Exchanges, and Voided. Open any unusual bucket or receipt rather than assuming its amount belongs in tender.",
        "Review Cash drawer movements. Drawer cash shown above the page is opening float plus manual pay-ins minus pay-outs and intentionally excludes customer Cash tenders. Confirm every safe drop, payout, or pay-in against the physical log and note. Never add a movement simply to force the close to balance.",
        "Review Payments Collected and expand each payment type to inspect contributing receipts. It includes supported payments collected on existing layaways. Review A/R/customer-account payments separately because the session screen keeps them outside register tender balancing by design.",
        "Resolve uncertain integrated-card results before closing. Check the sale payment row, terminal/processor transaction, and CentriPay evidence; do not resend, manually duplicate, void, or close over an unknown result simply because the terminal stopped responding.",
        "Add or edit Session Notes while the session is open when working context is useful. These lines are local component state, not independently saved journal entries. When Close Register opens, nonblank lines are joined with line breaks and copied into Closing Note; reopening the dialog copies the current Session Notes again.",
        "Choose Close Register beside the Lock icon. The dialog explicitly says to scroll. Review the entire Payments Collected list, Totals, Cash summary, and Closing Note before using the fixed footer action. On mobile, payment rows are cards in a separately scrollable area; on desktop, they appear in a table.",
        "When the dialog opens, counted values are reset. Every non-cash tender whose expected amount is within half a cent of zero starts as checked with 0.00. Cash always starts blank, even at zero. Every other tender starts blank and unchecked. Do not mistake a blank field for “not applicable”—the close operation parses it as zero.",
        "Verify one tender at a time using physical cash, processor/batch evidence, check log, external financing/gateway record, or the business’s approved source. Enter the actual Counted amount. The text field strips nonnumeric characters except a leading minus and decimal points; signed values can therefore be entered, but use a negative count only when the tender evidence truly requires it.",
        "Use the check box only after independent evidence proves Counted equals Expected. Checking fills the expected amount to two decimals. Unchecking clears the field. Manually editing a nonzero tender does not mark its checkbox; the checkbox is a convenience indicator, not an additional persisted approval record.",
        "Read Totals. Expected is the sum of all displayed payment-type expectations. Counted is the sum of parsed counted fields. Difference is Counted minus Expected. Values within $0.005 are treated as matched; because displayed money is two decimals, verify the actual source rather than relying on rounding edge cases.",
        "Review the Cash summary separately. Drawer base is opening float plus pay-ins minus pay-outs. Cash tenders collected comes from eligible session sale payments. Expected drawer cash is those two values added together. Cash difference is the Cash counted value minus expected drawer cash, rounded to two decimals.",
        "Do not force the overall tender Total to explain the physical drawer. Overall totals include every payment type, while the Cash summary isolates the drawer. A Balanced overall label means entered counts matched expected tender within tolerance; it does not prove processor settlement, deposit timing, bank receipt, inventory, or accounting sync.",
        "Review Closing Note. Replace or extend the copied Session Notes with a concise durable explanation of every approved over/short, processor uncertainty, missing check, safe drop, tender exception, or follow-up owner. The UI does not require a nonblank note before closing, even with a mismatch, so management policy must enforce the explanation.",
        "Choose Close Register once. The handler compares every displayed payment type. If all are within half a cent, it immediately submits the close. If any differ, Count Mismatch Detected lists their names, says management will be notified, and asks whether to continue. No separate notification record is visibly created by this component; the durable evidence is the saved close and note.",
        "Choose Go Back to recount or correct. Use Close Anyway only when the real mismatch is understood, authorized, and fully documented. Close Anyway submits the same count set. A blank missing count is zero and can therefore produce or conceal a mismatch when Expected is also zero—review each field before overriding.",
        "Wait for Register closed. The close operation stores closed user/time, every tender count in cash_counted, Cash as closing float and total, expected drawer cash, cash difference, and closing note. It clears the active-session cache, refreshes register/session/report/sale data, closes the dialog, and clears its local count and note state.",
        "The successful toast summarizes either all tenders matched, the number of payment types needing review, or both the Cash difference and mismatch count. This message is not the final report. Remain on Session Control and review Last Report, then choose View in Reports for the durable Register Reports record.",
        "After a successful close, CentriPOS starts a background processor-reconciliation refresh for the closed session. Failure is logged to the browser console and does not reopen or roll back the session. CentriPay batches and deposits can settle later, so Closed is not equivalent to deposit-reconciled or ready for QuickBooks.",
        "Audit the closed report: exact report/session number, location/register, opener/closer, open/close timestamps, receipt activity, expected and counted tender, variance, opening float, movements, notes, processor/deposit status, and accounting state. Trace any discrepancy through sale/payment → register session → closure tender → processor transaction/deposit → QuickBooks sync evidence.",
        "No close-dialog screenshot is published. The real Amelia Grant Harbor & Hearth image is the safe closed Session Control opening screen, not an active-session closeout. It remains attached to the broader session-control guide; using it here would falsely depict the close workflow."
      ],
      "controls": [
        {
          "name": "Banknote icon",
          "description": "Exact Register navigation icon for Session control."
        },
        {
          "name": "Lock icon",
          "description": "Exact action icon beside Close Register on an open session."
        },
        {
          "name": "pos.register_open",
          "description": "Permission required for the Open Register and Close Register controls."
        },
        {
          "name": "Receipt Activity",
          "description": "Session-attached receipts grouped by operational lifecycle; review exceptions before tender counts."
        },
        {
          "name": "Drawer base",
          "description": "Opening float + manual pay-ins − manual pay-outs; excludes customer Cash tenders."
        },
        {
          "name": "Payments Collected",
          "description": "Eligible session tender totals, including supported payments on existing layaways."
        },
        {
          "name": "A/R payments",
          "description": "Customer-account collections displayed separately and excluded from register tender balancing."
        },
        {
          "name": "Session Notes",
          "description": "Unsaved local working lines copied into Closing Note whenever the close dialog opens."
        },
        {
          "name": "Payments Collected close list",
          "description": "Every displayed tender with Expected, checkbox, and Counted value."
        },
        {
          "name": "Zero expected non-cash",
          "description": "Automatically initializes checked at 0.00 when within half a cent of zero."
        },
        {
          "name": "Cash initialization",
          "description": "Always blank and manual, even when Expected is zero."
        },
        {
          "name": "Expected tender",
          "description": "System-calculated eligible amount for that payment type in the exact session."
        },
        {
          "name": "Counted tender",
          "description": "Parsed actual value entered or copied with the checkbox; blank becomes zero."
        },
        {
          "name": "Verification checkbox",
          "description": "Convenience control that copies Expected to Counted; it is not separate persisted approval evidence."
        },
        {
          "name": "Signed currency input",
          "description": "Keeps a leading minus and numeric decimal content; verify any negative count carefully."
        },
        {
          "name": "Half-cent tolerance",
          "description": "A tender is mismatched only when absolute Counted − Expected exceeds 0.005."
        },
        {
          "name": "Totals Expected / Counted",
          "description": "Sums across every displayed tender type."
        },
        {
          "name": "Overall Difference",
          "description": "Total Counted − total Expected across displayed tenders."
        },
        {
          "name": "Balanced",
          "description": "Entered tender totals match within tolerance; not proof of settlement, deposit, inventory, or accounting reconciliation."
        },
        {
          "name": "Cash tenders collected",
          "description": "Eligible Cash payment amount derived from session sales."
        },
        {
          "name": "Expected drawer cash",
          "description": "Drawer base + Cash tenders collected."
        },
        {
          "name": "Cash difference",
          "description": "Counted Cash − expected drawer cash, rounded to two decimals."
        },
        {
          "name": "Closing Note",
          "description": "Durable closeout context stored on the register session; currently not required by the UI."
        },
        {
          "name": "Count Mismatch Detected",
          "description": "Lists tender names outside tolerance before allowing an override."
        },
        {
          "name": "Go Back",
          "description": "Returns to the close dialog without submitting so counts and note can be corrected."
        },
        {
          "name": "Close Anyway",
          "description": "Submits the mismatched count set; use only with approved, documented evidence."
        },
        {
          "name": "Register closed",
          "description": "Close RPC succeeded and the active session was cleared/refetched."
        },
        {
          "name": "Background processor refresh",
          "description": "Post-close reconciliation attempt that cannot roll back a successful close when it later fails."
        },
        {
          "name": "Register report",
          "description": "Durable session record containing lifecycle, receipts, expected/counted tender, cash movements, variance, notes, processor evidence, and accounting state."
        },
        {
          "name": "Screenshot boundary",
          "description": "The verified Harbor & Hearth capture shows the closed opening screen only, so it is not reused as a close-dialog image."
        }
      ],
      "expectedResult": "The session closes once with the submitted counts and notes, the calculated variance is recorded, and later sales cannot attach to that closed session.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "saved-views",
      "url": "https://platform.getcentri.com/centripos/saved-views",
      "title": "Use Saved Views",
      "summary": "Find, group, open, organize, and safely remove reusable Sales and Operational report configurations from one tenant-wide library.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Reports",
      "introduction": "Reports → Saved Views uses the Bookmark icon. This library combines active Sales report views and active Operational report views for the current CentriPOS business. It does not create a report, edit its analytical filters, or preserve old totals. Opening a card reruns the saved configuration against current permitted data. Company-wide organization/removal requires the account-owner permission used by this screen; personal views are manageable only by their creator.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Go to Reports → Saved Views, identified by the Bookmark icon. Confirm the active business because the library queries that tenant’s active Sales and Operational views only.",
        "Wait for Loading Saved Views to finish. If Couldn’t load Saved Views appears, read the returned error and retry only after connectivity, permissions, or data access is corrected. Do not interpret a load error as an empty library.",
        "Start with Folder grouping, the page default. Use Search views, folders, tags, report types, creators to match the view name, report-family label, scope, Sales/Operational kind, folder, category, tags, or creator name. Search and filters are applied in the browser to the rows already loaded.",
        "Use All scopes, Company-wide, or Personal. Company-wide cards have a filled scope badge and are shared within the business under its access rules. Personal cards have an outline badge and belong to an individual creator. The filter changes visibility only; it does not change a view’s scope.",
        "Use All types, Sales, or Operations. Sales refers to saved Sales-report configurations. Operations refers to the supported operational families such as tax, payments, cash, gift cards, store credit, or team reporting. These controls do not change the report definition.",
        "Choose Flat to show one All Saved Views group. Choose Folder to group by the optional folder and place blank folders under Unfiled. Choose Category to group by the optional category, falling back to the report-family label when no category exists. Choose Type to group by the report-family label—not merely into Sales versus Operations.",
        "Read each card before opening it. The card shows Company-wide or Personal, report-family label, view name, Sales or Operational kind, optional folder/category/tags, last updated date, and creator display name. Unknown user means the creator profile name was not returned; it does not prove the view is system-owned.",
        "Choose the card, chevron, or Open report action to run it. CentriPOS adds the savedView ID to the normalized saved query and routes Sales views to their saved path or Report Center, while Operational views open Report Center with their report family.",
        "On the opened report, verify the saved-view name/ID, report family, date logic, locations, users, measures, groupings, filters, exclusions, and current permission scope before relying on the result. The displayed rows and totals are recalculated current data, not a snapshot from the card’s Updated date.",
        "Return to the originating Sales or Operational report workflow to change analytical configuration. Saved Views edits only library organization; it has no controls here for dates, locations, measures, breakdowns, columns, sorting, report name, or Personal/Company-wide scope.",
        "A Pencil appears only when this screen considers the view manageable: the signed-in profile created a Personal view, or the account has owner permission for a Company-wide view. No pencil means the view can be opened but not organized or removed by this profile.",
        "Choose Pencil to open Organize report view. Enter an optional Folder and Category. Enter Tags as a comma-separated list; surrounding spaces are trimmed and blank entries are removed, but duplicate tags are not visibly deduplicated by this form. Empty Folder/Category stores null, and no tags stores an empty list.",
        "Choose Save library details once and wait for Saved view details updated. This changes only folder, category, tags, updated-by metadata, and the row’s updated timestamp. Reopen the editor and card to confirm organization and attribution.",
        "Choose Remove view only when the exact Personal or Company-wide configuration should leave the active library. The current screen has no confirmation dialog: clicking it immediately submits a soft removal by setting is_active false. It does not delete report transaction data, but there is no restore control on this page.",
        "After removal, wait for Report view removed and confirm the card disappears from All scopes and All types. If the wrong shared view was removed, stop and contact an authorized administrator; do not recreate a similarly named view without first understanding its original configuration and audience.",
        "When No report views found appears, clear Search, return to All scopes and All types, and check Flat grouping. If it remains, the tenant has no active view returned by either source. Create and save a controlled view from Report Center, then return here to organize it.",
        "No screenshot is published for this guide. The Amelia Grant Harbor & Hearth capture attempt ended on the real Couldn’t load Saved Views error state, so it was rejected rather than presented as a working screen or replaced with another page."
      ],
      "controls": [
        {
          "name": "Bookmark icon",
          "description": "Exact Reports navigation and page icon for Saved Views."
        },
        {
          "name": "Loading Saved Views",
          "description": "Both active Sales and Operational view sources are still loading."
        },
        {
          "name": "Couldn’t load Saved Views",
          "description": "A real query error, not an empty result; the screen prints the returned message."
        },
        {
          "name": "Search views, folders, tags, report types, creators",
          "description": "Client-side search across name, family, scope, kind, organization, tags, and creator."
        },
        {
          "name": "All scopes",
          "description": "Shows all loaded views visible to the signed-in profile."
        },
        {
          "name": "Company-wide",
          "description": "Filters to shared tenant views."
        },
        {
          "name": "Personal",
          "description": "Filters to individual-profile views."
        },
        {
          "name": "All types",
          "description": "Shows Sales and Operational views."
        },
        {
          "name": "Sales",
          "description": "Filters to the Sales-report view table."
        },
        {
          "name": "Operations",
          "description": "Filters to operational report-family views."
        },
        {
          "name": "Flat",
          "description": "One All Saved Views group."
        },
        {
          "name": "Folder",
          "description": "Optional folder groups with blank folders under Unfiled."
        },
        {
          "name": "Category",
          "description": "Optional category groups with report-family fallback."
        },
        {
          "name": "Type",
          "description": "Groups by report-family label, not simply Sales/Operations."
        },
        {
          "name": "Saved-view card",
          "description": "Scope, family, name, kind, optional organization, tags, updated date, and creator."
        },
        {
          "name": "Updated date",
          "description": "Last row update, including library-detail changes; not the date of a preserved report snapshot."
        },
        {
          "name": "Chevron / Open report",
          "description": "Runs the normalized saved query with savedView ID against current data and permissions."
        },
        {
          "name": "Pencil",
          "description": "Shown for creator-owned Personal views or owner-manageable Company-wide views."
        },
        {
          "name": "Organize report view",
          "description": "Edits folder, category, and comma-separated tags only."
        },
        {
          "name": "Save library details",
          "description": "Updates organization metadata and attribution; it does not edit analytical report configuration."
        },
        {
          "name": "Remove view",
          "description": "Immediate soft removal with no confirmation dialog and no restore control on this screen."
        },
        {
          "name": "No report views found",
          "description": "Completed empty result for current search/filters or no active views."
        },
        {
          "name": "Current data",
          "description": "Opening the view reruns its configuration; the library does not store old totals or rows."
        },
        {
          "name": "No substituted screenshot",
          "description": "The real Harbor & Hearth screen ended in a load-error state, so no image is published for this working-state guide."
        }
      ],
      "expectedResult": "The intended active Sales or Operational view opens for the correct tenant and current permissions with its normalized saved configuration; library folder, category, and tags are correct, current data is not mistaken for a snapshot, and any removal affects only the exact authorized view.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "market-intelligence",
      "url": "https://platform.getcentri.com/centripos/market-intelligence",
      "title": "Use Market Intelligence",
      "summary": "Compare the selected location’s real 18-month customer and receipt reach with Census ZIP/ZCTA demographics, cached Google Places competition, mapped ZIP centroids, conversion gaps, and saved growth-plan candidates.",
      "collection": {
        "id": "reports",
        "title": "Dashboard & reports"
      },
      "section": "Intelligence",
      "introduction": "Reports → Market Intelligence uses the Compass icon. The current screen is location-specific; it does not contain the older Network scope, arbitrary reporting-period, comparison-period, Today’s Market Brief, Do next, or Watch list controls. It reads up to 10,000 sales from the selected location’s latest 18 months and customer details for at most the first 1,000 distinct attached customer IDs. Public demographics, competition counts, map positions, fit scores, and local Ask Centri answers are estimates derived from the loaded evidence—not CentriPOS ledger totals or guaranteed expansion outcomes.",
      "beforeYouBegin": "Set the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.",
      "steps": [
        "Open Reports → Market Intelligence beside the Compass icon. The page heading is Customer reach, surrounding market, and expansion fit. Confirm the active CentriPOS business, then choose one active Location. There is no All locations or network-wide option on this screen.",
        "Choose Business type. This sector/niche lens changes like-business competition searches, prompts, score interpretation, and labels. It does not rewrite product categories or the tenant’s legal industry classification. Reconfirm it before comparing markets.",
        "Understand the fixed source window. Sales analyzed uses up to 10,000 tenant sales created during the last 18 months at the selected location. Known customers counts sales with attached customer records. The customer lookup requests at most the first 1,000 distinct attached customer IDs, so a high-volume location can have incomplete address enrichment even when more sales were loaded.",
        "Read the four top metrics together. Sales analyzed is the loaded sale count. Known customers is attached-customer coverage. Demographic-ready is the percentage/count of known customers with ZIP or street-address evidence. Revenue mapped is revenue available to the active customer/ZIP profile; it is not necessarily the location’s audited net sales total.",
        "Use the five tabs: Command center, Active reach, Surrounding market, Market map, and Expansion finder. Changing tabs does not change the location, business type, ACS year, candidate ZIP input, or already loaded evidence during the mounted session.",
        "Choose ACS year · ZCTA. ZCTA means Census ZIP Code Tabulation Area—a ZIP-like statistical geography, not a postal delivery boundary. The screen uses ACS five-year estimates because they are the stable small-area Census product. Choose Refresh Census to force a new demographic refresh for the store ZIP, up to five strongest customer ZIPs, and comma-separated candidate ZIPs. Cached results otherwise remain fresh for 15 minutes in the client query.",
        "On Command center, read Data readiness, Market fit, and Expansion signal as model scores from the current evidence. Data readiness asks whether address coverage can support the comparison. Market fit compares the store market with the strongest customer seed. Expansion signal reflects the best ranked candidate. A dash means the required evidence is not available.",
        "Review up to five Recommended operator moves. A high-priority badge reflects the local command-center rules, not an assigned task or guaranteed revenue action. Use ZIP opportunity overlay to compare up to six strongest customer ZIPs, mapped revenue share, population, and median household income.",
        "Use Ask Centri market workbench to type or choose a prompt about revenue ZIPs, conversion gaps, competition, expansion, or readiness. The answer and Evidence list are generated locally from the current loaded snapshot. Ask Centri active means the plan is entitled and the evidence packet is Gemini-ready; this component still displays the deterministic local answerer until governed routing/metering is connected.",
        "On Active reach, review Revenue by active customer ZIP, Highest-value ZIPs, and ZIP conversion gaps. A sale ZIP is resolved from customer ZIP, customer address/street address, delivery address, then customer display contact. Completed includes completed, bill-to-account, layaway-completed, and on-account statuses; parked_abandoned is abandoned; draft, parked, posted, and saved are saved; other statuses are excluded from the conversion-gap buckets.",
        "Read a positive ZIP conversion gap as mapped saved plus abandoned opportunities outnumbering completed sales in that ZIP. Open opportunity value uses sale subtotal when present, otherwise total. This is a demand/follow-up signal, not proof those opportunities are recoverable or that completion attribution is error-free.",
        "On Surrounding market, inspect Store ZIP baseline: population, median household income, age 25–44, bachelor-or-higher, no-vehicle households, median age, households with children, owner occupancy, and supported race/ethnicity estimates. If the location address has no ZIP, add a correct location ZIP before expecting a store baseline.",
        "Treat ACS figures as public survey estimates with source year, sampling uncertainty, and ZCTA boundaries. Do not use a demographic or race/ethnicity percentage to make discriminatory customer, credit, pricing, employment, housing, or service decisions. Use aggregated planning and accessibility context with qualified review.",
        "Review the local comparison and Competition lens. Like-business counts come from cached Google Places searches for the current niche. A failed competition refresh or zero count can mean provider/key/coverage limits rather than no competitors. Competition data is cached for 15 minutes in the client query.",
        "In Surrounding area ZIP checker, enter five-digit ZIPs separated by commas. The parser keeps unique ZIPs and combines them with the store ZIP and up to five strongest customer ZIPs. Choose Refresh ZIP data to force Census, competition, and map-coordinate refresh together. Review each comparison row’s customer reach, demographics, competition, and saved state.",
        "On Market map, understand the visual: it is a custom relative ZIP-centroid plot, not a street map or drive-time/territory boundary. Blue identifies the store ZIP, dark identifies customer/candidate ZIPs, and green identifies saved growth-plan ZIPs. Minus/Plus changes visual zoom from 80% through 240%; it does not change analysis radius or source queries.",
        "Choose Refresh map to force ZIP centroid refresh. When coordinates cannot load, the screen points to the platform Google Maps/Places key. Select a pin to inspect mapped revenue, customers, population, like-business count, median household income, and age 25–44. Missing values show absence of loaded evidence, not zero.",
        "Choose Save on a selected ZIP to upsert a location-specific growth-plan watchlist record. The store ZIP starts at priority 5; other new ZIPs receive decreasing priorities based on current list length, no lower than 1. Choosing Saved deletes that bookmark immediately. There is no confirmation dialog, note/status editor, or undo control on this screen.",
        "Use Growth plan trajectory to open saved ZIPs in stored priority/created order and review current enriched evidence. Saving a ZIP does not launch a campaign, create a task, approve a site, or preserve the demographic/competition snapshot; the row is re-enriched from current loaded data.",
        "On Expansion finder, enter candidate ZIPs or choose up to five Recommended ZIP seeds from the store and strongest customer markets. Statewide scan is described as future behavior; only explicitly entered ZIPs are ranked today.",
        "Read Candidate market ranking as a relative fit score. It compares each candidate’s Census population, median household income, education, age 25–44, and current like-business count against the strongest active customer ZIP (or store baseline) using the selected category model. Review Signals and Risks; Neutral fit means no modeled positive/negative flags, not that the site is safe or profitable.",
        "Before acting, verify the location address, customer ZIP/address capture, sale statuses, 18-month and row caps, selected ACS year, Census refresh state, business type, Google Places freshness, map coordinates, strongest seed, and explicitly entered candidates. Validate any expansion, marketing, accessibility, or investment decision with current local research, costs, legal review, site visits, and independently sourced market data.",
        "The published screenshot is the real Amelia Grant Harbor & Hearth /dashboard/market-intelligence screen at 1440×900 in a fully loaded state. It is attached only to this exact guide; no customer-level address, private message, credential, or state-changing action was captured."
      ],
      "controls": [
        {
          "name": "Compass icon",
          "description": "Exact CentriPOS Reports navigation icon for Market Intelligence."
        },
        {
          "name": "Location",
          "description": "One active location; there is no All/network scope in the current screen."
        },
        {
          "name": "Business type",
          "description": "Sector/niche lens for competition, prompts, scoring, and labels."
        },
        {
          "name": "Sales analyzed",
          "description": "Up to 10,000 selected-location sales created in the latest fixed 18 months."
        },
        {
          "name": "Known customers",
          "description": "Loaded sales with an attached customer ID; customer enrichment is limited to the first 1,000 distinct IDs."
        },
        {
          "name": "Demographic-ready",
          "description": "Share and count of known customers with ZIP or street-address evidence."
        },
        {
          "name": "Revenue mapped",
          "description": "Revenue represented in the active customer/ZIP profile; not an audited location net-sales KPI."
        },
        {
          "name": "Command center",
          "description": "Readiness, market-fit, expansion-score, recommended moves, ZIP overlay, and local Ask Centri evidence."
        },
        {
          "name": "Active reach",
          "description": "Customer-ZIP revenue and completed-versus-saved/abandoned conversion evidence."
        },
        {
          "name": "Surrounding market",
          "description": "Store/candidate Census baselines, local comparison, competition, and ZIP checker."
        },
        {
          "name": "Market map",
          "description": "Relative cached ZIP-centroid plot plus location growth-plan bookmarks."
        },
        {
          "name": "Expansion finder",
          "description": "Explicit candidate-ZIP scoring against the strongest active customer/store profile."
        },
        {
          "name": "ACS year · ZCTA",
          "description": "Selected ACS five-year source year and Census ZIP-like statistical geography."
        },
        {
          "name": "Refresh Census",
          "description": "Forces demographic refresh for the current ZIP evidence set."
        },
        {
          "name": "Data readiness",
          "description": "Model score for address/evidence sufficiency."
        },
        {
          "name": "Market fit",
          "description": "Modeled similarity between store-market and strongest active-customer demographic seed."
        },
        {
          "name": "Expansion signal",
          "description": "Modeled strength of the top explicitly entered candidate."
        },
        {
          "name": "Recommended operator moves",
          "description": "Up to five rule-generated suggestions; not assigned tasks or guaranteed impact."
        },
        {
          "name": "Ask Centri market workbench",
          "description": "Deterministic local answer/evidence from the loaded snapshot; entitlement badge describes governed AI readiness."
        },
        {
          "name": "ZIP resolution order",
          "description": "Customer ZIP → customer address → customer street address → delivery address → customer display contact."
        },
        {
          "name": "Completed conversion bucket",
          "description": "completed, bill_to_account, layaway_completed, and on_account."
        },
        {
          "name": "Abandoned conversion bucket",
          "description": "parked_abandoned."
        },
        {
          "name": "Saved conversion bucket",
          "description": "draft, parked, posted, and saved."
        },
        {
          "name": "ZIP conversion gap",
          "description": "Saved + abandoned count minus completed count for mapped eligible statuses."
        },
        {
          "name": "Store ZIP baseline",
          "description": "ACS/ZCTA demographic estimates for the ZIP parsed from the selected location address."
        },
        {
          "name": "Competition lens",
          "description": "Cached Google Places like-business count for the selected niche and ZIP."
        },
        {
          "name": "ZIPs to compare / Candidate ZIPs",
          "description": "Comma-separated unique five-digit ZIP input."
        },
        {
          "name": "Refresh ZIP data",
          "description": "Forces Census, competition, and map-coordinate refresh."
        },
        {
          "name": "ZIP target map",
          "description": "Relative centroid visualization; not street geography, radius, drive time, or territory."
        },
        {
          "name": "Map − / +",
          "description": "Visual zoom only, from 80% to 240%."
        },
        {
          "name": "Refresh map",
          "description": "Forces ZIP centroid/provider refresh."
        },
        {
          "name": "Save / Saved",
          "description": "Immediate location-specific growth-plan watchlist upsert or delete with no confirmation."
        },
        {
          "name": "Growth plan trajectory",
          "description": "Saved ZIP list re-enriched from current evidence; not a frozen plan snapshot or campaign."
        },
        {
          "name": "Candidate market score",
          "description": "Relative category-model fit using public demographics and current competition count."
        },
        {
          "name": "Signals / Risks / Neutral fit",
          "description": "Model explanations, not guarantees or approvals."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real fully loaded Amelia Grant Market Intelligence screen matched to /dashboard/market-intelligence."
        }
      ],
      "expectedResult": "The displayed market area, period, sources, benchmarks, and business comparisons match the intended location context and clearly distinguish estimates from CentriPOS transaction data.",
      "troubleshooting": [
        "Check the date range, timezone, locations, registers, statuses, and saved-view filters first.",
        "Refresh after the underlying transaction has finished posting.",
        "Open the source sale, payment, movement, or closure when a total needs transaction-level proof."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/dashboard-market-intelligence.png",
        "alt": "Real Harbor & Hearth Market Intelligence screen showing location and business-type selectors, customer-reach metrics, ACS ZIP baseline status, and the five analysis tabs in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "payment-types",
      "url": "https://platform.getcentri.com/centripos/payment-types",
      "title": "Understand and safely use payment types",
      "summary": "Know which checkout methods are integrated processor actions versus manual records, why a method appears or is hidden, how partial/split amounts and references work, and what evidence proves a customer payment actually succeeded.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Payments",
      "introduction": "At checkout, CentriPOS loads enabled payment types for the tenant, keeps only those supporting the POS channel and active location, and then separates integrated actions from eligible manual methods. A payment type label alone does not prove money moved through a processor. Use the separate Configure Payment Types guide for the exact Harbor & Hearth Admin screenshot.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Open Pay only after confirming the cart total, customer, tax, fulfillment, and register session. The Pay screen shows Total, Paid, Balance, any Payments Applied, and Amount to collect.",
        "Review the payment choices actually shown. An enabled type with no channel restriction or with POS enabled can appear; a location-unscoped type appears everywhere, while a scoped type appears only at an assigned active location. Disabled, WEB-only, other-location, or hidden-manual types do not belong in the manual list.",
        "Distinguish integrated choices from manual records. CentriPay Cloud sends a card-present request to the resolved active terminal; Tap to Pay uses the supported device plugin; Card on File charges an authorized vaulted card. A custom/manual type only records the amount under that tender unless its own connected workflow has already collected the money.",
        "Do not use a manual “CentriPay Terminal,” “NMI Gateway,” financing, gift, or card label as a substitute for running its integrated processor action. Manual integrated-tender options are intended only when administrators deliberately expose them for recording an already-completed outside transaction.",
        "Set Amount to collect before choosing a method when splitting payment. It defaults to the full remaining balance, offers Full and sometimes Half shortcuts, and caps an entered payment at the remaining balance. Selecting a method without a reference step applies that amount immediately; a positive remaining balance returns you to method selection.",
        "For Cash, enter the amount physically tendered or use a configured denomination preset. CentriPOS records the applied cash amount, tendered amount, and change. If this cash payment finishes the balance, the configured Cash payment type can round the remaining cash amount and store the separate cash rounding adjustment/discount on the receipt.",
        "For a manual method configured to collect a payment reference, enter the required searchable ID before applying it. Check always collects a reference by default; the field label, placeholder, and help text can be customized. Verify a check number, money-order number, voucher ID, authorization, or gateway transaction ID against the source document.",
        "For CentriPay Cloud terminal, confirm the selected terminal and amount, send once, wake the PAX if needed, and wait for an approved processor response. CentriPOS records processor/terminal IDs, approval and response details, brand/last four, entry method, device, batch/merchant/invoice/receipt references, and timestamp when returned.",
        "If a terminal request remains pending, use the terminal recovery guide. Manual completion becomes available only after the delay and records a pending-processor-confirmation exception; it is not equivalent to a verified approval. Never send a second request merely because the first response is slow without checking terminal/processor state.",
        "For Card on File, verify the attached customer and exact vaulted card. CentriPay Cloud and NMI Gateway saved cards run different connected charge paths and record their processor reference; do not describe a manual card label as a vaulted charge.",
        "Review Payments Applied after every tender. Each row shows method and amount; integrated rows are protected from casual removal, while a nonintegrated manual allocation can be removed before completion. Confirm Paid and Balance recalculate correctly.",
        "When Balance reaches zero, CentriPOS completes the sale automatically through the payment workflow. Do not click or add another method after the receipt begins completing. If a balance remains, add another valid payment, choose an approved partial-balance outcome such as layaway or Charge to Account, or correct the existing allocation.",
        "After completion, open the receipt and verify payment method/type, applied amount, tendered/change, reference number, processor/terminal evidence for integrated payments, cash rounding, total paid, and zero or intended remaining balance. Reconcile processor/card activity separately from the CentriPOS record.",
        "Administrators manage definitions at Admin → Payment types. Integrated Payment Types report the service connection plus mapped reporting row; Custom Payment Types are manual methods. Changes to enabled state, POS/WEB channels, locations, manual-list visibility, reference collection, cash rounding, conceal totals, or gateway URL affect future checkout choices and require controlled testing."
      ],
      "controls": [
        {
          "name": "Total / Paid / Balance",
          "description": "Current payment allocation summary."
        },
        {
          "name": "Amount to collect",
          "description": "Draft amount capped at the remaining balance; defaults to full remaining."
        },
        {
          "name": "Full / Half",
          "description": "Convenience allocations for the current remaining balance."
        },
        {
          "name": "Payments Applied",
          "description": "Tender allocations already added to this checkout."
        },
        {
          "name": "Enabled",
          "description": "Payment definition must be active before it is queried at checkout."
        },
        {
          "name": "POS channel",
          "description": "Required explicitly when channels are restricted; no/empty channel list behaves as unrestricted."
        },
        {
          "name": "Location assignment",
          "description": "No location list means all active locations; an explicit list limits availability."
        },
        {
          "name": "Manual-list visibility",
          "description": "Noncash payment setting that can hide a reporting/import/integrated row from cashier selection."
        },
        {
          "name": "Integrated payment",
          "description": "Connected action that actually requests or charges through CentriPay Cloud, Tap to Pay, or a supported saved-card provider."
        },
        {
          "name": "Manual payment",
          "description": "Cashier-recorded tender allocation; it does not itself contact a processor."
        },
        {
          "name": "Cash",
          "description": "Records applied amount, amount tendered, change, and completing-payment rounding."
        },
        {
          "name": "Cash rounding",
          "description": "Configured increment/mode applied when cash finishes the current balance; the delta is retained on the receipt."
        },
        {
          "name": "Payment reference",
          "description": "Required or optional searchable external ID; Check forces reference collection."
        },
        {
          "name": "CentriPay Cloud",
          "description": "Integrated terminal path with payment intent, transaction polling, and processor response evidence."
        },
        {
          "name": "Tap to Pay",
          "description": "Device-plugin card-present action shown only when available."
        },
        {
          "name": "Card on File",
          "description": "Connected charge against the selected attached-customer vault card."
        },
        {
          "name": "Manual CentriPay/NMI method",
          "description": "Exception record for an already completed outside transaction when explicitly exposed; not a processor send."
        },
        {
          "name": "Split payment",
          "description": "Multiple positive allocations whose combined amount satisfies the balance."
        },
        {
          "name": "Integrated-row protection",
          "description": "Integrated allocations are not removed with the simple X used for manual allocations."
        },
        {
          "name": "Pending processor confirmation",
          "description": "Manual terminal exception state, not verified approval/settlement."
        },
        {
          "name": "Automatic completion",
          "description": "Sale completes when the newly applied allocations reduce the balance to zero."
        },
        {
          "name": "Processor reconciliation",
          "description": "Independent confirmation that the provider approved/settled the transaction represented in CentriPOS."
        },
        {
          "name": "No exact Pay screenshot",
          "description": "The approved Harbor & Hearth manifest rejected /register/sell as rejected-loading; the real admin screenshot remains only on Configure Payment Types."
        }
      ],
      "expectedResult": "Only payment types allowed for the current business, location, register, channel, and role appear, and each uses its configured processing behavior.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "centripay-overview",
      "url": "https://platform.getcentri.com/centripos/centripay-overview",
      "title": "Understand the Payanywhere Suite Overview",
      "summary": "Read tenant-wide payment volume, money movement, attention signals, recent activity, payment-source mix, batches, and deposits without mistaking the overview for settlement or register reconciliation.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Payments",
      "introduction": "The Overview requests connected business reporting across all locations for the last seven days, with a small recent-record count. It does not follow the location/register shown in the top context bar and has no date, location, refresh, export, or reconciliation controls of its own. Use Transactions and Reporting for supporting detail.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Open Payanywhere Suite → Overview, identified by the Zap icon. Confirm the active CentriPOS business; the overview is tenant-wide even when the top bar names a location and register. Do not assume those selectors scope these cards.",
        "Wait for Payments collected and Money movement to finish Loading…. The reporting query requests all configured locations, seven days, and up to eight recent reporting records. The screen keeps reporting data fresh for about one minute before a normal revisit may request it again.",
        "Read Payments collected as gross reporting volume plus transaction count for the seven-day response. Gross volume is not net funding: it can differ from deposits, refunds, fees, chargebacks, unsettled activity, and register totals. Choose the card to open Transactions.",
        "Read Money movement as the returned deposit total, with deposit and batch counts beneath it. It is not a single bank-deposit amount and does not prove that every batch funded. Choose the card to open Reporting and inspect the underlying records.",
        "Read All quiet or Needs attention carefully. The number is unread gateway alerts plus declined reporting transactions plus reporting-source errors. An unread-alert badge, when present, counts only unread stored alerts. A zero means none of those signals surfaced in the current data—not that processors, terminals, batches, deposits, receipts, or accounting are fully reconciled.",
        "Read Active batches today on the captured Harbor & Hearth screen (newer product code may label the equivalent card Open batches). It represents batches returned as open/pending or without a closed timestamp under the supported status rules. Choose the card to open Reporting before closeout decisions.",
        "Use the right-side message as an unread-notice shortcut. Everything looks quiet means no unread stored gateway alert. If it reports new notices, start with Alerts. This message does not include all declines or sync errors even though the broader Needs attention number does.",
        "Review Latest payment activity. When Payments Hub reporting returns transactions, the overview shows up to the first five recent rows from that response. Each row can show location, time, source, masked card brand/last four or authorization reference, amount, and status. Choose View all for Transactions.",
        "Understand the fallback: when business reporting returns no transactions, Latest payment activity can use up to eight locally stored NMI Gateway transactions instead. Those fallback rows are labeled CentriPay Gateway. A fallback row does not mean Payments Hub reporting, batches, deposits, or source totals are healthy.",
        "Read Payment mix by dollar volume, not only the bar length. Supported source families include Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, and unclassified Payments Hub activity. Choose Report for the full Reporting workspace. A missing/empty mix means the reporting response has not supplied usable source totals.",
        "Read Batches & deposits as three separate counts: Active today/Open, total returned Batches, and returned Deposits. These are counts in the current reporting response, not lifetime totals, bank statement totals, or register-closure counts.",
        "When a card or panel is zero/empty, distinguish a legitimate no-activity response from a reporting error. All quiet can still coexist with missing expected activity if a source failed to connect or deliver data. Open Reporting and check its errors, locations, environment, masked MID, source status, and record lists.",
        "For a payment discrepancy, trace the entire operational path: CentriPOS sale and payment row → selected register session → closure tender totals → processor transaction → processor batch → processor deposit → QuickBooks sync row when applicable. Label each amount and status by its source; do not force unrelated totals to match.",
        "For an expected payment absent from Latest activity, search Transactions using the approved processor-safe reference, receipt, location, approximate time, amount, and masked tender context. Do not retry a customer charge solely because it is absent from this overview. Check terminal/payment-intent status and processor evidence first.",
        "For an unexpected decline, alert, reporting error, open batch, or missing deposit, preserve the business, location, register, receipt/sale ID, safe processor transaction reference, amount, time, source/environment, batch/deposit reference, and displayed error. Never include full card data, CVV, security keys, API passwords, or raw webhook credentials.",
        "The article screenshot is the real Amelia Grant Harbor & Hearth capture at 1440 × 900. It shows the loaded zero-aggregate state: $0.00 collected, $0.00 money movement, All quiet 0, Active batches today 0, no recent activity, no payment mix, and zero batch/deposit counts. It contains no transaction, card, customer, batch, or deposit details."
      ],
      "controls": [
        {
          "name": "Zap navigation icon",
          "description": "Exact Overview icon used in Payanywhere Suite navigation."
        },
        {
          "name": "Tenant-wide scope",
          "description": "Overview reporting explicitly requests all locations; the top-bar location/register does not filter it."
        },
        {
          "name": "Seven-day window",
          "description": "Fixed overview reporting period for Payments collected and related response summaries."
        },
        {
          "name": "Recent-record count",
          "description": "Overview requests a small reporting sample (eight) and displays up to five reporting rows."
        },
        {
          "name": "Payments collected",
          "description": "Gross volume and transaction count from the business-reporting summary."
        },
        {
          "name": "Money movement",
          "description": "Returned deposit total plus deposit and batch counts."
        },
        {
          "name": "All quiet / Needs attention",
          "description": "Unread stored alerts + declined reporting transactions + reporting-source errors."
        },
        {
          "name": "Unread notice message",
          "description": "Counts unread gateway alerts only and points the user to Alerts."
        },
        {
          "name": "Active batches today / Open batches",
          "description": "Returned batches treated as open/pending or lacking a closed timestamp; inspect Reporting before acting."
        },
        {
          "name": "Latest payment activity",
          "description": "First five Payments Hub reporting transactions when available."
        },
        {
          "name": "NMI fallback",
          "description": "Up to eight local gateway transactions used only when reporting supplies no transaction rows."
        },
        {
          "name": "Location name",
          "description": "Reporting-row location; fallback rows use CentriPay Gateway rather than a store name."
        },
        {
          "name": "Source",
          "description": "Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, or Payments Hub classification."
        },
        {
          "name": "Masked tender detail",
          "description": "Card brand plus last four, authorization reference, or generic payment label; never full credentials."
        },
        {
          "name": "Payment mix",
          "description": "Reported dollar volume by payment-source classification."
        },
        {
          "name": "View all",
          "description": "Opens Payanywhere Suite Transactions."
        },
        {
          "name": "Report",
          "description": "Opens the full Reporting workspace."
        },
        {
          "name": "Batches & deposits",
          "description": "Counts of active/open batches, all returned batches, and returned deposits."
        },
        {
          "name": "Zero-value boundary",
          "description": "A rendered zero is only evidence about returned overview data, not full processor or accounting reconciliation."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant zero-aggregate overview with no sensitive payment records exposed."
        }
      ],
      "expectedResult": "The suite overview’s alerts, transactions, batches, deposits, and totals agree with the selected merchant and date scope and link to the relevant detail views.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/centripay-overview.png",
        "alt": "Harbor & Hearth Payanywhere Suite overview showing payments collected, money movement, alerts, batches, deposits, and recent activity in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "centripay-settings",
      "url": "https://platform.getcentri.com/centripos/centripay-settings",
      "title": "Configure Payanywhere Suite Payment Settings",
      "summary": "Safely configure location-scoped in-person processing, tenant or location-routed online checkout, gateway risk controls, reporting credentials, billing-link convenience fees, and register-specific overrides.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Payanywhere Suite",
      "introduction": "This is a restricted administrative surface containing merchant identifiers and secret-bearing controls. Never place a private key, API password, MID, developer key, webhook signing material, or full terminal identifier in screenshots, tickets, chat, email, public documentation, or CentriAI prompts. The approved Harbor & Hearth capture policy rejected this screen, so this guide intentionally has no screenshot. Work with the merchant account owner and an authorized CentriPOS administrator.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Go to Payanywhere Suite → Settings, identified by the Settings icon. Wait for Loading settings… to finish. Confirm the CentriPOS business first; then use each section’s own location/routing selector instead of assuming the top-bar register scopes it.",
        "Read the four cards before editing. In-Person Payments reports Ready or Needs Credentials; Online Payments can report Verified, Retest Needed, Saved, or Not Connected; Billing-Link Fees reports On/Off; Register Rules is labeled Register Level. Some Payments Connected means at least one online or in-person configuration exists—not that all channels or locations are ready.",
        "Create a change record before touching credentials: business, affected location/register/channel, current environment, current non-secret status, requested outcome, processor owner/approver, test plan, rollback plan, and maintenance window. Never copy existing masked/secret fields into the record.",
        "For In-Person Payments, choose the exact Location. Each location can have a different Payments Hub/Payanywhere merchant route, environment, MID, credentials, application-source header, public gateway key, webhook status, and terminal assignments.",
        "Choose Production only for approved live merchant credentials, Sandbox for test credentials and non-live transactions, or Beta / pilot only when the processor explicitly provisions it. Environment and credentials must belong together. Never test with a live customer card in a sandbox/pilot route.",
        "Enter or verify Display Name, MID, Developer Key, API Password, App Source Header, Gateway Public Key, and the branded webhook URL supplied by CentriPOS. A blank API Password on an existing record preserves the saved password; do not enter a placeholder. Public keys are not card data, but still treat merchant configuration as internal.",
        "Choose Save CentriPay™ Cloud only for the selected location. MID and Developer Key are required by the visible control; API Password is required for a new working connection even when the button state cannot prove it. Saving marks an approved branded webhook as approved or another nonempty webhook as pending approval.",
        "Review Selected location, Cloud config, and Paired terminals after save. Configured · webhook approved is configuration evidence, not proof of processor delivery. The reporting panel depends on this location record; an unconfigured location cannot contribute its Payanywhere reporting through this connection.",
        "Review Location Terminal Devices. A terminal can be available to the whole location or assigned to one register and can show Active/Inactive, device type, and account identifier. Use Open Location Terminals to manage pairing from the location record; saving merchant credentials does not pair a terminal.",
        "Tap to Pay on iPhone appears only in the native iPhone app. Save Environment, MID, Developer Key, and API Password for the location first. Activate Tap to Pay launches native enrollment; Check status reports eligibility, authentication, settings load, and environment; Setup info opens Apple/provider education when available. A successful enrollment is device/location evidence, not proof every register can accept a payment.",
        "Use Reset SI Details only as a controlled recovery/decommission action. Confirm the exact location in the browser warning. It clears saved Payanywhere/North credentials for that location and deactivates paired semi-integrated terminals while preserving historical payments. It is destructive operationally even though history remains; reconfiguration and re-pairing may be required.",
        "For Online Payments, treat North embedded checkout and NMI Gateway as separate routes. North can be stored at Universal tenant scope or for one selected settlement location. A missing, inactive, or Standby North route falls back to the current NMI flow where supported.",
        "For North Online, choose routing scope and location when applicable; enter Display Name, Checkout Mode, Checkout ID, Profile ID, private API key, and environment. Choose Standby only during configuration/certification. North-first routing can affect e-cart, online store, and Woo-style checkout only when the corresponding Use toggle is enabled.",
        "Configure North capabilities deliberately: Cards, ACH / Pay-by-Bank, Apple Pay / Google Pay, reusable-token default, and channel toggles are independent. The saved policy requires supported card-not-present authentication/fraud controls. Do not enable wallets, ACH, reusable tokens, or a channel until processor certification, customer consent, legal disclosure, and controlled tests are complete.",
        "Choose Save North Online to persist only the selected tenant/location North route; an entered private key is cleared from the visible field after success. Choose Check North Readiness only when Checkout ID, Profile ID, and a saved/new private key make the route ready. Readiness is not a completed charge or settlement test.",
        "For NMI Gateway (Collect.js), understand the two credentials: Security Key is private and stored encrypted; Tokenization Key is public and used client-side. When a private key is already saved, leave the field blank to keep it or enter a replacement. Changing either credential makes the prior Verified status stale until a new test succeeds.",
        "Choose Test Gateway Connection after entering the intended credentials. Verified and Last tested prove that authentication succeeded at that time. They do not prove e-cart, storefront, billing links, keyed entry, ACH, 3DS, refunds, webhooks, settlement, or every register override. Save Online Payment Settings after the intended test and review the resulting status.",
        "Configure Gateway Risk & Capture only under processor/risk approval. Auto-Capture captures rather than authorizes only; AVS requests address verification; Require CVV requires the security code for supported gateway card transactions; 3D Secure is a tenant-level gateway switch. When 3DS is off here, a register override cannot force it on.",
        "Treat Processing Rate and Per-Transaction Fee as manual reference values only. CentriPOS does not currently synchronize processor pricing into them, and in-person Payanywhere terminal pricing is not separately stored here. They do not add a customer surcharge or determine processor billing.",
        "Enable PaymentsHub Reporting Add-On only for an NMI Gateway merchant that has the approved CentriPay reporting MID. Environment, Developer Key, Auth Password, App Source, and fee-collection mode must match that reporting account. CentriPOS caches the returned account identity internally and keeps NMI deposits classified separately from Payanywhere deposits.",
        "For Billing-Link Fees, understand the narrow scope: the Credit Card and ACH / Bank toggles add percentage or flat convenience fees only to the public franchise billing-link flow. They do not configure terminal surcharge/edge pricing, e-cart fees, storefront fees, processor pricing, or ordinary register payments.",
        "Before Save Billing-Link Fees, confirm the screen finished loading the existing online gateway settings. This control uses the same tenant gateway-settings save payload as the Online Payments form, so avoid changing unrelated online fields in the same session. Enter a reviewed nonnegative percentage or flat value and verify legal/card-network disclosure rules.",
        "Open Register Rules for a read-only inventory. Review Total registers, Custom gateway / 3DS, and ACH enabled; filter by location or search register/location. Rows can show Custom gateway keys, 3DS forced on/off, ACH enabled, or Uses storefront defaults. These counts and badges are configuration indicators, not transaction-success evidence.",
        "Choose Edit register settings or Open Locations & Registers to change one register. Register-specific NMI keys, 3DS behavior, and ACH availability live on the register record. A register with no custom gateway/3DS and ACH off is counted as using storefront defaults. Tenant 3DS off remains a kill switch even if a register says forced on.",
        "Run a controlled test matrix after an approved save: each affected location/register; PAX or semi-integrated terminal; Tap to Pay iPhone; keyed card; ACH; e-cart; online store; Woo-style route; billing link; authorization/capture; AVS/CVV/3DS; approved and declined callbacks; receipt match; refund/void; batch; deposit; register closure; and reporting source classification. Use test credentials/data where appropriate.",
        "For a failed or misrouted payment, stop retries until checking the CentriPOS payment intent/transaction, processor portal, configured location/register route, environment, terminal assignment, gateway test state, webhook delivery, batch, and deposit. Preserve only safe references. Never switch to another tenant’s MID or credentials as a shortcut.",
        "The screenshot boundary is intentional: the Amelia Grant Harbor & Hearth manifest records this route as rejected-sensitive-credentials because it contains MID, developer key, API password, public key, webhook, terminal pairing, and destructive reset controls. No screenshot was retained, and this guide does not invent or expose one."
      ],
      "controls": [
        {
          "name": "Settings navigation icon",
          "description": "Exact Payanywhere Suite icon for Payment Settings."
        },
        {
          "name": "Some Payments Connected",
          "description": "At least one stored online or in-person configuration exists; not full readiness."
        },
        {
          "name": "In-Person Payments",
          "description": "Location-scoped Payments Hub/Payanywhere credentials, webhook, reporting eligibility, terminals, and Tap to Pay."
        },
        {
          "name": "Location",
          "description": "Explicit merchant-routing scope for in-person settings; independent from the top-bar context."
        },
        {
          "name": "Environment",
          "description": "Production, Sandbox, or Beta / pilot; must match the credential set."
        },
        {
          "name": "MID / Developer Key / API Password",
          "description": "Restricted merchant authentication values; never expose them."
        },
        {
          "name": "App Source Header",
          "description": "Processor-provided application identity used by semi-integrated flows."
        },
        {
          "name": "Gateway Public Key",
          "description": "Public tokenization/configuration key stored on the selected location."
        },
        {
          "name": "Webhook status",
          "description": "Approved, pending, or unconfigured configuration evidence; not delivery proof."
        },
        {
          "name": "Location Terminal Devices",
          "description": "Read-only summary with link to pairing in Locations & Registers."
        },
        {
          "name": "Tap to Pay on iPhone",
          "description": "Native-only enrollment/status/education surface using selected location credentials."
        },
        {
          "name": "Reset SI Details",
          "description": "Confirmed destructive location reset that clears credentials and deactivates paired SI terminals while preserving history."
        },
        {
          "name": "North routing scope",
          "description": "Universal tenant route or one selected settlement location."
        },
        {
          "name": "Standby",
          "description": "Saved North configuration that should not take first routing priority."
        },
        {
          "name": "North-first",
          "description": "Active priority route for explicitly enabled online channels."
        },
        {
          "name": "North readiness",
          "description": "Required route identifiers plus saved/new private key; not charge proof."
        },
        {
          "name": "NMI Security Key",
          "description": "Private encrypted credential; blank preserves an existing saved value."
        },
        {
          "name": "NMI Tokenization Key",
          "description": "Public Collect.js key used for client-side tokenization."
        },
        {
          "name": "Retest Needed",
          "description": "Previously verified credentials changed in the current form."
        },
        {
          "name": "Test Gateway Connection",
          "description": "Authentication check for the supplied NMI credentials."
        },
        {
          "name": "Auto-Capture",
          "description": "Capture immediately instead of authorization-only behavior."
        },
        {
          "name": "AVS / CVV / 3DS",
          "description": "Gateway card-not-present risk controls; tenant 3DS off blocks register forcing."
        },
        {
          "name": "PaymentsHub Reporting Add-On",
          "description": "Optional NMI reporting/deposit link for an approved reporting MID."
        },
        {
          "name": "Gateway Fee Reference",
          "description": "Manually entered processor-cost reference; not a customer fee."
        },
        {
          "name": "Billing-Link Fees",
          "description": "Franchise public billing-link convenience fees only."
        },
        {
          "name": "Save Billing-Link Fees",
          "description": "Uses the shared tenant gateway-settings payload, so unrelated online fields must remain unchanged."
        },
        {
          "name": "Register Rules",
          "description": "Read-only tenant inventory of register gateway/3DS/ACH overrides."
        },
        {
          "name": "Uses storefront defaults",
          "description": "No custom gateway keys, no explicit 3DS override, and ACH off for that register."
        },
        {
          "name": "No screenshot",
          "description": "Exact route intentionally rejected by the Harbor & Hearth safe-capture policy because secrets and destructive controls are present."
        }
      ],
      "expectedResult": "The intended merchant, location, terminal, and processing options report a healthy connection and a controlled payment follows the new mapping.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "transactions-refunds",
      "url": "https://platform.getcentri.com/centripos/transactions-refunds",
      "title": "Review payments, payment receipts, and card authorizations",
      "summary": "Filter configured payment reporting, open the matching payment and POS receipts, and use reviewed authorization capture or release controls only when available and authorized.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Payments",
      "introduction": "Payments / Transactions brings together configured transaction reporting and a separate Card authorizations section. A reported approval, pending transaction, authorization hold, captured payment and bank settlement are different states. The reporting rows provide receipt actions; a Refund or Void transaction type describes reported activity rather than an immediate refund/void button on that row.",
      "beforeYouBegin": "Confirm the business, configured location, store timezone, amount and safe processor/receipt reference. Financial changes require the appropriate role, enabled runtime and original payment evidence. Keep card data, private customer details and internal credentials out of support requests.",
      "steps": [
        "Open Money → Payments, or CentriPay → Transactions in the POS workspace. Confirm the intended business and the configured-location selection. These entry points share the current Transactions panel; separate reporting/deposit views and direct gateway activity can have their own coverage.",
        "Choose All configured locations or the exact configured location. The location choice affects transaction reporting and the Card authorizations section. It does not grant access to another business or prove that every location/provider has been configured.",
        "Review the date picker. Its default is Year to date. Choose the intended preset or custom period and verify the store timezone before comparing transaction dates with a register closure, processor report or bank deposit. The panel waits for a usable timezone and valid date bounds before loading reporting.",
        "Wait for loading to finish. Transactions could not load is an error, while No transactions were found for this period means the configured reporting response was empty for the selected period/location. Neither result proves that another source, provider or unreturned historical record has no activity.",
        "Use Search TXN ID, sale, name… to match the returned processor ID, invoice reference, sale ID, customer name, location name or card last four. Search is applied to returned rows in the browser; it does not search amounts, authorization codes, arbitrary receipt notes or unloaded transaction history.",
        "Choose All statuses, Approved, Declined or Pending and All types, Sale, Refund, Void or Auth. Read Showing X of Y transactions returned for this period. The panel requests a bounded reporting response with count 500; client filters cannot find rows the service did not return. Narrow the period or location when investigating a missing record.",
        "Read the date/time, type, location/customer, masked card/funding detail, amount, status, payment-receipt action, POS receipt and transaction ID. The phone layout presents the same returned rows as cards. A blank card field or missing POS link is an information gap, not proof that no payment occurred.",
        "Open the POS receipt link when present and compare the exact sale/customer, payment amount/reference, original register session and invoice/return state. Keep payment reporting and receipt history distinct: a processor-only transaction may need investigation before it can be tied to a POS sale.",
        "Choose Payment receipt when offered to preview the receipt for that exact processor transaction. Review its merchant, amount, status and reference before sharing. This is the payment receipt, which can differ from the merchandise/tax/fulfillment detail on the POS receipt.",
        "Use the payment-receipt Print control only after checking the intended document and printer destination. Printing re-reads the transaction so a recent refund can be reflected. A printed receipt is a document copy, not confirmation of bank settlement.",
        "To email that payment receipt, enter the one intended Email receipt to address, review it and choose Email receipt once. This compact action uses a server-built receipt and the configured sending service; it is separate from the full POS receipt email composer. If delivery is uncertain, retain the original context and check available communication evidence before starting another send.",
        "For a product return, partial refund, exchange, inventory/tax adjustment or correction to a completed payment, open the originating POS receipt and use its eligible return or original-payment controls. Do not follow older instructions to click an immediate full-amount Refund or Void button in this reporting table; those buttons are not part of the current Transactions rows.",
        "Read Card authorizations separately when that section appears. Authorized · unpaid means funds were reserved, not collected. Capture in progress, Release in progress, Captured, Released and Review required describe different lifecycle states. Report date/status/type/text filters do not filter this separate authorization list; use its location scope and Refresh.",
        "Before Capture payment, confirm the exact receipt, held amount, customer authorization and capture deadline. The action captures the full retained hold amount shown here; this compact panel has no partial-capture amount editor. Capture before is a maximum workflow window, and the issuing bank may release funds earlier.",
        "Before Release authorization, confirm that the original hold should be released without collecting payment. Review the displayed capture/release question, then choose Confirm capture or Confirm release once. Use Cancel to leave the review without dispatching the action. An enabled button still requires the backend to accept the original payment scope, role and lifecycle.",
        "If the action is pending or its outcome is uncertain, use Check saved result for the retained original action. Do not start the opposite action, open another tab to bypass the saved attempt, or take a second payment. If the browser cannot retain the action, stop before submission and follow the message. A declined or unresolved action needs review of the original authorization.",
        "Some explicitly enabled accounts have a checkout-hold recovery panel under Alerts. It is not a general action in the transaction rows. An expired checkout window can still retain a payment hold. Inspect the original processor outcome and follow the separately authorized recovery procedure; inspection alone does not release a hold, collect money or refund a payment.",
        "After a confirmed capture, release, refund or other authorized financial action, reopen the same payment and POS receipt. Reconcile the actual processor outcome, receipt/invoice balance, register/closure evidence, batch/deposit, bank settlement and accounting state as applicable. A success message or changed reporting row does not establish every downstream result. Escalate uncertainty with safe references before another financial action."
      ],
      "controls": [
        {
          "name": "All configured locations",
          "description": "Selects configured reporting scope; the same location is passed to Card authorizations."
        },
        {
          "name": "Date range / store timezone",
          "description": "Default Year to date, with presets/custom bounds interpreted for the selected business location."
        },
        {
          "name": "Search TXN ID, sale, name…",
          "description": "Client-side match across returned processor ID, invoice/sale reference, customer/location name and last four."
        },
        {
          "name": "Status / Type",
          "description": "Approved, Declined, Pending and Sale, Refund, Void, Auth, plus All choices."
        },
        {
          "name": "Showing X of Y",
          "description": "Filtered count versus returned reporting rows, not a complete unlimited ledger."
        },
        {
          "name": "Payment receipt",
          "description": "Processor-transaction receipt preview, print and one-recipient email when an exact reference is available."
        },
        {
          "name": "POS receipt",
          "description": "Linked CentriPOS sale context when the report supplies a sale ID."
        },
        {
          "name": "Card authorizations",
          "description": "Separate held-funds lifecycle list, scoped by location rather than report date/search filters."
        },
        {
          "name": "Capture payment / Release authorization",
          "description": "Reviewed full-hold financial action, offered only when the returned capability allows it."
        },
        {
          "name": "Confirm capture / Confirm release / Cancel",
          "description": "Explicit review before dispatching a capture/release; cancel leaves the review."
        },
        {
          "name": "Check saved result",
          "description": "Checks the retained original action after pending or uncertain outcomes."
        },
        {
          "name": "Capture before",
          "description": "Latest supported capture window; the issuing bank may release earlier."
        },
        {
          "name": "Alerts checkout holds",
          "description": "Separately gated recovery surface available only to explicit rollout accounts; not a universal Transactions tool."
        },
        {
          "name": "Return/refund boundary",
          "description": "Use the originating receipt’s authorized return/payment workflow rather than treating a reported type badge as an action."
        }
      ],
      "expectedResult": "The intended reported transaction is traced to its payment receipt and linked POS receipt when available. Any authorization action has the reviewed original scope and a confirmed result, while settlement, receipt balance and accounting outcomes are checked separately without duplicate payment attempts.",
      "troubleshooting": [
        "For a missing payment, check business, configured location, store timezone, date range and active client filters. Narrow the scope before concluding that the payment is absent; investigate another source separately when needed.",
        "If reporting cannot load or the authorization runtime is unavailable, preserve the error and ask authorized support to inspect configuration. Do not change a provider, tenant route or permission to bypass the failure.",
        "After an uncertain capture, release or payment, keep the original attempt and use its saved-result path. Do not create an offsetting charge, new payment, new refund or replacement invoice without reconciliation.",
        "For support, provide the safe transaction/receipt reference, amount, time/timezone, visible state and exact action/message. Redact private customer and payment data; no transaction screenshot is published by this guide."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "centripay-reporting",
      "url": "https://platform.getcentri.com/centripos/centripay-reporting",
      "title": "Use CentriPay Reporting",
      "summary": "Follow supported payment activity from processor or gateway records through CentriPOS receipts, settlement batches, deposits, monthly summaries, and matched register closures without confusing one source for another.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "CentriPay",
      "introduction": "CentriPay → Reporting uses the Bar Chart 3 icon. The screen requests at most 500 cloud reporting records and separately loads up to 500 local NMI gateway records. Its numbers are operational reporting evidence, not a bank statement: processor time, sale time, register-session scope, batch close, estimated deposit date, and bank posting can all differ.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Go to CentriPay → Reporting using the Bar Chart 3 icon. Only locations with a saved and tested Payanywhere reporting connection are included. If No configured CentriPay reporting locations appears, finish and test the location connection before interpreting the empty page.",
        "Choose All configured locations or one location, then apply a preset or custom date range. Choose Refresh to rerun the reporting request. Refresh is not a bank-posting confirmation and does not change a register closure or accounting record.",
        "Read the four headline tiles independently. Cloud gross is cloud processor volume/count; Deposited is the synced deposit amount/count; Batches is the returned batch amount/count; Gateway is approved local NMI volume while its count includes every local gateway record in range. Do not add these tiles together because they overlap different stages and sources.",
        "Use Latest deposit and Top location as orientation only. Location performance ranks by net payment volume and visibly renders the first six configured locations, showing environment, masked MID, transaction count, and approval rate. A location below the first six is still in the selected reporting result.",
        "Review Payment health. Approved and Declined come from the processor summary. Refunds counts cloud transaction types containing refund. Confirm the underlying rows before using these counts for reconciliation or coaching.",
        "Read Settlement path as a guide—Payments → Receipts → Batches → Deposits—not proof that every step is linked. Receipts says Linked when POS sale exists. Open batches treats open, pending, or not-closed/non-settled records as open and visibly lists only the first four.",
        "If Some configured locations could not be queried appears, record every named location, environment, masked MID, and message. The remaining tiles and tables are partial; do not reconcile an all-location period until the failed locations are resolved or explicitly excluded.",
        "Open Transactions. Source cards distinguish Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, and unclassified Payments Hub activity. The cloud table shows Date, Location, Source, Type, Card, Amount, Status, Auth, and Receipt / TXN; choose the receipt link only when a POS sale ID exists.",
        "Below the cloud table, NMI Gateway Local Activity shows local POS-stored gateway records in the date range and renders only the first ten. Its approved amounts feed the Gateway volume tile, while declined or other statuses remain in the record count. This local list is separate from the cloud transaction result.",
        "Open Deposits to review Type, Location, Estimated deposit date, Method, Register closures, Amount, and View. No match yet means the displayed deposit ID has no link in the loaded register-closure reconciliation evidence; it does not prove that funding or the register activity is absent.",
        "Choose View on a deposit. Confirm the location, estimated deposit date, clearing method, environment, masked MID, and amount. Matched register closures show their report/register/location, lifecycle, and processor net deposit. Batch information appears only when the matched closure evidence also contains related source batch IDs.",
        "Open Batches to review batch date, location, status, closed time, matched register closures, amount, and detail. The detail repeats environment and masked MID and links only those closures whose reconciliation evidence names the batch ID. A closed or settled batch is not by itself proof that its deposit posted to the bank.",
        "Open Statements. These rows are generated in CentriPOS by grouping the currently loaded deposits by effective-date month and batches by closed/opened month. They show period, unique represented locations, deposit count, batch count, and net deposited; they are not processor-issued statement documents and do not show fees.",
        "Choose Register closures to compare the selected reporting evidence with the exact session report. Closure matching reads recent reconciliation rows and associates only explicit source deposit IDs and source batch IDs. Trace a representative payment → POS receipt → batch → deposit → closure and keep location, environment, MID, date/time, amount, and identifiers aligned.",
        "For final cash settlement, fees, adjustments, chargebacks, or bank-posted timing, use the authorized processor and bank statements alongside CentriPOS. Capture the active filters and identifiers before escalating; never paste full card numbers, credentials, or an unmasked merchant ID into support notes.",
        "No screenshot is shown for this guide because the real Amelia Grant Harbor & Hearth /centripay/reporting capture ended in Reporting could not load: Unknown error. That rejected state is not replaced with another route, mockup, or invented image."
      ],
      "controls": [
        {
          "name": "Bar Chart 3 icon",
          "description": "Exact CentriPOS navigation icon for CentriPay → Reporting."
        },
        {
          "name": "Configured location",
          "description": "Location with a saved and tested Payanywhere reporting connection."
        },
        {
          "name": "Location filter",
          "description": "All configured locations or one returned configured location."
        },
        {
          "name": "Date range",
          "description": "Preset/custom processor query window; local gateway rows are filtered against the same from/to timestamps."
        },
        {
          "name": "Refresh",
          "description": "Reruns the reporting request; does not confirm bank posting or mutate closures."
        },
        {
          "name": "500-record boundary",
          "description": "The screen requests up to 500 cloud reporting records and loads up to 500 local gateway records."
        },
        {
          "name": "Cloud gross",
          "description": "Processor gross volume and processor transaction count for the returned scope."
        },
        {
          "name": "Deposited",
          "description": "Synced deposit total and count; not an independent bank-statement total."
        },
        {
          "name": "Batches",
          "description": "Returned batch amount and count."
        },
        {
          "name": "Gateway",
          "description": "Approved local NMI amount; displayed count includes all local gateway statuses in range."
        },
        {
          "name": "Latest deposit",
          "description": "Most recent returned deposit by effective date."
        },
        {
          "name": "Top location",
          "description": "Highest net-volume configured location in the returned result."
        },
        {
          "name": "Location performance",
          "description": "Ranks all returned configured locations but visibly renders the first six."
        },
        {
          "name": "Payment health",
          "description": "Processor Approved/Declined counts plus cloud transaction types containing refund."
        },
        {
          "name": "Settlement path",
          "description": "Orientation from Payments to Receipts to Batches to Deposits; not proof that each record is linked."
        },
        {
          "name": "Open batches",
          "description": "Open/pending or otherwise unclosed/unsettled batches; first four are shown in the card."
        },
        {
          "name": "Partial-query warning",
          "description": "Named configured locations failed; combined totals are incomplete."
        },
        {
          "name": "Source cards",
          "description": "Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, and unclassified Payments Hub counts/volume."
        },
        {
          "name": "Transactions table",
          "description": "Cloud reporting rows with time, location, source, type, card summary, amount, status, auth, and receipt/processor reference."
        },
        {
          "name": "Receipt link",
          "description": "Available only when a processor row carries a CentriPOS sale ID."
        },
        {
          "name": "NMI Gateway Local Activity",
          "description": "Separate local POS-stored list; first ten rows rendered."
        },
        {
          "name": "Deposits tab",
          "description": "Funding records with estimated date, method, amount, and reconciliation-derived links."
        },
        {
          "name": "Batches tab",
          "description": "Settlement groups with status, open/close timing, amount, and reconciliation-derived links."
        },
        {
          "name": "Statements tab",
          "description": "CentriPOS-generated monthly grouping of loaded deposits and batches—not a processor-issued statement."
        },
        {
          "name": "No match yet",
          "description": "No explicit reconciliation link for that displayed deposit/batch ID in the loaded evidence."
        },
        {
          "name": "Register closures",
          "description": "Opens closure reporting for session-level comparison."
        },
        {
          "name": "Rejected screenshot",
          "description": "The exact Harbor & Hearth route ended in an error, so no screenshot or substitute image is published."
        }
      ],
      "expectedResult": "The processor totals, fees, batches, deposits, refunds, and disputes reconcile with the selected merchant, date, and settlement scope.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "centripay-alerts",
      "url": "https://platform.getcentri.com/centripos/centripay-alerts",
      "title": "Review Payanywhere Suite Alerts",
      "summary": "Read processor chargeback and dispute notices surfaced inside CentriPOS, connect each notice to its supporting payment record, and mark it read without mistaking the queue for the processor’s dispute-resolution portal.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Alerts",
      "introduction": "The queue is tenant-wide, newest first, and limited to the latest 100 stored gateway alerts. It has no search, date/status filters, pagination, detail drawer, evidence upload, response, accept, contest, or resolve control. Mark Read changes only the CentriPOS unread flag; it does not acknowledge or resolve a dispute with the processor.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Go to Payanywhere Suite → Alerts. The Activity icon in navigation is the exact product icon for this section. Wait for Loading alerts… to finish before deciding the queue is empty.",
        "For each notice, read the alert-type badge and received timestamp first. Chargeback uses the destructive treatment; other alert types use the neutral treatment. New means the CentriPOS record has not been marked read—it is not the processor’s case status.",
        "Record the displayed Transaction reference. A missing reference appears as an em dash. Use the approved Payanywhere/NMI transaction, CentriPOS Transactions, receipt, and deposit records to establish the real payment chain before acting. Never use a customer name, card number, or guess as the transaction key.",
        "Read the amount only when it is shown. The UI suppresses zero or absent amounts. A displayed amount belongs to the notice payload and is not by itself proof of the remaining disputed balance, refunded amount, processor withdrawal, or accounting treatment.",
        "Read the optional reason text and reason code. Preserve the code exactly in an internal authorized case note, but use the processor’s current case record for its formal meaning, required evidence, response deadline, and final status. This screen does not display a deadline or processor case status.",
        "Open the supporting processor case outside this queue using the business’s authorized processor access. Confirm card-safe reference, transaction, amount, reason, response deadline, and whether the case is an inquiry, retrieval, dispute, or chargeback before preparing evidence.",
        "Follow the processor’s authorized evidence and response workflow. Do not upload evidence, accept liability, issue a refund, or tell a customer the case is resolved from this CentriPOS screen; those actions are not available here.",
        "Choose Mark Read only after the correct owner has recorded the next step or confirmed no action is needed. The button is available only on unread alerts, has no confirmation, and is not reversible from this page. After the update reloads, the New badge and Mark Read button disappear.",
        "Use the Payanywhere Suite overview’s Needs attention card as a signal, not a complete case count. That number combines unread alerts with declined-payment and reporting-sync issues; its alert badge counts unread gateway alerts from the same stored queue.",
        "If No alerts appears, the page loaded successfully but no stored gateway alerts were returned for the current tenant. It does not prove there are no disputes at the processor, no older records beyond the 100-row limit, or that webhook delivery is healthy.",
        "When an expected alert is missing, check the processor portal first, then ask an authorized administrator to verify that the NMI Gateway is sending supported POST callbacks to the tenant’s configured CentriPay webhook. Keep the callback URL, signing material, API keys, and Supabase details out of public notes and customer-facing links.",
        "For escalation, provide the CentriPOS tenant, safe transaction reference, processor case reference if available, notice received time, reason code, expected behavior, and whether the processor portal contains the case. Never include full card data, CVV, gateway credentials, or raw webhook secrets.",
        "The article screenshot is the real Amelia Grant Harbor & Hearth capture at 1440 × 900. It shows the fully loaded No alerts state and contains no dispute, chargeback, customer, or payment details."
      ],
      "controls": [
        {
          "name": "Activity navigation icon",
          "description": "Matches the Alerts icon used in the Payanywhere Suite navigation."
        },
        {
          "name": "Loading alerts…",
          "description": "The gateway-alert query is still in progress; do not interpret it as an empty queue."
        },
        {
          "name": "Alerts queue",
          "description": "Newest-first tenant records, capped at 100 by the current screen query."
        },
        {
          "name": "Alert type",
          "description": "Processor-supplied classification such as chargeback or dispute; the badge color is presentation, not case disposition."
        },
        {
          "name": "Received timestamp",
          "description": "When the gateway-alert row was created in CentriPOS."
        },
        {
          "name": "New badge",
          "description": "Unread inside CentriPOS only; not a processor status."
        },
        {
          "name": "Transaction reference",
          "description": "Processor-safe identifier used to find the supporting payment chain; may be absent."
        },
        {
          "name": "Amount",
          "description": "Optional positive amount from the notice payload, not independently a settlement or balance figure."
        },
        {
          "name": "Reason text",
          "description": "Optional human-readable processor context."
        },
        {
          "name": "Reason code",
          "description": "Optional processor code whose current interpretation should be confirmed in the processor case."
        },
        {
          "name": "Mark Read",
          "description": "Immediately sets is_read to true and refreshes the queue; it does not resolve or acknowledge the processor case."
        },
        {
          "name": "No alerts",
          "description": "Completed empty result for stored alerts returned to this tenant, not proof of a dispute-free processor account."
        },
        {
          "name": "100-record boundary",
          "description": "Older stored alerts may not appear because the query returns only the newest 100."
        },
        {
          "name": "Needs attention",
          "description": "Overview total combining unread alerts, declines, and reporting errors; not a pure dispute count."
        },
        {
          "name": "Webhook requirement",
          "description": "Supported NMI POST callbacks must reach the configured tenant CentriPay webhook for expected notices to be stored."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant empty-state capture with no sensitive payment or dispute information."
        }
      ],
      "expectedResult": "Each alert shows the intended merchant-safe reference, type, amount or deadline, status, and available action, and resolved alerts leave the active queue appropriately.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/centripay-alerts.png",
        "alt": "Harbor & Hearth Payanywhere Suite Alerts screen showing the fully rendered no-alerts state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "deposits",
      "url": "https://platform.getcentri.com/centripos/deposits",
      "title": "Understand deposits and funding",
      "summary": "Read the Deposits tab exactly as implemented, open one funding record safely, and follow only evidence-backed links to its register closures and batches.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "CentriPay",
      "introduction": "Deposits is a tab inside CentriPay → Reporting, not its own left-navigation route. The table represents returned processor funding records; it does not invent or itemize gross sales, interchange, fees, refunds, reserves, chargebacks, adjustments, or final bank-posted status. Estimated deposit date and Amount must be verified against the authorized processor and bank records.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Go to CentriPay → Reporting with the Bar Chart 3 icon. Choose the intended configured location and date range, then open Deposits. Keep the environment and masked MID aligned with the merchant account you intend to review.",
        "If No deposits found appears, first distinguish a loaded empty tab from No configured CentriPay reporting locations, a loading state, a partial-location warning, or Reporting could not load. An empty returned period is not proof that no bank funding occurred.",
        "Read each desktop row across Type, Location, Estimated deposit date, Method, Register closures, Amount, and Detail. On mobile the same record is condensed into location, date/method, closure link, amount, and View deposit detail.",
        "Treat Type as the processor status/classification normalized into the deposit record. Treat Estimated deposit date as the processor-provided effective date. Neither field alone confirms when the bank posted or made funds available.",
        "Read Register closures carefully. No match yet means no loaded reconciliation row explicitly names this deposit ID. A Report number link opens the exact register session; more than two matches are summarized with +N in the table, while the detail lists every loaded match.",
        "Choose View. The dialog title uses the amount and displays Location, Estimated deposit date, Clearing method, Environment, masked MID, and Amount. The full MID and reporting credentials are intentionally not displayed.",
        "In Matched register closures, open the exact report/register/location link. Read whether it is open or closed and compare its displayed processor Net deposit. A link exists because reconciliation evidence names the deposit ID—not because CentriPOS independently proved bank settlement.",
        "Review Batch information. Related batches appear only when a closure matched to this deposit also contains source batch IDs that match batches in the currently loaded reporting result. No matched batch records does not prove that the processor never formed a batch.",
        "If you arrived through a URL containing depositId, Reporting opens the Deposits tab and attempts to load that exact tenant deposit directly. Changing tabs removes depositId and batchId from the URL; closing the detail removes the depositId. Preserve the identifier separately before navigating away during an investigation.",
        "Trace the whole chain without changing source data: processor transaction → CentriPOS receipt/payment → processor batch → deposit → north deposit reconciliation → exact register session. Confirm tenant, location, environment, masked MID, timestamps, amounts, and identifiers at every step.",
        "Use the processor-issued statement for fee/adjustment detail and the bank statement for final posted amount/date. Do not label a difference as a POS error solely because gross sales, batch amount, deposit amount, counted tender, and bank posting differ.",
        "When escalating, include the safe deposit ID, location, environment, masked MID, selected range, estimated date, amount, linked report/batch IDs, and observed bank/processor result. Never share full card data, a full MID, API keys, or reporting passwords.",
        "No screenshot is published for this guide because the real Amelia Grant Harbor & Hearth Reporting route returned an error instead of a loaded Deposits tab. A different screen or fabricated funding table would be misleading."
      ],
      "controls": [
        {
          "name": "Deposits tab",
          "description": "Funding view inside CentriPay → Reporting; not a standalone left-navigation destination."
        },
        {
          "name": "Type",
          "description": "Processor status or classification normalized into the deposit record."
        },
        {
          "name": "Location",
          "description": "Configured merchant location returned with the deposit."
        },
        {
          "name": "Estimated deposit date",
          "description": "Processor-provided effective date; not guaranteed bank-posted date."
        },
        {
          "name": "Method / Clearing method",
          "description": "Funding or clearing descriptor returned for the record."
        },
        {
          "name": "Register closures",
          "description": "Links created from explicit source deposit IDs in loaded reconciliation evidence."
        },
        {
          "name": "No match yet",
          "description": "No current explicit deposit-to-closure reconciliation link; not proof of missing funding."
        },
        {
          "name": "+N",
          "description": "More matched closures exist than the first two table chips; open detail to see all loaded matches."
        },
        {
          "name": "Amount",
          "description": "Returned processor deposit amount; this table does not itemize gross, fees, refunds, or adjustments."
        },
        {
          "name": "View / View deposit detail",
          "description": "Opens the funding record’s safe detail dialog."
        },
        {
          "name": "Environment",
          "description": "Production, beta, or sandbox context of the reporting connection."
        },
        {
          "name": "Masked MID",
          "description": "Last four digits for merchant-account verification without exposing the full identifier."
        },
        {
          "name": "Matched register closures",
          "description": "Exact session links with lifecycle and processor net-deposit evidence."
        },
        {
          "name": "Batch information",
          "description": "Batches connected through a matched closure’s source batch IDs and present in the current result."
        },
        {
          "name": "Direct depositId link",
          "description": "Opens a tenant-scoped deposit detail and prepends it if it falls outside the base response."
        },
        {
          "name": "No deposits found",
          "description": "Loaded empty result for current connection/location/range, not proof of no bank funding."
        },
        {
          "name": "Processor statement",
          "description": "Source for processor-issued settlement, fee, and adjustment detail."
        },
        {
          "name": "Bank statement",
          "description": "Source for final bank-posted amount and timing."
        },
        {
          "name": "Rejected screenshot",
          "description": "Exact demo Reporting screen failed to load; no substitute or invented screenshot is used."
        }
      ],
      "expectedResult": "The deposit amount and funding date reconcile to its included batches, transactions, refunds, adjustments, and fees for the intended merchant account.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "terminal-management",
      "url": "https://platform.getcentri.com/centripos/terminal-management",
      "title": "Pair and Route Payment Terminals",
      "summary": "Pair a Payments Hub terminal identity to the correct CentriPOS location, optionally make it a register default, understand checkout routing priority, and safely reassign or remove the pairing.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Payment terminals",
      "introduction": "Do not add, reassign, or remove a terminal while any card-present request is sending, awaiting the customer, uncertain, or recovering. The Payments Hub terminal login is operational account information: never publish it in screenshots, CentriAI prompts, tickets, chat, or email. This screen stores a routing record; it does not provision the processor account, sign the physical device in, approve a webhook, or prove device connectivity.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Before changing anything, confirm the CentriPOS business, physical location, register, device label/serial kept in an approved internal inventory, Payments Hub merchant/environment, terminal login currently signed into the device, and whether a payment intent is active or uncertain. Stop if any payment is unresolved.",
        "Go to Admin → Locations & Registers, identified by the Building2 icon. Open the exact location record and find Terminal Devices. Do not use a similarly named showroom, warehouse, or test location.",
        "Read the CentriPay™ Cloud notice. Merchant credentials, environment, public gateway key, application-source header, and webhook approval are configured for this location under Payanywhere Suite → Settings → In-Person Payments. Pairing below only creates the device-routing record.",
        "Wait for the terminal list to finish loading. No terminal devices paired is a completed empty state for the selected location; it does not prove that no physical terminals or processor logins exist outside CentriPOS.",
        "Choose Add Terminal. Enter a stable, human-readable Terminal Name that staff can distinguish during checkout, such as Front Counter A920—not a customer name, password, or full secret identifier.",
        "Enter the exact Payments Hub terminal login currently signed into that physical device. This value targets the correct device when multiple terminals share one MID. Verify it directly through the approved processor/device administration path; do not infer it from an email address or copy another location’s login.",
        "Understand the uniqueness rule before saving: CentriPOS upserts terminal records by the current tenant plus terminal login. Reusing an existing login updates/moves that terminal record’s name, location, type, register assignment, provider, and active state instead of creating a second independent pairing. Search existing locations first and document an intentional move.",
        "Choose Device Type: PAX (A920 Pro, etc.), Ingenico, or Other. This classification describes the paired device; it does not detect the hardware, validate firmware, or enable capabilities automatically.",
        "Optionally choose Default Register from registers belonging to the opened location. Choose No default register to make the terminal a location-level candidate. A register assignment is a routing preference, not exclusive ownership, and a supported checkout can explicitly override it.",
        "Review Terminal Name, login, Device Type, location, and Default Register, then choose Add Terminal once. The button requires a nonblank name and login. Wait for Terminal saved and confirm one row appears with the intended name, uppercase device type, login, and Paired register when assigned.",
        "Understand checkout routing priority for active CentriPay Cloud terminals: an explicit terminal selected at checkout wins; otherwise CentriPOS chooses a terminal assigned directly to the active register; otherwise it chooses an unassigned active terminal at the active location; otherwise it reports that no active terminal is available. A requested provider also filters candidates.",
        "When more than one candidate exists at the same priority, the resolver prefers the most recently seen terminal when last-seen evidence exists, then terminal name alphabetically. Do not rely on that tie-break as store policy—give each register an unambiguous assignment or explicitly select the device.",
        "To change an existing route, use its register selector. Choosing a register immediately writes the new register ID; choosing Unassigned immediately clears it. There is no confirmation or success toast for this selector, so wait for the query refresh and re-open/verify the location before testing.",
        "After reassignment, confirm that the chosen register belongs to the same displayed location and that no other active terminal creates an ambiguous same-priority candidate. The list includes all records for the location, but checkout uses active records only.",
        "To remove a pairing, choose Trash and read Remove this terminal? Confirm only when the exact device should no longer be routable. Removal hard-deletes the CentriPOS terminal-device record and then reports Terminal removed. It does not sign out the physical device, revoke processor credentials, cancel a merchant account, undo payments, or erase processor history.",
        "If a terminal is being moved, prefer a controlled update/re-pair plan over deletion during business hours. Because the login is the upsert key, adding it at the new location may update the existing record. Verify both old and new location lists afterward and ensure the old register no longer resolves to it.",
        "Run a controlled card-present test from the intended business/location/register with no customer-sensitive data. Confirm the checkout shows the expected terminal or explicit selector, the request reaches only that device, the amount matches, the terminal completes once, and CentriPOS records the expected approved/declined status.",
        "Test the fallback deliberately when relevant: remove the explicit selection and confirm the register-assigned device wins; for an unassigned location device, confirm it is used only when no register default exists. Never create a live duplicate charge just to test fallback.",
        "Trace a successful test through payment intent → terminal transaction → sale payment/receipt → register session → closure tender totals → processor batch → deposit. Device routing success alone does not prove settlement, webhook delivery, or accounting reconciliation.",
        "For no-device, wrong-device, duplicate, or uncertain behavior, stop retries. Capture the business/location/register, safe receipt or payment-intent reference, amount/time, expected terminal name, selected/resolved routing scope, masked processor reference, and displayed status/error. Check assignment, active state, provider, location credentials/environment, device login/connectivity, webhook, and existing terminal request before acting.",
        "The approved Amelia Grant Harbor & Hearth manifest contains only the safe Locations & Registers overview; it does not contain a location edit view or Terminal Devices form. This guide intentionally publishes without substituting that overview or inventing a terminal screenshot, and it never exposes the demo’s terminal login."
      ],
      "controls": [
        {
          "name": "Building2 navigation icon",
          "description": "Exact Admin icon for Locations & Registers, where terminal routing records are managed."
        },
        {
          "name": "CentriPay™ Cloud notice",
          "description": "Separates location merchant/webhook configuration from terminal pairing."
        },
        {
          "name": "Terminal Devices",
          "description": "All paired terminal records for the opened location; checkout queries active records."
        },
        {
          "name": "No terminal devices paired",
          "description": "Loaded empty state for CentriPOS records at this location, not processor inventory proof."
        },
        {
          "name": "Add Terminal",
          "description": "Opens the Add Terminal Device dialog."
        },
        {
          "name": "Terminal Name",
          "description": "Human-readable operational label used to distinguish devices."
        },
        {
          "name": "Payments Hub terminal login",
          "description": "Exact device login and tenant-wide upsert key; restricted operational configuration."
        },
        {
          "name": "Upsert behavior",
          "description": "Same tenant + login updates the existing record, potentially moving its location/assignment."
        },
        {
          "name": "Device Type",
          "description": "PAX, Ingenico, or Other classification; not hardware detection or capability validation."
        },
        {
          "name": "Default Register",
          "description": "Optional register-specific routing preference within the opened location."
        },
        {
          "name": "No default register / Unassigned",
          "description": "Location-level terminal candidate used after explicit and register-default candidates."
        },
        {
          "name": "Explicit checkout override",
          "description": "Highest-priority active terminal choice when supported and provider-compatible."
        },
        {
          "name": "Register default",
          "description": "Second priority: active terminal assigned directly to the current register."
        },
        {
          "name": "Location default",
          "description": "Third priority: active terminal at the current location with no register assignment."
        },
        {
          "name": "Candidate tie-break",
          "description": "Most recently seen first, then terminal name; avoid relying on it for ambiguous routing."
        },
        {
          "name": "Register selector",
          "description": "Immediate update with no confirmation or success toast; verify after refresh."
        },
        {
          "name": "Trash / Remove this terminal?",
          "description": "Confirmed hard deletion of the CentriPOS pairing record."
        },
        {
          "name": "Terminal removed",
          "description": "Routing record was deleted; processor/device account and historical payments remain."
        },
        {
          "name": "Active state",
          "description": "Only active records are eligible at checkout; this form does not expose an active toggle."
        },
        {
          "name": "Controlled card-present test",
          "description": "One safe, authorized test proving routing and resulting CentriPOS/processor records."
        },
        {
          "name": "Full payment trace",
          "description": "Intent → terminal transaction → sale payment → register session/closure → batch → deposit."
        },
        {
          "name": "No exact screenshot",
          "description": "Harbor & Hearth safe captures do not include the Terminal Devices location-edit surface or any terminal login."
        }
      ],
      "expectedResult": "The terminal reports the expected connection state and register assignment, and one controlled payment reaches only that selected device.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "qbo-sync",
      "url": "https://platform.getcentri.com/centripos/qbo-sync",
      "title": "Understand QuickBooks Online sync status",
      "summary": "Read the exact invoice, receipt, payment, register-report and deposit evidence without confusing an observed QuickBooks update with a new payment or completed bank reconciliation.",
      "collection": {
        "id": "payments",
        "title": "Payments & CentriPay"
      },
      "section": "Integrations",
      "introduction": "A Connected badge or saved mapping does not prove that every CentriPOS workflow has posted to QuickBooks. Read the status on the exact receipt, payment, invoice, or register report, then verify the linked QuickBooks record. Never create a second accounting transaction merely to clear an uncertain state.",
      "beforeYouBegin": "Confirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.",
      "steps": [
        "Open Admin → QuickBooks Online and confirm the selected storefront, authorized QuickBooks company, Connected status, last connection time, and cached-option readiness. Refresh QuickBooks options only when an authorized administrator needs current accounts, items, payment methods, tax codes, or classes.",
        "Treat connection, saved mappings, record-level linkage and the result of the supported action as separate evidence. Some broad Ready now / Still to wire setup notices can lag the enabled record workflows. Do not use one notice as proof that every invoice/payment path is unavailable or active. If the notice conflicts with the action on your record, stop and have support confirm the intended workflow before changing accounting data.",
        "Start from the CentriPOS source record that should have created accounting activity. For a Customer Account transaction, open Sales → Receipts or Customers → Customer Accounts. For a register summary, open Register → Reports and select the exact closed report. Do not infer one record’s status from the storefront-level connection badge.",
        "On a Customer Account receipt, look for the linked QBO invoice number/action and payment rows. QBO posted means that payment has an external QuickBooks payment ID. QBO failed means the payment has no external ID and its last accounting attempt failed; preserve the displayed error before changing anything.",
        "Use Send to QBO on an eligible receipt or Send to QB on an eligible invoice only with the required invoice-send permission. If a customer match is required, compare the local customer name, company, email, phone, and source code with every proposed QuickBooks customer. Select the existing customer only when identity is certain. Approve creating a new customer only after confirming that no valid match exists.",
        "After the action, confirm Customer account receipt sent to QBO, Invoice added to QuickBooks, or the existing-invoice linked result. Open the linked invoice and compare customer, document number, dates, items, tax, payments and total. Send to QB adds or links the accounting document; it does not email the customer. A successful accounting link proves only that document relationship.",
        "Disconnecting a Customer Account invoice removes the CentriPOS link; it does not delete or void the invoice in QuickBooks. Confirm the named invoice before disconnecting, then reconcile the still-existing QBO document before resending so a duplicate is not created.",
        "For an eligible Customer Account payment with no external payment ID, use the supported resubmit control once. QBO payment posted confirms a new external payment reference; QBO payment already linked means the existing reference was recovered; QBO payment was not posted means the workflow was skipped and the reason must be reviewed.",
        "On Register Reports, use the exact badge as the starting point: QB not connected, QB manual only, QB older report, QB resend needed, QB ready, QB future report, QBO Synced, Send to QBO, EPX Review Needed, Awaiting EPX Deposit, an open-EPX-batch label, or Account payments sync separately. The badge describes that report, not the health of all accounting.",
        "An open register is a future report and cannot be sent. The list does not offer Send to QBO when the report’s accounting net is zero or when it contains only customer-account payments. Account payments sync separately means those payments follow their own invoice/accounting path and must not be posted a second time as a register-summary invoice. QB older report stays manual because it predates the configured sync start point. QB ready means eligible under the current rules; it does not prove a QuickBooks document exists.",
        "QB resend needed means one or more tracked sales changed after the drawer closed. Inspect the edits and report totals before choosing Resend report. If the notice is accurate but no resend is required under approved accounting policy, dismissing the notice only acknowledges the tracked edits; it does not update QuickBooks.",
        "CentriPay can gate a register report on processor evidence. Awaiting EPX Deposit means the expected deposit record is not yet available. An open EPX batch is still accumulating or settling. EPX Review Needed means the processor-to-report evidence needs review. Trace payment → receipt → register closure → EPX batch/deposit before sending or repairing.",
        "Choose Send report or Resend report only for the eligible closed report after reviewing its edits and totals. If a matching accounting document already exists, CentriPOS can restore its link. Open the returned document and read its type: ordinary report summaries use an invoice; eligible refund-only reports can use a refund receipt; older linked sales receipts may still exist. Do not replace one type merely to make its label match another report.",
        "A linked register report displays Connected to QuickBooks or QBO Synced. Compare the company, report number/date, included sale and tender totals, customer-account exclusions, tax, class, processing fees, payments and final total. A synced document or an observed linked deposit does not prove processor settlement, bank-feed matching, or final bank reconciliation.",
        "Only owners, super admins, and finance managers can disconnect a linked QuickBooks register report. The confirmation requires the exact CentriPOS report number. Disconnect removes the CentriPOS link but leaves the QuickBooks invoice or sales receipt in place and makes the report eligible to resend.",
        "For any failed, skipped, resend, missing-link, processor-review, or mismatch state, preserve the CentriPOS receipt/report number, QBO document/payment identifier, EPX reference when applicable, time, amount, and exact error. Correct the verified source or mapping, use one supported retry, and re-open both records to confirm the result.",
        "On Customer Accounts invoices, Refresh QuickBooks status or Check QuickBooks reads the linked accounting evidence. It does not send invoices or post new local payments. Incoming invoice/payment/deposit notifications can update observed status, communication history and accounting details while payment posting remains a separate workflow.",
        "If QuickBooks shows no remaining balance while CentriPOS still shows an open balance, use Check the open balance and reconcile the existing payment before requesting money again. Do not record a second tender solely to make the two displays agree.",
        "When Payments recorded in QuickBooks lists one payment covering several invoices, the displayed Payment total is the full payment, not this invoice’s allocation. Review the linked invoice allocation before adding amounts to a report. A missing linked deposit means no deposit was observed for that payment; it is not evidence that the customer must pay again.",
        "For an enabled processor-backed invoice payment, Pending QBO sync for EPX deposit means the customer payment is recorded but QuickBooks posting is waiting for matched settlement evidence. EPX settlement needs accounting review is a separate exception. Do not retry the card payment, create another account payment, or turn a pending settlement into a manually marked paid invoice.",
        "Where Matched EPX settlement is available, compare the full deposit processing fee with the fee allocated to this invoice, any surcharge credit, the invoice principal payment and the processor reference. Review & sync deposit is a real accounting action: an authorized administrator reviews the entire settlement and confirms one QuickBooks bank deposit. It does not rewrite the original invoice totals or replace bank-feed matching."
      ],
      "controls": [
        {
          "name": "Connected",
          "description": "The selected storefront has an active QuickBooks authorization; it is not a blanket all-records-synced status."
        },
        {
          "name": "Cached options",
          "description": "QuickBooks accounts, items, payment methods, tax codes, classes, and other values available to mapping controls."
        },
        {
          "name": "Ready now / Still to wire",
          "description": "Broad setup notices that may lag specific enabled record workflows; use the exact supported action, result and linked record as evidence."
        },
        {
          "name": "QBO invoice linked",
          "description": "An existing or newly created QuickBooks invoice is attached to this Customer Account receipt."
        },
        {
          "name": "QBO posted",
          "description": "The individual payment row has an external QuickBooks payment identifier."
        },
        {
          "name": "QBO failed",
          "description": "The payment lacks an external payment identifier and its last accounting attempt failed."
        },
        {
          "name": "Customer match",
          "description": "Identity decision that links the CentriPOS customer to an existing QBO customer or explicitly approves creation."
        },
        {
          "name": "QB not connected",
          "description": "The report remains local because this storefront has no active QuickBooks authorization."
        },
        {
          "name": "QB manual only",
          "description": "Automatic register-report sync is disabled; an eligible report can be sent manually."
        },
        {
          "name": "QB older report",
          "description": "Closed report predating the configured automatic-sync start point."
        },
        {
          "name": "QB ready",
          "description": "Closed report eligible under current sync rules but not yet proof of a posted document."
        },
        {
          "name": "QB future report",
          "description": "Open register that will be evaluated under the configured rules after closure."
        },
        {
          "name": "QB resend needed",
          "description": "Tracked sale edits occurred after close and require accounting review."
        },
        {
          "name": "QBO Synced",
          "description": "A sent sync record with a QuickBooks transaction identifier, URL, or document number is linked to the report."
        },
        {
          "name": "Send to QBO",
          "description": "Manual action available only for an eligible nonzero closed report that is not processor-gated or already linked."
        },
        {
          "name": "Awaiting EPX Deposit",
          "description": "CentriPay report is waiting for matching processor deposit evidence."
        },
        {
          "name": "EPX Review Needed",
          "description": "Available processor evidence does not reconcile cleanly enough for an automatic send decision."
        },
        {
          "name": "Open EPX batch",
          "description": "Processor batch evidence exists but the batch has not reached its final closed/settled condition."
        },
        {
          "name": "Send report / Resend report",
          "description": "Supported register-report action; resend is used after tracked edits or a prior unlinked/send attempt."
        },
        {
          "name": "Disconnect",
          "description": "Removes only the CentriPOS-to-QBO link; the external QuickBooks document remains."
        },
        {
          "name": "No public screenshot",
          "description": "No approved Harbor & Hearth capture matches these record-level states without exposing financial data, so this guide intentionally uses no invented image."
        },
        {
          "name": "Send to QB",
          "description": "Permission-controlled manual invoice action that adds/links the QBO document without emailing the customer."
        },
        {
          "name": "Refresh QuickBooks status / Check QuickBooks",
          "description": "Read and display linked QuickBooks evidence without sending invoices or creating local tender."
        },
        {
          "name": "Check the open balance",
          "description": "QuickBooks reports the balance paid while CentriPOS still has an open amount; reconcile the existing payment before asking again."
        },
        {
          "name": "Payments recorded in QuickBooks",
          "description": "Observed accounting payments; a payment total may cover several invoices and must not be counted once per invoice."
        },
        {
          "name": "Pending QBO sync for EPX deposit",
          "description": "Recorded invoice payment is awaiting matched processor settlement, not a request to collect the payment again."
        },
        {
          "name": "Matched EPX settlement",
          "description": "Processor deposit, full fee, per-invoice fee/surcharge allocation and principal-payment evidence."
        },
        {
          "name": "Review & sync deposit",
          "description": "Separate staff-approved creation/recovery of one linked bank deposit after full settlement validation."
        },
        {
          "name": "Account payments sync separately",
          "description": "The register report contains only customer-account payments, which use their own invoice/accounting path and are not sent again as a register-summary invoice."
        }
      ],
      "expectedResult": "Each source invoice, receipt, payment, report and settlement has a traceable accounting reference and an understood posted, pending, skipped, failed or review state. Observed QuickBooks data is distinguished from local tender, and duplicate collection or duplicate accounting entries are avoided.",
      "troubleshooting": [
        "Check the processor transaction status before retrying an uncertain payment or refund.",
        "Confirm the terminal, register, amount, and transaction reference all belong together.",
        "Never include full card numbers or protected credentials in a support request.",
        "If a QBO balance and local balance disagree, reconcile the actual linked payment and allocations before collecting or posting again.",
        "If a settlement review changed or a created deposit has not been confirmed locally, reopen the same review to recover the existing deposit; do not create a second deposit elsewhere.",
        "A signed incoming provider update is accounting evidence, not permission to create another local payment."
      ],
      "updated": "2026-11-16",
      "sourceReviewed": "2026-11-16",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "general-settings",
      "url": "https://platform.getcentri.com/centripos/general-settings",
      "title": "Configure General Settings",
      "summary": "Manage tenant-wide identity, A/R fields, branding, policies, numbering, labels, customer rules, saved-sale reasons, Network visibility, cash quick picks, and company contact defaults without confusing an uploaded asset or partial save with a completed configuration.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → General uses the Settings gear icon and opens General setup. These are business-wide defaults, not location/register-only preferences. Save changes performs several ordered writes and verifications; company-logo files upload immediately but their URLs remain unsaved settings until Save changes succeeds. Clear Test Sales Data is a separate owner-only destructive operation and must never be used as routine troubleshooting or on a live business. CentriPhone and CentriTeam documentation remain intentionally withheld.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin → General beside the Settings gear icon. Confirm the active CentriPOS business and that you are authorized to change tenant-wide defaults. Wait for the loading spinner to disappear; the page reads both the tenant settings and private storefront company-ID record before rendering.",
        "Start with Store settings. Store name changes the tenant name. Default currency offers US dollar, Canadian dollar, Euro, British pound, or Australian dollar. Time zone uses the selected IANA zone for business date/time behavior. Private URL currently displays an em dash and is not editable.",
        "Choose the correct Company ID type before entering Company ID. The field formats supported identifiers such as EIN, GST/HST, ABN, ACN, NZBN, UTR, CNPJ, and RFC while typing. This value is stored in a separate private storefront settings record. Clearing the value saves both company-ID type and value as null even though the selector still displays its local default.",
        "Review the Communication sources section only for the currently supported SMS/source settings shown in your tenant. Save changes routes dirty communication-source data through a separate runtime-settings service after the main tenant writes. A successful tenant update followed by a communication-source failure can therefore leave part of the change saved; reopen the page and verify each affected channel.",
        "Configure Account invoice fields separately for Customer account and Sale / invoice. Each row has Field label, normalized Field ID, Text/Date/Number Type, Active, and Remove. A blank new row is discarded on save. If a label exists without an ID, the ID is derived; manually edited IDs are normalized. Removing a row changes the future definition after save—it does not erase values already copied into historical records.",
        "Choose Add customer field or Add sale field as required. Keep IDs stable once integrations or accounting mappings use them. Save verifies that both field lists persisted; if not, it retries through the dedicated account-field update operation and reports failure if verification still disagrees.",
        "Set Account fulfillment release to Review each account fulfillment or Always release account fulfillments. Review is the safe default for open A/R receipts; auto-release allows their fulfillment to proceed like paid receipts. Test one controlled customer-account order after changing this policy.",
        "Treat Test sales reset as a production-risk boundary. Clear Test Sales Data is disabled for non-owners. For an owner, it opens Clear all test sales data? and permanently purges the tenant’s sales, line items, payments, parked receipts, linked return/exchange rows, sale-linked financing/eCart artifacts, and resets receipt counters. Cancel unless this is an explicitly authorized disposable test tenant with verified backups/retention.",
        "For Company logo, choose Square or Rectangle before selecting an image because that choice controls the crop aspect ratio. Upload accepts an image, opens the crop dialog, uploads both an original file and cropped PNG to storage, and then places new public URLs into unsaved settings. Wait for Logo uploaded — remember to save settings.",
        "Choose Replace to upload/crop another file, Crop to fetch and recrop the current displayed logo, or the X on the preview to clear the logo URL in unsaved settings. These controls do not delete prior storage objects. Choose Save changes and verify the login/receipt branding before treating the replacement or removal as complete.",
        "Edit Storewide Terms & Conditions in the rich-text editor only after legal/operations approval. This is the storefront default used across POS, customer display, and eCart, but register-level terms override it. Saving text here does not prove every historical receipt or already-open customer display immediately changed.",
        "Use Tax settings only as a pointer: General contains no tax editor. Configure tax per location in Locations & registers and verify the actual taxable sale.",
        "In Barcode and SKU settings, Generate SKUs by number controls whether sequence numbering is used instead of product-name generation. Current sequence number falls back to 1 for blank, zero, or invalid input. Changing it can affect future generated identifiers and create collision risk; search existing product/variant SKUs before saving.",
        "Choose Label printer format from Continuous feed (wide), Continuous feed (narrow), Dymo Label, or Avery Label. Choose Embedded barcodes from Only allow SKUs, Allow all barcodes, or Allow UPC/EAN only. These are defaults; print and scan one real test label before a batch.",
        "In Customer settings, Allow duplicate customers permits the same email or phone on more than one customer when enabled; disabling it blocks supported duplicate creation. The local duplicate-customer behavior is updated while editing and normalized again on save, so verify both a duplicate and unique controlled customer case after changing it.",
        "Manage Saved sale reasons in the two separate lists: Abandoned opportunity for true lost demand and Void / cancel cleanup for mistakes, duplicates, tests, or cleanup. Each list must retain one row. Adding, editing, or removing remains unsaved until Save changes. Use the dedicated Saved Sale Reasons guide for the operational close-saved-sale effect.",
        "Owners can Enable Network Hub. This makes the Network area visible for multi-location/franchise work; Network can also appear automatically when child stores exist. Enabling the menu is not proof that network catalog, inventory, transfer, permissions, or represented-business data is configured.",
        "Configure Cash denominations as positive, unique numeric quick-pick values. Add by pressing Enter or Add; values are sorted ascending. X removes a value. These buttons assist Cash tender entry at checkout and do not change currency, rounding rules, drawer counts, or physical denominations.",
        "Complete Company / HQ contact with name, email, phone, website, Twitter URL, and physical address. Check Use different address for postal address only when a separate full postal address is required. These defaults can feed price sheets, order forms, and business-level documents; review privacy and customer-facing accuracy before publishing them.",
        "Choose Save changes once. The handler reloads the latest settings, merges only dirty general keys, normalizes customer duplicate and account-field definitions, writes and verifies tenant settings, upserts the private Company ID, writes the final merged tenant state, and—only when changed—saves communication-source settings separately. Wait for Settings saved; Failed to save means completion is unproven and earlier ordered writes may need inspection.",
        "After Settings saved, reload General and verify every edited value. Then test each affected consumer: business name/time zone, account form and fulfillment, login/receipt logo, store policy, SKU creation, label print/scan, duplicate customer behavior, saved-sale decision, Network navigation/data, cash quick picks, and company document/contact output.",
        "No screenshot is published. The real Amelia Grant Harbor & Hearth /admin/general inspection exposed private company configuration and a destructive reset control while remaining in a loading state, so it was rejected rather than redacted into a misleading screen or replaced with another page."
      ],
      "controls": [
        {
          "name": "Settings gear icon",
          "description": "Exact CentriPOS Admin navigation icon for General."
        },
        {
          "name": "Save changes",
          "description": "Runs the multi-step tenant/private/runtime save and verification flow; wait for Settings saved."
        },
        {
          "name": "Failed to save",
          "description": "At least one save or verification step failed. Because writes are ordered rather than one transaction, reopen and inspect every changed section."
        },
        {
          "name": "Store name",
          "description": "Tenant-wide business name."
        },
        {
          "name": "Default currency",
          "description": "US dollar, Canadian dollar, Euro, British pound, or Australian dollar."
        },
        {
          "name": "Time zone",
          "description": "Tenant IANA time-zone default used by supported business date/time workflows."
        },
        {
          "name": "Private URL",
          "description": "Read-only em dash in the current page; no editable URL control."
        },
        {
          "name": "Company ID type / Company ID",
          "description": "Private storefront identifier record with type-specific input formatting."
        },
        {
          "name": "Communication sources",
          "description": "Supported source/SMS settings saved through a separate runtime service when dirty; detailed CentriPhone content remains withheld."
        },
        {
          "name": "Customer account fields",
          "description": "Reusable internal A/R definitions attached to customer-account scope."
        },
        {
          "name": "Sale / invoice fields",
          "description": "Reusable internal A/R definitions attached to sale/invoice scope."
        },
        {
          "name": "Field label / Field ID",
          "description": "Human label and normalized stable key. A missing key can derive from the label."
        },
        {
          "name": "Text / Date / Number",
          "description": "Supported custom account-field value types."
        },
        {
          "name": "Active",
          "description": "Keeps the definition available to supported future workflows without removing its row."
        },
        {
          "name": "Account fulfillment release",
          "description": "Review each open-account fulfillment or always release like a paid receipt."
        },
        {
          "name": "Clear Test Sales Data",
          "description": "Owner-only permanent purge of tenant sales-related test records and receipt-counter reset."
        },
        {
          "name": "Square / Rectangle",
          "description": "Logo display style and crop aspect ratio."
        },
        {
          "name": "Upload / Replace / Crop",
          "description": "Uploads original and cropped assets immediately, then stages their URLs for Save changes."
        },
        {
          "name": "Logo X",
          "description": "Clears the staged logo URL; it does not delete prior storage files."
        },
        {
          "name": "Storewide Terms & Conditions",
          "description": "Tenant storefront default rich text; register-level terms override it."
        },
        {
          "name": "Tax settings",
          "description": "Informational pointer to per-location configuration; no tax fields are editable here."
        },
        {
          "name": "Generate SKUs by number",
          "description": "Uses numeric sequence generation for future supported SKU creation."
        },
        {
          "name": "Current sequence number",
          "description": "Future sequence seed; blank/zero/invalid input becomes 1."
        },
        {
          "name": "Label printer format",
          "description": "Wide/narrow continuous feed, Dymo, or Avery default."
        },
        {
          "name": "Embedded barcodes",
          "description": "SKU-only, all barcodes, or UPC/EAN-only default."
        },
        {
          "name": "Allow duplicate customers",
          "description": "Controls supported creation of profiles sharing email or phone."
        },
        {
          "name": "Saved sale reasons",
          "description": "Separate future-selection vocabularies for abandoned opportunities and void/cancel cleanup."
        },
        {
          "name": "Enable Network Hub",
          "description": "Owner-only navigation setting; child stores can also make Network visible automatically."
        },
        {
          "name": "Cash denominations",
          "description": "Positive unique Cash checkout quick-pick values, sorted ascending."
        },
        {
          "name": "Company / HQ contact",
          "description": "Business-level contact and physical address defaults."
        },
        {
          "name": "Use different address for postal address",
          "description": "Reveals separate postal fields; unchecked uses the physical-address context."
        },
        {
          "name": "Settings saved",
          "description": "All steps returned successfully and caches were invalidated; still verify the consuming workflow."
        },
        {
          "name": "No substituted screenshot",
          "description": "Private/destructive loading-state Harbor & Hearth capture was rejected and no invented image is used."
        }
      ],
      "expectedResult": "Only the intended business default changes, the saved value persists after reload, and a controlled customer-visible workflow reflects it without altering unrelated settings.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "saved-sale-reasons",
      "url": "https://platform.getcentri.com/centripos/saved-sale-reasons",
      "title": "Configure Saved Sale Reasons",
      "summary": "Keep abandoned opportunities separate from genuine void or cleanup items by controlling the two reason lists shown when staff close a saved sale.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Saved Sale Reasons is a focused section of General Settings. The Admin navigation item uses the Save icon. These reasons are not selected when a cashier first chooses Save Sale; they appear later when an unfinished saved sale is closed as either an abandoned opportunity or a void/cancel cleanup item.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin → Saved Sale Reasons. CentriPOS opens General Settings directly at the Saved sale reasons section.",
        "Review the Abandoned opportunity list. Use these reasons when the customer did not buy and the saved sale should count as a lost opportunity, such as Not interested, Too expensive, Bought elsewhere, Timed out / no response, or Needs follow-up.",
        "Review the Void / cancel cleanup list separately. Use these reasons for cashier mistakes, duplicate saved sales, wrong customers, rebuilt quotes, tests, or other records that should not be treated as lost demand.",
        "Edit an existing label directly in its field. Keep the wording short, mutually distinct, and understandable without private customer details; the stable reason ID remains associated with the configured entry.",
        "To add a reason, type it in the matching Add reason field and choose Add, or press Enter. CentriPOS ignores a blank value and warns when the same label already exists in that list, regardless of capitalization.",
        "To remove a reason, choose the X beside it. Each list must retain at least one choice, so the remove control is disabled when only one reason remains. There is no Active or Availability switch on this screen.",
        "Choose Save at the top of General Settings. Adding, renaming, or removing a row only changes the unsaved page state until Settings saved appears.",
        "Verify the operational menu from Sales → Receipts or a saved-sale detail. Open an unfinished saved sale and choose its close or abandon action. The dialog first asks for Decision: Abandoned opportunity or Void / cancel cleanup.",
        "Choose the matching reason and add optional Notes. CentriPOS requires a reason before Mark Abandoned or Void Saved Sale can continue. The stored action reason combines the configured label with the optional note.",
        "Use Abandoned opportunity only for a real lost opportunity. It changes the saved sale to an abandoned status and feeds lost-opportunity trends. A previously abandoned saved sale can later move to Void / cancel cleanup, but it cannot be marked abandoned a second time.",
        "Use Void / cancel cleanup for a mistake, duplicate, test, or administrative cleanup. The saved sale becomes voided and remains separate from abandonment trends.",
        "If the saved sale contains active payment lines, correct or void those payment lines before closing it. Changing the reason configuration does not bypass payment, void, or permission safeguards.",
        "After changing the lists, reopen the close-saved-sale dialog or refresh the screen if it was already open. Confirm the correct list appears under the selected Decision and that a removed choice is no longer offered for a new action."
      ],
      "controls": [
        {
          "name": "Abandoned opportunity",
          "description": "Reason list for saved sales that represent genuine lost customer opportunities. These choices feed lost-opportunity trends."
        },
        {
          "name": "Void / cancel cleanup",
          "description": "Separate reason list for mistakes, duplicates, tests, wrong customers, rebuilt quotes, and administrative cleanup."
        },
        {
          "name": "Reason label",
          "description": "Human-readable choice shown to staff. Avoid duplicates and customer-sensitive detail."
        },
        {
          "name": "Add",
          "description": "Appends a nonblank, nonduplicate reason to the selected list in the current unsaved settings state."
        },
        {
          "name": "X remove control",
          "description": "Removes the row from the current settings state. It is disabled when the list has only one remaining reason."
        },
        {
          "name": "Save",
          "description": "Persists the entire General Settings change. Wait for Settings saved before leaving the page."
        },
        {
          "name": "Decision",
          "description": "Operational choice on a saved sale: Abandoned opportunity or Void / cancel cleanup. It determines which configured list is shown."
        },
        {
          "name": "Abandonment reason",
          "description": "Required selection from the Abandoned opportunity list before Mark Abandoned."
        },
        {
          "name": "Void / cancel reason",
          "description": "Required selection from the cleanup list before Void Saved Sale."
        },
        {
          "name": "Notes",
          "description": "Optional context appended to the selected reason for that saved-sale action. Do not place sensitive payment data in notes."
        },
        {
          "name": "Mark Abandoned",
          "description": "Closes the saved sale as an abandoned opportunity and makes it part of lost-opportunity analysis."
        },
        {
          "name": "Void Saved Sale",
          "description": "Closes the saved sale as a genuine void or cleanup record rather than a lost opportunity."
        },
        {
          "name": "Historical boundary",
          "description": "Changing the available lists controls future selections. Existing closed records retain the action reason already written to them."
        }
      ],
      "expectedResult": "After Settings saved appears, the configured abandonment choices show only when Decision is Abandoned opportunity, the configured cleanup choices show only for Void / cancel cleanup, each list retains at least one reason, and a newly closed saved sale stores the selected reason and optional note under the correct disposition.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "locations-registers",
      "url": "https://platform.getcentri.com/centripos/locations-registers",
      "title": "Create and Configure Locations & Registers",
      "summary": "Manage each operating location, its shared receipt numbering and tax context, register behavior, receipt template, signatures, access, payment overrides, and paired CentriPay terminals.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Locations & Registers uses the Building 2 icon. A new location is created immediately with a default Register 1. Location fields are drafts until the page-level Save; most register selectors/checkboxes auto-save the entire current register settings object, register names save on blur, restriction and user assignments write separately, and NMI Gateway has its own Save. Deletion is permanent and can affect sessions, devices, inventory, reporting, and transaction access. Make one narrow change at a time and verify in the actual location/register.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Locations & Registers, identified by the Building 2 icon. Review every card’s internal name, address, Active/Inactive state, and register count before creating or deactivating anything.",
        "Choose Add location only for an approved operating scope. Enter the required Name and optional Address, then choose Add location once. CentriPOS immediately inserts the location, attempts to create Register 1, and opens the new location editor. Confirm both records; a location can exist even if the default-register insert fails because those writes are separate.",
        "Understand location identity. Location name is internal. Public display name appears on supported e-carts, receipts, and delivery tickets and falls back to the internal name when blank. Set the timezone to the location’s operating timezone, not the administrator’s current timezone.",
        "Enter a complete Street address. It can participate in tax synchronization, delivery-hub/closest-store distance pricing, route planning, customer documents, and map links. A syntactically saved address is not proof it geocodes correctly; test the dependent workflows.",
        "Set the location Email and Phone only to approved public/operational contacts. Phone formatting follows the tenant country context. Review customer-facing receipts, e-carts, fulfillment slips, and notifications after changing identity fields.",
        "Under Tax settings, choose No location default or an approved tax rate. Registers can inherit this value or override it. Tax selection is configuration only; test taxable, exempt, online, in-store, return, delivery, and shipping carts before normal use.",
        "Under Numbering, set the receipt prefix and Starting number. Save normalizes a blank prefix to S and starting number to at least 1. Next number is read-only and never moves backward: Save keeps the greater of the existing next number and the starting number. Do not use this form to reset or reuse issued receipt numbers.",
        "Set PO number prefix and PO starting number only under an approved purchasing convention. This page does not preview collisions or historical numbering effects; create a controlled purchase order after saving.",
        "Choose the location-level Sell screen prompts as needed: warn about negative inventory, missing customer, or missing note. These are warnings, not hard inventory, customer, or note requirements. Verify each prompt on Sell with the affected location selected.",
        "Choose the page-level Save and wait for Location saved. Cancel/Back does not call Save for draft location fields. Reopen the location and verify public name, timezone, address, contacts, tax, numbering, and prompts.",
        "In Registers, choose + Add register to immediately create Register <count + 1>. Rename it in the row and leave the name field to save. Duplicate names or gaps in numbering are not prevented by this naming convention; use stable operational names.",
        "Expand each register. Under Receipts, assign a custom or POS Default receipt template. The location owns the protected prefix/number sequence shared by its registers; the older per-register receipt number fields are retained internally but not editable in this panel. Run an actual print/email/public-link test after assignment.",
        "Under End of sale, choose whether to Select user for next sale, Email receipt, Print receipt, ask for a note on all sales/never/returns only, Print note on receipt, and Show discounts on receipts. Most changes trigger a register save; wait for Register saved and reopen before changing several unrelated settings.",
        "Under Tax, select Use location default or a register-specific approved rate. This update saves immediately through the register editor. Confirm the displayed and calculated tax on a controlled sale and return from this exact register.",
        "Under Cash management, choose Cash, No cash, or Cash and card. This value affects operational expectations but does not by itself pair a payment terminal, open a session, or remove a configured payment type. Test open/close, float, cash payment, payout/drop, card, and closure reporting as applicable.",
        "Under Customer Signature & Terms, enable Require customer signature before payment only when the business has approved the legal/operational flow. Choose On-screen or Topaz USB, then Full T&C text, Simple acceptance line, or Signature only. Review customer readability, consent, retention, and receipt evidence.",
        "The remembered signature choice is local to This device for the tenant/register. Reset this device clears that device preference only. For Full T&C, edit the rich text and choose Save Terms; for Simple acceptance, leaving the label field saves through the register update. Test the actual hardware/browser.",
        "Under Access Restriction, switching Restricted register writes immediately and separately. When enabled, only owners, super admins, and assigned users can view that register’s sales and invoices. An empty assignment list leaves only owners/super admins. Assign or remove users deliberately and test with a non-owner account.",
        "The assigned-user picker can show inactive users with an Inactive badge. Do not grant access based only on the name; confirm employment/access status. User assignment is a separate write and is not reverted by Cancel on the location page.",
        "Under NMI Gateway, leave the register inheriting storefront settings unless an approved merchant/register requires an override. A tokenization key is customer-side; the Security Key is private and stored encrypted for server-side processing. Never include either credential in screenshots, tickets, or public documentation.",
        "For an override, configure ACH and 3DS only when the gateway account supports them. The optional PaymentsHub Reporting Add-On can use a register reporting MID, Production/Beta/Sandbox environment, developer key, private auth password, app source, and fee-collection mode. Choose the NMI Gateway Save and wait for its success message; it is independent of register auto-save and the page-level location Save.",
        "Under Terminal devices, pair supported CentriPay terminals to this location and choose their default register routing. A paired terminal is not the same as an NMI online-gateway override. Run a controlled push-to-terminal transaction and inspect CentriPay Transactions before retrying any uncertain result.",
        "Use the location card Active switch for reversible operational retirement. It writes immediately. Before deactivating, inspect open register sessions, fulfillment schedules/routes, device pairings, inventory ownership, active users, public/online availability, tax mappings, and reports; then verify users can no longer select it where intended.",
        "The list shows Trash only after a location is inactive. Its confirmation says registers, register summaries/sessions, cash records, terminal pairings, and location inventory will be permanently removed while receipts retain the location name. The handler deletes registers first, then the location; confirm backups/retention and downstream database behavior before Delete permanently.",
        "The editor’s Delete location uses a separate browser confirmation and directly deletes the location record. Do not treat the two deletion paths as interchangeable or tested cleanup tools. Prefer deactivation unless permanent erasure has been explicitly reviewed; there is no restore button.",
        "Deleting a register uses a browser confirmation and permanently deletes that register. Check sessions, receipts, assignments, terminal routing, gateway overrides, reports, and required audit retention first. A deleted register is not automatically recreated.",
        "After any change, sign in with an appropriate test user, choose the exact business/location/register from the CentriPOS context selector, and verify Sell, register session, receipt numbering/template, tax, customer prompts, signature, cash/card behavior, fulfillment, inventory, terminal routing, restricted reporting, and CentriPay activity.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the loaded Locations & Registers list at 1440×900 with only business showroom/warehouse cards visible. No register details, credentials, assignments, customer data, edit forms, or dialogs were opened and no values were changed."
      ],
      "controls": [
        {
          "name": "Building 2 icon",
          "description": "Exact Admin navigation icon for Locations & Registers."
        },
        {
          "name": "Add location",
          "description": "Immediately creates the location and then separately attempts to create Register 1."
        },
        {
          "name": "Location name",
          "description": "Internal operational name."
        },
        {
          "name": "Public display name",
          "description": "Customer-facing name on supported e-carts, receipts, and delivery tickets; falls back to location name."
        },
        {
          "name": "Timezone",
          "description": "Location operating timezone used by time-sensitive workflows."
        },
        {
          "name": "Street address",
          "description": "Used by supported tax, fulfillment pricing, routing, map, and customer-document workflows."
        },
        {
          "name": "Default sales tax",
          "description": "Location tax fallback; registers can inherit or override."
        },
        {
          "name": "Receipt prefix",
          "description": "Location-wide prefix; blank normalizes to S on Save."
        },
        {
          "name": "Starting number",
          "description": "Minimum initial sequence value; normalized to at least 1."
        },
        {
          "name": "Next number",
          "description": "Read-only protected counter that Save will not move backward."
        },
        {
          "name": "PO numbering",
          "description": "Location purchasing prefix and starting-number settings."
        },
        {
          "name": "Sell prompts",
          "description": "Warnings for negative inventory, missing customer, and missing note; not hard enforcement."
        },
        {
          "name": "Page Save",
          "description": "Persists location fields/settings and logs location_updated."
        },
        {
          "name": "+ Add register",
          "description": "Immediately inserts a register named from the current count."
        },
        {
          "name": "Register name",
          "description": "Saves when the inline field loses focus."
        },
        {
          "name": "Receipt template",
          "description": "Register assignment to a custom or POS Default template."
        },
        {
          "name": "End-of-sale settings",
          "description": "User selection, email/print receipt, note prompt, note printing, and discount display."
        },
        {
          "name": "Register tax",
          "description": "Inherit location default or use a register-specific rate."
        },
        {
          "name": "Cash management",
          "description": "Cash, No cash, or Cash and card operational mode."
        },
        {
          "name": "Require signature",
          "description": "Pre-payment signature workflow for this register."
        },
        {
          "name": "Signature input",
          "description": "On-screen or Topaz USB."
        },
        {
          "name": "Terms display",
          "description": "Full scrollable text, simple acceptance line, or signature only."
        },
        {
          "name": "Reset this device",
          "description": "Clears the locally remembered signature choice for this tenant/register."
        },
        {
          "name": "Restricted register",
          "description": "Immediate visibility restriction to owners, super admins, and assigned users."
        },
        {
          "name": "Assigned users",
          "description": "Separate access records; may include users visibly marked Inactive."
        },
        {
          "name": "NMI Gateway override",
          "description": "Register-specific online gateway/ACH/3DS configuration with its own Save."
        },
        {
          "name": "PaymentsHub Reporting Add-On",
          "description": "Optional register reporting credentials, environment, and fee-collection metadata."
        },
        {
          "name": "Terminal devices",
          "description": "Location CentriPay terminal pairing and default-register routing."
        },
        {
          "name": "Active switch",
          "description": "Immediate location activation/deactivation."
        },
        {
          "name": "List deletion",
          "description": "Available only while inactive; deletes registers then location after a detailed confirmation."
        },
        {
          "name": "Editor deletion",
          "description": "Separate direct location delete after native browser confirmation."
        },
        {
          "name": "Register delete",
          "description": "Permanent register deletion after native browser confirmation."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant /admin/locations capture showing only loaded location cards; no register or secret details exposed."
        }
      ],
      "expectedResult": "The location and its registers appear with the intended status and become available only to users and workflows that have access.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-locations.png",
        "alt": "Harbor & Hearth Locations and Registers screen showing configured showroom and warehouse locations in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "users-roles",
      "url": "https://platform.getcentri.com/centripos/users-roles",
      "title": "Manage users, roles, and permissions",
      "summary": "Add staff, control storefront access, build job roles, organize the team, and preserve an accurate access history.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin is available only to owners, super admins, and custom roles with Manage settings. Give each person only the access needed for their work, and deactivate staff with history instead of trying to erase them.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Users. Use Search for users or the Role and Location filters to find an existing staff member. The list shows their role, assigned locations, sales targets, last activity, invitation status, and whether access is enabled.",
        "Choose Add user. Select Send invitation to email a personal welcome link, or Create without invite to create the account with a temporary password of at least six characters. Enter the display name, email, and storefront role, then choose Send invitation or Create user. Location access is not selected in this dialog.",
        "For an invited user, wait for them to accept the welcome email and set their password. If the profile says Welcome pending or Welcome expired, open the user, go to Security and ID, and choose Resend welcome. A password-reset email works only after the welcome email has been accepted and the email is confirmed.",
        "Open a user from the list to edit their display name, email, photo, daily, weekly, and monthly sales targets, assigned role, employment record, and access status. The Locations section is read-only on this screen and shows the locations already assigned; no listed locations is displayed as All locations.",
        "In Employment and access, turn User access off when a staff member should no longer sign in. Add the employment status, end date, rehire eligibility, separation reason, and internal notes as appropriate, then choose Save changes. Disabling access keeps the person available on historical receipts, reports, and audit records. You cannot disable your own access or the account owner from this screen.",
        "Use Security and ID to send a confirmed user a reset email or set a matching password of at least six characters. For an unconfirmed invite, resend the welcome email instead. These controls manage the person’s Centri Account credential; their storefront membership, role, and direct-login policy are separate controls.",
        "Open Admin → Users → Roles to review the system and custom roles. Owner has full access and cannot be modified. Super Admin has operational full access, but owner financial reports still require an approved financial role or the explicit financial-reporting permission.",
        "Choose Add role to create a named custom role with an optional description. Open the role and enable only the needed permissions across Sell, Discounts, Products, Customers, Payments, Reporting, Setup, and Visibility. Agency accounts also see Support & Proxy Access and Agency Administration. Each checkbox change is written immediately; Done returns to the role list.",
        "Use the receipt-scope permissions carefully: View receipts controls history access, View receipts across all storefront locations expands its location scope, and Limit receipts to this user’s own sales narrows it. Hide product costs removes cost, margin, and vendor-cost visibility. Manage settings is what allows a custom role into Admin.",
        "Open Admin → Users → Team to assign a manager, department, job title, and one or more work lanes such as Sales, Service, Delivery, Logistics, Warehouse, Admin, Management, or Support. Team classifications support org views, coaching, service, delivery, warranty, and reporting; they do not replace the user’s security role. Choose Save for each changed profile.",
        "Use Admin → Users → Activity for the Activity Log and Login History when you need evidence of user, role, or sign-in activity. Search and date filters help narrow the record. Removing an activity-log row does not undo the original action and is restricted to authorized administrators.",
        "Delete user is only for a mistaken, unused profile with no sales, line items, register sessions, activity, inventory, or customer-interaction history. Type the exact display name to confirm. CentriPOS blocks deletion when dependencies exist; deactivate that user instead. You cannot delete yourself or an owner until ownership is transferred.",
        "After any access change, have the user sign in through the intended Centri Account path and confirm the correct business, locations, navigation sections, receipt scope, financial visibility, and allowed actions. Membership, location access, role permissions, active status, and direct-login security policy all have to agree."
      ],
      "controls": [
        {
          "name": "Users tab",
          "description": "Searchable staff list with role, location, targets, last activity, invitation state, and enabled status."
        },
        {
          "name": "Send invitation",
          "description": "Emails a personal welcome link; the recipient accepts it and creates their password before password-reset email is available."
        },
        {
          "name": "Create without invite",
          "description": "Creates an account immediately with the temporary password entered by the administrator."
        },
        {
          "name": "Welcome pending / expired",
          "description": "The email is not yet confirmed; use Resend welcome from Security and ID."
        },
        {
          "name": "User access",
          "description": "Controls whether the person can sign in while preserving their historical records."
        },
        {
          "name": "Location access",
          "description": "Locations already assigned to the storefront membership. The user-detail Locations section shows the result but does not edit it."
        },
        {
          "name": "Role",
          "description": "Storefront permission set controlling visible areas and allowed actions."
        },
        {
          "name": "System role",
          "description": "Protected built-in role. Owner cannot be modified; Super Admin has operational full access with a separate financial-reporting boundary."
        },
        {
          "name": "Custom role",
          "description": "Named permission set created for the business."
        },
        {
          "name": "Permission checkbox",
          "description": "Turns one capability on or off and saves immediately."
        },
        {
          "name": "Manage settings",
          "description": "Permission that gives a custom role access to Admin."
        },
        {
          "name": "Receipt scope",
          "description": "Combination of receipt history, cross-location, and own-sales-only permissions."
        },
        {
          "name": "Hide product costs",
          "description": "Removes product cost, margin, and vendor-cost visibility."
        },
        {
          "name": "Team structure",
          "description": "Manager, department, job title, and work-lane classification; it does not grant security access."
        },
        {
          "name": "Activity Log",
          "description": "Auditable user and system actions. Deleting a log row does not reverse the underlying action."
        },
        {
          "name": "Login History",
          "description": "Recorded sign-in sessions available under Activity."
        },
        {
          "name": "Security and ID",
          "description": "Welcome resend, password-reset email, or administrator-set password for the Centri Account credential."
        },
        {
          "name": "Deactivate",
          "description": "Recommended offboarding action for a staff member with historical records."
        },
        {
          "name": "Delete unused user",
          "description": "Permanent removal available only when no protected operational dependencies exist."
        },
        {
          "name": "Direct-login policy",
          "description": "Separate security control determining whether a membership can authenticate directly or is available only through an authorized switch/proxy path."
        }
      ],
      "expectedResult": "The staff member can authenticate only through the intended Centri Account path, enter only the intended storefront and locations, and see only the navigation, receipt scope, financial information, and actions allowed by the active membership and role. Offboarded staff remain in historical records but cannot sign in.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "security-settings",
      "url": "https://platform.getcentri.com/centripos/security-settings",
      "title": "Configure Security",
      "summary": "Record intended login, user-switching, MFA, inactivity, and role policies while understanding the current page’s immediate-save behavior and location-record enforcement gap.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Security uses the Shield icon and is a sensitive administrative surface. The current component stores one `security` object inside the settings JSON of only the first location row returned for the tenant; it does not select a location, update every location, or prove that login, switching, MFA, barcode, privilege comparison, or inactivity code consumes these values. Treat the page as policy configuration awaiting end-to-end enforcement verification—not as evidence that controls are active. Every selection saves immediately with no confirmation or visible saving indicator.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Security, identified by the Shield icon, while signed in to the intended CentriPOS business. Keep a separate verified Owner recovery session and current account-recovery methods available before changing access policy.",
        "Wait for the loading spinner to disappear. The screen concurrently requests one location settings record and the tenant’s custom roles. It does not display fetch errors. If either request fails, defaults or an empty role table can appear without an error banner; do not save until the loaded values are independently confirmed.",
        "Understand the storage scope before editing. The component reads the first location row returned with `limit(1)` and no explicit ordering, then stores defaults and role overrides inside that row’s settings.security object. There is no Location selector and no tenant-level security table write. In a multi-location business, the chosen record can be ambiguous and other location rows are not updated.",
        "Read Default settings as the intended fallback policy represented by four stored fields. The current defaults used when no stored object is returned are Has access to log in, Don’t require a password when switching with a barcode, Username and password, and inactivity re-authentication off. A displayed default can therefore mean either a real stored choice or a fallback after missing/failed data.",
        "Under Log in access, Has access to log in stores `full`; Only has access to log in through user switching stores `switch_only`. Selecting either immediately submits a save. The page itself does not sign anyone out, disable an identity-provider credential, or demonstrate that the login route enforces this field.",
        "Under Switching user accounts, choose one intended policy: Never require a password; Don’t require a password when switching with a barcode; Require a password when switching to a user with more privileges; or Always require a password. The selection saves immediately.",
        "Do not infer implementation details from the switching labels. The page contains no barcode enrollment/scanner controls, privilege-ranking editor, password prompt, switching test, or session-lock behavior. Verify the actual user switcher with controlled accounts for lower, equal, and higher privilege, barcode and non-barcode entry, and failed/cancelled authentication.",
        "Under Authentication method, Username and password stores `password`; Username and password with multi-factor authentication stores `password_mfa`. Selecting either saves immediately. This page has no MFA factor enrollment, recovery-code, authenticator, SMS/email factor, reset, grace-period, remembered-device, or enforcement-status controls.",
        "Before selecting Password + MFA, confirm how every affected account enrolls and recovers through the actual Centri Account authentication system. After saving, prove enforcement with a designated non-owner account in a private browser session. A stored `password_mfa` value or success toast alone is not proof of MFA.",
        "Require logging in after inactivity stores a boolean immediately. The page has no inactivity duration, warning, grace period, pause-screen, exempt-workflow, or resume editor. Verify the actual timeout source and behavior across Sell, customer data, reports, customer display, and interrupted forms; never test during a terminal payment.",
        "Review Role specific settings only if roles loaded successfully. Each row is a tenant custom-role record sorted with system roles first, then name. The table can be absent because there are no roles or because the role query failed; confirm in Admin → Users/Roles before concluding no overrides exist.",
        "For a non-Owner role, Log in access can inherit Default setting, explicitly allow Has access to log in, or require User switching only. Authentication method can inherit Default setting, require Password only, or require Password + MFA. Every dropdown selection immediately saves the entire override map.",
        "For the exact system role whose name is `Owner`, direct Log in access is hard-coded as Has access to log in and has no selector. Owner Authentication method remains editable. This UI safeguard does not prove the owner account’s credential, MFA factor, recovery email, or break-glass process is usable.",
        "Choosing Default setting stores the literal override value `default` rather than removing that role’s override object. Any enforcement consumer must interpret `default` as inheritance. Verify behavior; do not assume the mere presence of an override row means it differs from the baseline.",
        "Change only one control at a time. Each action rereads the first location and writes its whole settings JSON with the updated security object, preserving the then-read other settings. Rapid overlapping saves have no queue or version check and can race, while another administrator can also change the row. Wait for Security settings saved, reload, and confirm before the next change.",
        "If no location row is returned during a save, the function ends without a success or error toast. If the location update errors, the page shows the raw error message but keeps the new local selection visible. In either case, reload and inspect stored state; never treat the selected radio/dropdown alone as persisted.",
        "Create a written test matrix before rollout: direct login for Owner and representative roles; `switch_only`; each password-switching policy; barcode and ordinary switching; lower/equal/higher privileges; Password only and MFA; enrolled versus unenrolled MFA; inactivity timeout/resume; logout/session revocation; offline/network failure; and recovery.",
        "Run tests with designated demo users in an isolated browser while the Owner recovery session remains untouched. Verify both permitted and denied paths. Check that user switching changes the effective audit identity and permissions, not just the displayed name, before customer, inventory, or financial work.",
        "For a multi-location tenant, inspect which location row currently holds settings.security and whether runtime enforcement reads that same row for every register. Do not copy or repair production location JSON merely to make the page look consistent without a scoped engineering/data plan and before/after verification.",
        "If the intended restriction is not enforced, restore only a known-good tested policy through an authorized path and escalate as a security defect. Preserve tenant, location/register, role IDs/names, stored policy values, test user, route, time, expected/actual result, and audit evidence without including passwords or MFA secrets.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Security page was both a sensitive administrative surface and remained loading during the safe inspection window, so the capture was rejected rather than shown, fabricated, or replaced."
      ],
      "controls": [
        {
          "name": "Shield icon",
          "description": "Exact CentriPOS Admin navigation icon for Security."
        },
        {
          "name": "Loading spinner",
          "description": "One location-settings query and the custom-role query are running; errors are not displayed by this component."
        },
        {
          "name": "First location record",
          "description": "Only settings source/destination selected with limit(1) and no explicit order; no location picker or all-location update."
        },
        {
          "name": "Default settings",
          "description": "Intended fallback values merged with the one returned settings.security object."
        },
        {
          "name": "Has access to log in",
          "description": "Stores login_access `full`; enforcement must be tested separately."
        },
        {
          "name": "Only through user switching",
          "description": "Stores login_access `switch_only`; it does not revoke credentials by itself."
        },
        {
          "name": "Never require a password",
          "description": "Stored switching policy with no in-page enforcement test."
        },
        {
          "name": "Barcode exception",
          "description": "Stored no-password-barcode policy; no barcode setup exists here."
        },
        {
          "name": "Higher privilege",
          "description": "Stored password-higher-privilege policy; no privilege-rank editor exists here."
        },
        {
          "name": "Always require a password",
          "description": "Stored always-password switching policy."
        },
        {
          "name": "Username and password",
          "description": "Stores auth_method `password`."
        },
        {
          "name": "Password + MFA",
          "description": "Stores auth_method `password_mfa`; no factor enrollment/recovery controls exist here."
        },
        {
          "name": "Require logging in after inactivity",
          "description": "Stored boolean without a duration/editor or proven pause implementation."
        },
        {
          "name": "Role specific settings",
          "description": "Tenant custom roles plus saved override map; the section is hidden when no roles are returned."
        },
        {
          "name": "Default setting override",
          "description": "Literal `default` value stored in the role override object and expected to inherit baseline."
        },
        {
          "name": "Owner direct login",
          "description": "Hard-coded non-editable Has access to log in only for a system role named exactly Owner."
        },
        {
          "name": "Owner authentication",
          "description": "Still selectable separately in the Authentication method column."
        },
        {
          "name": "Immediate save",
          "description": "Every radio, checkbox, and dropdown change writes without page-level Save or confirmation."
        },
        {
          "name": "Security settings saved",
          "description": "One location row update returned success; not enforcement proof."
        },
        {
          "name": "Silent no-location outcome",
          "description": "No location row means the save ends without success/error feedback."
        },
        {
          "name": "Visible-state mismatch",
          "description": "A failed update can leave the newly selected local value visible until reload."
        },
        {
          "name": "Race risk",
          "description": "Overlapping full settings-JSON writes have no version check or serialized queue."
        },
        {
          "name": "No public screenshot",
          "description": "The approved Harbor & Hearth inspection rejected the sensitive/loading Security surface."
        }
      ],
      "expectedResult": "The intended policy is confirmed in the exact stored location record and then proven end to end for direct login, effective-identity switching, barcode and privilege cases, MFA enrollment/recovery, inactivity, representative roles, denied paths, and Owner recovery; immediate saves are reloaded and no first-location setting is mistaken for verified tenant-wide enforcement.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "loyalty-settings",
      "url": "https://platform.getcentri.com/centripos/loyalty-settings",
      "title": "Review Loyalty settings",
      "summary": "Understand the complete current Loyalty screen, its CentriCRM direction, and why no earning, reward, balance, tier, or redemption behavior should be promised yet.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Loyalty uses the Gift icon. In the current customer-visible product, this route is a fully loaded feature-status screen—not an editable loyalty-program setup. The real Amelia Grant Harbor & Hearth capture documents that exact state without fabricated controls or reward data.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Loyalty using the Gift icon. Confirm the page heading is Loyalty and the supporting line reads Configure loyalty programs and rewards.",
        "Read the single Loyalty panel. The current message is Loyalty program configuration coming soon. This is the completed loaded state of /admin/loyalty, not a loading failure or a collapsed settings form.",
        "Read the smaller integration note: This will integrate with CentriCRM loyalty features. It describes intended future direction; it does not confirm that CentriCRM enrollment, points synchronization, rewards, or redemption is active for this CentriPOS tenant.",
        "Do not look for a hidden Save button, program switch, points-per-dollar rule, reward catalog, tier editor, expiration setting, member list, balance ledger, import, report, or redemption control. None is exposed on this screen today.",
        "Do not interpret Products → Promotions → Offer loyalty points as an operational loyalty program. The promotion editor stores that flag, but the current promotion matcher does not award points and this Loyalty route provides no program configuration or balance system.",
        "Do not tell staff or customers that purchases earn points, that balances exist, or that a reward can be redeemed until a released interface exposes those rules and a controlled sale proves earning, balance posting, receipt/customer visibility, return reversal, and redemption behavior end to end.",
        "If loyalty was contractually expected for the business, use Contact support from the Help Center and include the tenant/business name, the /admin/loyalty route, the exact coming-soon message, and the expected capability. Do not include customer details, payment data, or invented reward balances.",
        "When the screen changes in a future release, treat the new controls as undocumented until this guide and its real screenshot are recaptured and each earning, adjustment, reversal, expiration, and redemption path is tested."
      ],
      "controls": [
        {
          "name": "Gift icon",
          "description": "Exact CentriPOS Admin navigation icon for Loyalty."
        },
        {
          "name": "Loyalty heading",
          "description": "Confirms the current /admin/loyalty route is loaded."
        },
        {
          "name": "Configure loyalty programs and rewards",
          "description": "Current page description; it is not evidence that configuration controls are available."
        },
        {
          "name": "Loyalty panel",
          "description": "The only feature-status panel currently rendered on this route."
        },
        {
          "name": "Loyalty program configuration coming soon",
          "description": "Explicit boundary showing that editable program controls are not yet available."
        },
        {
          "name": "CentriCRM integration note",
          "description": "Future-direction statement, not proof of a live loyalty connection or data synchronization."
        },
        {
          "name": "No Save or setup controls",
          "description": "There is currently no program activation, earning, reward, tier, expiration, member, balance, or redemption interface on this screen."
        },
        {
          "name": "Promotions boundary",
          "description": "Offer loyalty points can be stored on a promotion, but the current matcher does not award points and Loyalty has no operational program configuration."
        },
        {
          "name": "Verification boundary",
          "description": "Do not promise loyalty until controlled earning, receipt/customer balance, return reversal, and redemption tests succeed after release."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/loyalty in its fully loaded coming-soon state; it contains no customer or reward data."
        }
      ],
      "expectedResult": "The screen clearly identifies whether loyalty configuration is available for this business. No reward behavior should be assumed until controls are enabled and tested.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-loyalty.png",
        "alt": "Harbor & Hearth Loyalty settings showing the current feature availability state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "store-credit-settings",
      "url": "https://platform.getcentri.com/centripos/store-credit-settings",
      "title": "Configure Store Credit & Gift Cards safely",
      "summary": "Edit the shared tenant gift-card enablement, expiry flag, and amount limits while recognizing the screen’s validation and operational boundaries.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Store credit uses the Wallet icon and is the only current wired editor for gift_card_settings. Database policy permits the tenant owner to manage it. These values represent stored-value policy and potential financial liability, but this screen does not issue, reload, redeem, expire, search, or reconcile cards. Current UI validation does not prevent negative values, a minimum above the maximum, or other unreasonable combinations; review policy, law, accounting, and test evidence before saving.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Store credit in the intended business. Confirm the Store Credit & Gift Cards heading and wait for loading to finish. Do not confuse it with Contacts → Store credit, which uses the Badge Dollar Sign icon and shows customer balance records.",
        "Verify that you are the tenant owner authorized to manage the setting. Other signed-in users can be allowed to read settings by database policy but should not assume the save is permitted.",
        "Read Enable gift cards. Changing the switch updates only the unsaved form state; choose Save changes to persist it. Disabling the flag changes the configuration summary but this screen does not show or resolve outstanding issued balances or accounting liability.",
        "Read Gift Cards Expire. This is only a stored Boolean flag. The page has no duration, expiration date rule, notice, escheatment, jurisdiction, grandfathering, or historical-card controls. Do not enable it until the business has a lawful, fully implemented expiration workflow outside this screen.",
        "Review Minimum amount and Maximum amount as currency-value policy even though the inputs are plain numbers without currency symbols. The current UI accepts negative values and does not enforce minimum ≤ maximum, decimal precision, or a reasonable cap. Enter only reviewed nonnegative values with minimum no greater than maximum.",
        "Be aware of input fallback behavior: clearing Minimum stores/display-updates as 0; clearing Maximum or entering numeric 0 changes the local value to 10000 because of the current parser fallback. If a zero maximum is intended, this screen cannot reliably enter it.",
        "If no settings row exists, the page displays in-memory defaults: enabled, no expiry, minimum 0, maximum 10000. Save changes does nothing until a field is changed because the underlying settings state is still null. Toggle or edit an intended field, recheck all four values, then save to create the tenant row.",
        "Choose Save changes once and wait for Settings saved. The upsert writes the current settings object for the tenant. There is no confirmation dialog, change preview, activity summary, effective date, or rollback control on this page.",
        "Open Products → Gift Cards after saving. Its read-only summary should reflect enabled state, stored sales channel, and limits. The Products page cannot edit the values, and its disabled-state Enable gift cards button is currently inert.",
        "Do not claim end-to-end gift-card readiness from a successful settings save. Current customer-visible POS source has no issuance, reload, balance lookup, redemption, or card-management component. Confirm with CentriPOS support and complete a controlled end-to-end implementation test before launching the program.",
        "For accounting, separately verify QuickBooks gift-card liability and breakage/revenue mappings, payment-type policy, receipt-template gift-card display, and Gift Cards reporting. A settings toggle does not configure those surfaces or prove their records reconcile."
      ],
      "controls": [
        {
          "name": "Wallet icon",
          "description": "Exact Admin navigation icon for Store credit."
        },
        {
          "name": "Badge Dollar Sign icon",
          "description": "Different Contacts → Store credit navigation item for customer balance records, not this settings editor."
        },
        {
          "name": "Enable gift cards",
          "description": "Unsaved is_enabled switch; requires Save changes. It does not settle outstanding balances."
        },
        {
          "name": "Gift Cards Expire",
          "description": "Unsaved has_expiry Boolean without duration, legal-policy, notice, or historical-card controls."
        },
        {
          "name": "Minimum amount",
          "description": "Plain numeric min_amount input; blank becomes 0 and the UI does not reject negative values."
        },
        {
          "name": "Maximum amount",
          "description": "Plain numeric max_amount input; blank or numeric 0 falls back to 10000 in current UI."
        },
        {
          "name": "Missing-row defaults",
          "description": "Enabled, no expiry, minimum 0, maximum 10000 are displayed in memory when no tenant row exists."
        },
        {
          "name": "Save changes",
          "description": "Owner-policy upsert of the current shared settings object. It does not run a gift-card transaction."
        },
        {
          "name": "Shared configuration",
          "description": "Products → Gift Cards reads the same tenant row as a summary."
        },
        {
          "name": "Sales channel",
          "description": "Stored on the shared row and displayed on Products → Gift Cards, but not editable on this Admin page."
        },
        {
          "name": "Predefined amounts",
          "description": "Exists in the underlying settings schema but has no control on this page."
        },
        {
          "name": "No validation guard",
          "description": "UI does not enforce nonnegative values, min ≤ max, decimal precision, legal caps, or liability review."
        },
        {
          "name": "No card operations",
          "description": "No issuance, reload, redemption, balance lookup, expiration processing, or card list exists in this settings screen."
        },
        {
          "name": "Accounting boundary",
          "description": "QBO mappings, reporting, payment types, and receipt display are separate configurations."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/store-credit showing only program settings, with no customer balances or gift-card records exposed and no values changed."
        }
      ],
      "expectedResult": "A controlled issuance and redemption follow the configured location and usage rules, and the remaining balance updates correctly.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-store-credit.png",
        "alt": "Harbor & Hearth Store Credit and Gift Cards settings showing program behavior without customer balances in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sales-taxes",
      "url": "https://platform.getcentri.com/centripos/sales-taxes",
      "title": "Configure and Verify Sales Tax",
      "summary": "Create immutable percentage rates, synchronize US location defaults through ZIPTax, control online-order nexus behavior, and safely retire rates without confusing location/register assignment or historical sales.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Sales tax uses the Receipt icon. Tax configuration is legal and financial policy, not a recommendation from CentriPOS. ZIPTax location sync performs multiple sequential lookups and writes without an all-or-nothing transaction; a failure can leave earlier locations changed. Nexus and Always collect save immediately. Manual rate percentages lock after creation, while names remain editable. Confirm requirements with a qualified tax professional and test actual calculations in every channel.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Sales tax, identified by the Receipt icon. Wait for Sales tax rates to finish loading, then inventory Location sync, Tax nexus, Tax rates, and Tax groups before changing anything.",
        "Before ZIPTax sync, go to Admin → Locations & Registers and verify every saved location address is complete, current, and geocodable. ZIPTax sync is enabled only when the tenant country is United States; non-US tenants see an availability message and a disabled button.",
        "Understand what Sync from locations does. It processes saved locations one at a time, looks up the address in ZIPTax, creates or reuses a ZIPTax-managed rate for the resolved reporting area, records provider/source metadata, and assigns that rate as the location default when allowed.",
        "Multiple stores resolving to the same ZIPTax source key reuse one managed rate. Existing ZIPTax-managed defaults can have their percentage, generated name, normalized address, source payload, and last-synced time refreshed after an address/rate change.",
        "A location with no address, an unresolvable/nonpositive lookup, a broken managed mapping, or an existing manual default is skipped. A manual default is not silently overwritten; the result shows Current and ZIPTax percentages and offers Use ZIPTax sync (same rate) or Replace with ZIPTax sync when applicable.",
        "Choose Sync from locations only after recording the current location defaults/rates and approving the change window. The operation is sequential and not transactional: earlier creates, updates, and assignments are not automatically rolled back if a later location throws an error.",
        "Read every result row, not just the summary badges. Created means a managed rate was created and assigned; Reused means an existing managed rate was assigned; Updated means managed rate/source or assignment changed; Skipped can mean already current, intentionally protected manual default, missing address, lookup failure, or broken mapping.",
        "If a manual-default result offers an opt-in button, compare Current, ZIPTax, and normalized address. Choosing it immediately creates/reuses and assigns a managed rate—even when the percentage is identical—so future sync can refresh it. There is no second confirmation or rollback button.",
        "After sync or opt-in, reopen Admin → Locations & Registers and verify each location’s Default sales tax. Check any register-specific tax override because it can continue to supersede the location default. Keep obsolete manual rates until assignments and downstream mappings are reviewed.",
        "Under Tax nexus, understand the current online-order rule: when Always collect is off, supported online checkout collects only when the destination state is listed as nexus, tax is not disabled, and the customer is not tax-exempt. No states means the page warns online orders will not collect tax.",
        "To add nexus, choose an unlisted US state/DC abbreviation and +. To remove one, choose X on its chip. Each action saves the entire sorted nexus list immediately and logs a settings update; there is no page-level Save or confirmation. Wait for Tax nexus settings saved and test before another change.",
        "Always collect tax immediately stores the override and hides the Nexus states editor while on. It instructs supported checkout to treat all destination states as having nexus; it does not determine the correct jurisdiction/rate, validate registrations, or make collection lawful. Enable only under approved tax advice.",
        "Choose Add tax rate to create a manual rate. Enter a required stable Name and Rate as a percentage, such as 8.25 for 8.25%. The UI currently has no min/max validation, so it can submit negative, excessive, or otherwise unreasonable numeric values. Enter only a reviewed finite nonnegative percentage.",
        "Choose Add tax rate once and wait for Tax rate added. The new rate is not automatically made Default or assigned to a location/register by this form. Assign it separately under Locations & Registers, then test the exact register and channel.",
        "A ZIPTax badge identifies a rate with provider source metadata. Default identifies the row’s global is_default flag, but this screen has no control to set/unset that flag. Location default and register override are separate settings and may matter more for the operational sale.",
        "Use Pencil to edit only Tax name. The displayed Tax rate percentage is locked after creation to preserve reporting accuracy. To change a percentage, create a new approved rate, reassign intended locations/registers/mappings, test, and only then consider retiring the old rate.",
        "Renaming a ZIPTax-managed rate can be temporary: future sync updates the generated name when the name is blank, still equals the prior provider label, or starts with ZIPTax. Use a deliberate custom name that does not start with ZIPTax only when operational policy requires it, and verify later sync behavior.",
        "Use Trash only after auditing location defaults, register overrides, products/tax groups, open carts/orders, saved/layaway/account receipts, online checkout, QuickBooks tax mappings, reports, and integrations. The confirmation says historical sales are unaffected, but current assignments or foreign-key constraints can make deletion fail.",
        "Confirm Delete only for the exact named percentage. There is no restore action. Preserve the rate when it remains necessary to interpret active configuration or reconcile historical/accounting evidence.",
        "Tax groups are read-only rows on this page. There is no create, edit, membership, rate assignment, or delete control in the current component. No tax groups configured is a completed empty state, not a failed load.",
        "Test a matrix after every change: location-default and register-override in-store sales; taxable/non-taxable products; tax-exempt and ordinary customers; discounts; returns/exchanges; pickup/delivery/shipping and shipping-taxability; e-cart/online destinations inside/outside nexus; Always collect; rounding; receipts; Sales Tax reports; register closure; and QuickBooks mappings/sync.",
        "For an unexpected amount, capture the business/location/register, customer exemption, destination, channel, item taxability, assigned rate ID/name/percentage, nexus/Always collect state, discounts, and receipt. Do not repair financial records or change a rate merely to make one receipt look right.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the loaded /admin/taxes screen at 1440×900 with the actual Receipt navigation icon and tax-configuration summary. No ZIPTax synchronization, nexus change, rate creation/edit/deletion, location assignment, or customer/transaction data was invoked or exposed."
      ],
      "controls": [
        {
          "name": "Receipt icon",
          "description": "Exact Admin navigation icon for Sales tax."
        },
        {
          "name": "Location sync",
          "description": "US-only ZIPTax orchestration across saved location addresses."
        },
        {
          "name": "Sync from locations",
          "description": "Sequential multi-location lookup/create/reuse/update/assignment operation; not an all-or-nothing transaction."
        },
        {
          "name": "Created",
          "description": "New ZIPTax-managed rate/source created and assigned."
        },
        {
          "name": "Reused",
          "description": "Existing managed reporting-area rate assigned."
        },
        {
          "name": "Updated",
          "description": "Managed rate/source and/or assignment refreshed."
        },
        {
          "name": "Skipped",
          "description": "Already current, protected manual default, missing/unresolved address, invalid lookup, or broken mapping."
        },
        {
          "name": "Normalized address",
          "description": "Provider-resolved address evidence shown in a sync result."
        },
        {
          "name": "Current / ZIPTax",
          "description": "Existing manual rate comparison with provider suggestion."
        },
        {
          "name": "Use ZIPTax sync (same rate)",
          "description": "Switches a matching manual default to a provider-managed equivalent."
        },
        {
          "name": "Replace with ZIPTax sync",
          "description": "Replaces a differing manual location default with the managed rate."
        },
        {
          "name": "ZIPTax badge",
          "description": "Rate has provider source metadata and can be refreshed by later sync."
        },
        {
          "name": "Tax nexus",
          "description": "Immediate tenant list used by supported destination-based online tax decisions."
        },
        {
          "name": "Always collect tax",
          "description": "Immediate tenant override treating all destination states as nexus in supported checkout."
        },
        {
          "name": "Add a state / X",
          "description": "Immediate full-list nexus save; no page-level Save."
        },
        {
          "name": "Add tax rate",
          "description": "Creates a manual name and immutable percentage."
        },
        {
          "name": "Rate (%)",
          "description": "Percentage units; current UI lacks reasonable range validation."
        },
        {
          "name": "Default badge",
          "description": "Global is_default marker with no editor on this screen."
        },
        {
          "name": "Pencil",
          "description": "Renames a rate only; percentage stays locked."
        },
        {
          "name": "Trash / Delete",
          "description": "Confirmed permanent rate deletion; no restore and assignments may block it."
        },
        {
          "name": "Tax groups",
          "description": "Read-only list in the current page."
        },
        {
          "name": "Location default",
          "description": "Separate Admin → Locations & Registers assignment."
        },
        {
          "name": "Register override",
          "description": "Separate register-level tax choice that can supersede location default."
        },
        {
          "name": "Historical sales boundary",
          "description": "Deletion confirmation says historical sales are unaffected; still verify active dependencies and reporting."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant /admin/taxes capture; no tax mutation or transaction/customer data exposed."
        }
      ],
      "expectedResult": "Representative taxable, exempt, and non-taxable test carts calculate as expected for the selected location.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-taxes.png",
        "alt": "Harbor & Hearth Sales Tax Rates screen showing tax configuration and location coverage in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "receipt-settings",
      "url": "https://platform.getcentri.com/centripos/receipt-settings",
      "title": "Build, assign, and test Receipt Templates",
      "summary": "Create custom thermal or letter receipts, control customer-visible identity/data/policies, assign them per register, and verify every delivery format with a real controlled transaction.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Receipts uses the Receipt icon. The system POS Default is locked and recoverable; duplicate it to customize. The builder has no rendered receipt preview and most edits remain unsaved until Save. Logo upload writes a public media object immediately but still requires Save to attach its URL to the template. Templates can expose customer contact/balance data, gift-card code/balance/expiry, policies, barcodes, and captured signatures—enable only what policy and recipient privacy allow.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Receipts. Wait for loading, then review Template name, Template style, Width, Receipts visibility, POS Default badge, and row actions. “No receipt templates yet” is a completed empty state; Add receipt template creates New Receipt Template immediately as thermal 80 mm and opens its editor.",
        "Understand the POS Default. It cannot be edited or deleted. Its list-row switch can immediately change only the default print style between Thermal receipt (using existing width or 80 mm) and 8.5 x 11. Duplicate template creates an unlocked <name> Copy with all copied content but is_default false and no automatic register assignment.",
        "For non-default templates, choose the row pencil. Set a distinct Name, Output format Thermal receipt or 8.5 x 11 paper, and, for thermal, 80 mm countertop or 58 mm compact width. There is no live print/PDF/email preview inside the builder.",
        "Under Logo, choose Use storefront logo, Custom logo, or No logo. Inherit uses the tenant General-setup logo. A custom image opens the 2.4:1 crop tool, then uploads PNG to a public product-media path immediately and updates the draft URL. Save the template to retain the attachment. Removing the draft logo does not delete the uploaded storage object.",
        "Use Quick header builder cautiously. It can copy selected business name, location name, register name, address, phone, email, and website into rich HTML. Business/address/contact values come from tenant General settings; location/register names are prefilled only when exactly one assigned location/register is detected. Shared multi-location/register templates leave those names blank by default.",
        "Choose Replace header with selected details to overwrite header_html, Add selected details to append, or Clear header. These are draft operations. The copied header is a snapshot and does not automatically follow later tenant/location/register changes; reapply and save when source details change.",
        "Edit Header content directly when needed. Review all text, links, and embedded images as customer-visible content. Use Receipt number prefix only as template display wording; do not assume it changes the register’s underlying receipt counter/numbering policy.",
        "Under Cashier label, choose whether to Show who processed the sale and set its label. Decide whether exposing the staff display identity is appropriate on printed, emailed, downloaded, text-linked, and public receipts.",
        "Under Line Item Display, select Name + SKU, Name only, or SKU only. Separately choose Show line item discounts and Show tax breakdown per item. Test variable/custom items, returns, discounts, and tax rounding rather than relying on labels alone.",
        "Under Totals & Labels, set Subtotal, Grand total, Change given, and Amount due wording. Enable Print tax summary and its label only when it matches accounting/tax policy. Enable Print gift card details only when card number, balance, and expiry may safely appear on every applicable receipt format and recipient.",
        "Under Customer Details, turn Include customer section on/off and select Full name, Company/organization, Account number, Email, Phone, Mailing address, and Account & store credit balances. Apply data minimization: balances and contact/address fields are sensitive and may travel through print, email, text link, PDF, screenshots, or forwarded public links.",
        "Under Policies & Fine Print, Use store policies replaces the draft with the current General-setup store policy HTML; Add store policies appends it. Use register policy override is available only when exactly one assigned register has usable policy text. Shared templates across multiple registers cannot auto-select one override.",
        "Add signature line inserts a printable blank line and the current signature label into policy HTML; it does not capture an electronic signature. Clear fine print removes the draft. Store/register shortcut content is copied, not linked, so later policy edits do not update this template automatically. Review legal text with the business’s authorized policy owner.",
        "Use Footer Message for approved closing content and optionally Print scannable sale barcode. The barcode helps staff find a sale but also exposes an encoded sale identifier; test scanning and handling under receipt privacy policy.",
        "Under Captured Signature, Print signature on receipt includes an already saved checkout signature and lets you set the label above it. This is separate from the blank signature line shortcut. Do not expose biometric/signature evidence without consent, retention, and delivery-channel approval.",
        "Under Email Delivery, set the customer-facing subject line; the receipt number is added automatically. Avoid unnecessary customer or transaction details in the subject because email metadata can be broadly visible.",
        "Choose Save once and wait for Template saved. Cancel/Back leaves without invoking Save, but any uploaded media object may already exist. Reopen the template and confirm the persisted values.",
        "Back in the list, Receipts visibility controls whether a template is Shown or Hidden in the Receipts selection context. With only one template it is Always shown and the switch is disabled. This visibility setting is not the same as assigning the template to a register.",
        "Go to Admin → Locations & Registers, open each intended register, and assign the custom receipt template. A duplicated/new template is not assigned automatically. Do not reuse a location-specific header/policy template across mismatched registers without reviewing its customer-visible content.",
        "To delete a non-default template, use Trash from the list or Delete this template in the editor. Confirm the named template; registers using it revert to the default. There is no restore. Preserve required historical/policy evidence and verify affected register assignments before deletion.",
        "Run controlled sales for every assigned register and relevant scenario. Inspect thermal 58/80 mm or letter print, Receipts reprint/selection, email, text/public link, PDF/download, customer/no-customer, discounts/tax, partial/account balance, gift card (only if operational), fulfillment, return, barcode, policy, staff label, and captured signature. Confirm actual output—not just saved settings—before launch."
      ],
      "controls": [
        {
          "name": "Receipt icon",
          "description": "Exact Admin navigation icon for Receipt Templates."
        },
        {
          "name": "POS Default",
          "description": "Locked recoverable system template; duplicate to customize."
        },
        {
          "name": "Default style switch",
          "description": "Immediate list action changing default thermal versus 8.5 x 11 output."
        },
        {
          "name": "Add receipt template",
          "description": "Immediately creates an unlocked New Receipt Template, thermal 80 mm, then opens it."
        },
        {
          "name": "Duplicate",
          "description": "Copies template content to <name> Copy, removes Default state, and does not assign registers."
        },
        {
          "name": "Output format",
          "description": "Thermal receipt or 8.5 x 11 paper."
        },
        {
          "name": "Paper width",
          "description": "80 mm countertop or 58 mm compact for thermal templates."
        },
        {
          "name": "Logo mode",
          "description": "Inherit storefront, custom public uploaded logo, or no logo."
        },
        {
          "name": "Logo upload",
          "description": "Uploads cropped PNG immediately; Save is still required to persist template reference."
        },
        {
          "name": "Quick header builder",
          "description": "Copies selected current identity/contact values into header HTML; it is not dynamically linked."
        },
        {
          "name": "Replace / Add / Clear header",
          "description": "Overwrite, append, or clear draft header content."
        },
        {
          "name": "Receipt number prefix",
          "description": "Display configuration, not proven receipt-counter mutation."
        },
        {
          "name": "Cashier label",
          "description": "Controls whether/how the sale processor identity appears."
        },
        {
          "name": "Line item display",
          "description": "Name + SKU, Name only, or SKU only."
        },
        {
          "name": "Line item discount / tax per line",
          "description": "Independent customer-visible detail toggles."
        },
        {
          "name": "Totals labels",
          "description": "Custom labels for subtotal, total, change, and amount due."
        },
        {
          "name": "Tax summary",
          "description": "Optional aggregate tax display and label."
        },
        {
          "name": "Gift card details",
          "description": "Can print card number, balance, and expiry; high-sensitivity setting."
        },
        {
          "name": "Customer fields",
          "description": "Name, company, account number, email, phone, address, balances."
        },
        {
          "name": "Policy shortcuts",
          "description": "Copy current store or single-register policy HTML into the draft; no ongoing linkage."
        },
        {
          "name": "Add signature line",
          "description": "Printable blank sign-off line, not electronic capture."
        },
        {
          "name": "Sale barcode",
          "description": "Scannable receipt identifier for later lookup."
        },
        {
          "name": "Captured signature",
          "description": "Optional rendering of an already saved customer signature."
        },
        {
          "name": "Email subject",
          "description": "Customer email subject with receipt number added automatically."
        },
        {
          "name": "Save",
          "description": "Persists draft fields; no in-builder output preview."
        },
        {
          "name": "Receipts visibility",
          "description": "Shown/Hidden selection availability; not register assignment."
        },
        {
          "name": "Register assignment",
          "description": "Separate Admin → Locations & Registers configuration."
        },
        {
          "name": "Delete",
          "description": "Non-default only; confirmed permanent deletion makes assigned registers revert to default."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/receipts in a fully rendered no-template state. No editor, receipt, customer, policy, signature, or register details are exposed."
        }
      ],
      "expectedResult": "The saved template produces a test receipt with the intended branding, fields, policy text, and delivery behavior.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-receipts.png",
        "alt": "Harbor & Hearth Receipt Templates screen showing template guidance and the fully rendered empty state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "fulfillment-settings",
      "url": "https://platform.getcentri.com/centripos/fulfillment-settings",
      "title": "Configure Pickup, Delivery, and Shipping Methods",
      "summary": "Build customer-facing fulfillment choices, fees, eligibility, distance pricing, and scheduling without confusing the three independent tabs or their save behavior.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Fulfillment Methods uses the Truck icon and defaults to Delivery. Method names, fees, taxable state, enablement, and deletion affect checkout choices and order totals. Add, rename, price, Tax, Enabled, and trash actions write immediately; schedules, the delivery hub, and Advanced delivery settings have their own Save actions. Trash has no confirmation or restore. Test every intended location/register/cart and Fulfillment Center result before launch.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Fulfillment Methods, identified by the Truck icon. The URL retains the selected Pickup, Delivery, or Shipping tab; confirm the tab before changing anything.",
        "Start with Pickup when customers collect orders. Enter a required customer-facing method name, such as Curbside or In-store counter, and a nonnegative base price, then choose Add. Blank/invalid price text becomes 0. The new row is written immediately.",
        "For each pickup row, click the name or pencil to rename and click the displayed amount to edit its base price. Enter or blur commits the edit; Escape cancels the inline editor. Tax controls whether the method fee is taxable, and the unlabeled row switch controls Enabled. These switches save immediately.",
        "Configure the base Pickup Schedule separately. For each available weekday choose Time Windows, Specific Slots, or Free-form, then set Start, End, Max Slots, window minutes when applicable, and buffer minutes. These are drafts until Save Schedule appears and is chosen.",
        "Use Pickup Method Schedules only when one pickup method needs different availability or capacity. Select the method, configure its weekdays and slot values, and choose Save. If no method-specific rows are set, that method uses the base pickup schedule.",
        "Open Delivery. Choose the Primary Delivery Hub only when operations or hub-distance pricing require one, then choose Save Hub. Changing the selector alone is unsaved. Active locations populate this list; No hub selected removes the stored hub reference.",
        "Add each delivery method with its required name and base price. A new delivery method starts taxable, enabled by the database default, flat-priced, price-enabled, generally available, unable to use past fulfillment dates, and with no saved location/register scope. Verify the row after Add.",
        "Use a delivery row’s inline name, amount, Taxable, and Enabled controls carefully because they persist immediately. If Advanced has Charge a delivery price off, the row shows No method price and its amount is not editable from the list.",
        "Open Advanced for delivery-only controls. Charge a delivery price off is intended for contract/account methods priced through products, agreements, or manual terms. Allow past delivery dates permits backdating for invoice/account workflows; do not enable it for ordinary forward scheduling.",
        "Under Limit availability, search and select active Locations and/or active Registers. With no selection the method is general. Add to the available delivery options keeps general methods alongside matching scoped methods; Use as the only scoped delivery option hides general choices when that scope matches. Save advanced settings is required.",
        "Choose Flat base price for a fixed fee; Distance from delivery hub for hub mileage; or Distance from closest assigned store for the nearest participating store. Distance pricing uses the configured multiplier in dollars per mile, a dollar adjustment, and optional nearest/up rounding to $1, $5, or $10.",
        "For closest-store pricing, enter a base price only for locations that should participate. A location with no base price is not assigned for closest-store matching. Confirm location addresses are usable and test the actual customer address; the configuration screen does not preview a mileage quote.",
        "Choose Save advanced settings and wait for Delivery pricing updated. Cancel closes the dialog without saving its draft. Reopen Advanced to verify pricing, eligibility, price-enabled state, backdating, and assigned locations/registers.",
        "Configure Delivery Schedule. Scheduling mode saves immediately when changed: Use Schedule exposes the weekly grid; Day Only retains the grid but has staff choose a delivery day and optionally record no preference, before, after, or between times.",
        "In Use Schedule, enable intended weekdays and set Mode, Start, End, Max Slots, Window minutes for Time Windows, and Buffer minutes. Choose Save Schedule when the dirty-state button appears. The Schedule Preview is a configuration summary, not proof of checkout capacity behavior.",
        "Open Shipping and add customer-facing methods such as Standard Ground or Express. Names, prices, Tax, Enabled, inline edits, and trash behavior match Pickup: each row action writes immediately and there is no separate method-list Save.",
        "In Shipping Schedule, choose Open-ended when shipping does not require a scheduled day, or Use Schedule when availability/capacity applies. Choose whether the selected date means Ship on or Deliver by. Configure weekday mode, hours, slots, windows, and buffer when scheduled, then choose Save Schedule.",
        "To remove any pickup, delivery, or shipping method, choose its trash icon only after checking active carts, orders, customer promises, and downstream operations. The current UI deletes immediately with no confirmation, archive state, or restore control.",
        "Run controlled checkout tests for each enabled method across every intended location, register, channel, customer/account type, taxable scenario, address, and date. Confirm the displayed choice, fee/tax, eligibility, distance result, date/slot capacity, receipt, sale record, and Fulfillment Center work item before offering it to customers.",
        "If the page shows No pickup/delivery/shipping methods configured, treat it as a completed empty state for that tab—not a loading failure. Harbor & Hearth’s real Amelia Grant screenshot shows the fully rendered empty Delivery tab with no hub or methods configured and no settings changed."
      ],
      "controls": [
        {
          "name": "Truck icon",
          "description": "Exact Admin navigation icon for Fulfillment Methods and the Delivery/Shipping method headings."
        },
        {
          "name": "Pickup / Delivery / Shipping tabs",
          "description": "Three independent method and schedule surfaces; the selected tab is stored in the URL query."
        },
        {
          "name": "Method name",
          "description": "Required customer-facing choice; click the row name or pencil to rename immediately."
        },
        {
          "name": "Base price",
          "description": "Nonnegative fee; Add treats blank or unparsable text as 0. Inline blur/Enter saves."
        },
        {
          "name": "Tax / Taxable",
          "description": "Immediate switch controlling tax treatment of the method fee."
        },
        {
          "name": "Enabled switch",
          "description": "Immediate availability flag for the method."
        },
        {
          "name": "Trash icon",
          "description": "Immediate hard delete with no confirmation or restore in the current UI."
        },
        {
          "name": "Grip handle",
          "description": "Displayed on method rows, but these components do not implement drag-and-drop reordering."
        },
        {
          "name": "Pickup Schedule",
          "description": "Base weekly pickup availability used separately from delivery."
        },
        {
          "name": "Pickup Method Schedules",
          "description": "Optional per-method override; if unset, the method uses the base pickup schedule."
        },
        {
          "name": "Primary Delivery Hub",
          "description": "Active location used by hub-based delivery pricing; selection requires Save Hub."
        },
        {
          "name": "Save Hub",
          "description": "Persists only the hub setting, separately from methods and schedules."
        },
        {
          "name": "Advanced delivery pricing",
          "description": "Saved dialog for price enablement, past dates, scope, pricing mode, adjustments, rounding, and participating stores."
        },
        {
          "name": "Charge a delivery price",
          "description": "Off creates a no-method-price option for account/contract workflows."
        },
        {
          "name": "Allow past delivery dates",
          "description": "Permits backdated fulfillment dates for the selected delivery method."
        },
        {
          "name": "Locations / Registers scope",
          "description": "Restricts a delivery method to selected active operational contexts."
        },
        {
          "name": "Add availability behavior",
          "description": "Scoped method appears alongside applicable general methods."
        },
        {
          "name": "Exclusive availability behavior",
          "description": "Matching scope uses only explicitly scoped delivery methods."
        },
        {
          "name": "Flat base price",
          "description": "Fixed configured delivery fee."
        },
        {
          "name": "Distance from delivery hub",
          "description": "Hub mileage pricing; requires a saved, addressed primary hub."
        },
        {
          "name": "Distance from closest assigned store",
          "description": "Uses the closest location with an entered base price."
        },
        {
          "name": "Distance multiplier / adjustment",
          "description": "Per-mile amount plus a fixed dollar adjustment."
        },
        {
          "name": "Rounding",
          "description": "None, nearest $1/$5/$10, or round up to $1/$5/$10."
        },
        {
          "name": "Scheduling mode",
          "description": "Delivery-only selector that persists immediately as Use Schedule or Day Only."
        },
        {
          "name": "Time Windows / Specific Slots / Free-form",
          "description": "Available schedule-generation modes for enabled weekdays."
        },
        {
          "name": "Start / End",
          "description": "Available operating span for the weekday."
        },
        {
          "name": "Max Slots",
          "description": "Configured daily capacity value."
        },
        {
          "name": "Window / Buffer",
          "description": "Window duration and spacing inputs used by scheduled availability."
        },
        {
          "name": "Save Schedule",
          "description": "Persists dirty pickup, delivery, or shipping weekly schedule changes."
        },
        {
          "name": "Open-ended shipping",
          "description": "Does not require a scheduled shipping day."
        },
        {
          "name": "Ship on / Deliver by",
          "description": "Meaning assigned to a selected scheduled shipping date."
        },
        {
          "name": "Schedule Preview",
          "description": "Read-only summary of enabled schedule rows, not an end-to-end capacity test."
        },
        {
          "name": "Empty state",
          "description": "A fully rendered tab with no configured methods; not evidence that another tab is empty."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/fulfillment-methods at 1440×900, fully loaded on the empty Delivery tab. It exposes no customer/order data and no values were changed."
        }
      ],
      "expectedResult": "Each enabled method appears on an eligible test cart with the intended schedule, fee, instructions, and downstream Fulfillment Center behavior.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-fulfillment-methods.png",
        "alt": "Harbor & Hearth Fulfillment Methods screen showing pickup, delivery, and fulfillment configuration in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "admin-centripay",
      "url": "https://platform.getcentri.com/centripos/admin-centripay",
      "title": "Open CentriPay from Admin",
      "summary": "Use the Admin shortcut to reach the current CentriPay Settings workspace, then choose the exact payment channel or register rule you intend to manage.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → CentriPay is a compatibility shortcut, not a second payment-configuration screen. It uses the Zap icon and immediately redirects from /admin/centripay to CentriPay → Settings. All current settings live in the dedicated CentriPay area so credentials, transaction activity, reporting, and alerts are not split across two copies.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin and choose CentriPay, identified by the Zap icon. CentriPOS redirects you to CentriPay → Settings and highlights the dedicated CentriPay area.",
        "If you already see CentriPay in the main navigation, choose CentriPay → Settings directly. Both paths lead to the same current settings workspace.",
        "On the Settings index, choose In-Person Payments for Payments Hub credentials, CentriPay Cloud terminals, Tap to Pay on iPhone, environment, and location-specific webhook readiness.",
        "Choose Online Payments for the NMI Gateway configuration used by keyed payments, saved cards, eCart, online-store checkout, billing links, and supported ACH.",
        "Choose Billing-Link Fees only when the business intentionally adds a percentage or flat convenience fee to supported public billing links. This is merchant pricing behavior, not a processor-fee feed.",
        "Choose Register Rules to review which registers inherit the company online-payment defaults and which use a register-specific gateway, reporting MID, or ACH rule.",
        "Use the CentriPay section list to move to Overview, Transactions, Reporting, or Alerts. These are distinct operational screens; returning to Admin is not required.",
        "Before editing, confirm the active CentriPOS business and, for location-specific in-person settings, the selected location. Never infer the merchant or environment from the browser path alone.",
        "Save only inside the settings subsection you changed and wait for its success state. A save in In-Person Payments does not automatically update Online Payments or a register override.",
        "Run one controlled test in the affected channel. For an uncertain payment result, inspect CentriPay → Transactions before retrying; do not use the Admin shortcut or page refresh as a payment-retry action.",
        "If a bookmark or older instruction opens /admin/centripay, keep it only as a navigation convenience. Share the current branded pos.getcentri.com/centripay/settings path when directing an authorized administrator to the settings workspace."
      ],
      "controls": [
        {
          "name": "Admin → CentriPay",
          "description": "Backward-compatible Admin shortcut that redirects to the dedicated CentriPay Settings screen."
        },
        {
          "name": "Zap icon",
          "description": "Product navigation icon used for both the CentriPay area and its Admin shortcut."
        },
        {
          "name": "CentriPay → Settings",
          "description": "Canonical settings workspace for in-person payments, online payments, billing-link fees, and register rules."
        },
        {
          "name": "In-Person Payments",
          "description": "Location-based Payments Hub and CentriPay Cloud setup, terminals, Tap to Pay, environment, and webhook readiness."
        },
        {
          "name": "Online Payments",
          "description": "NMI Gateway card and ACH configuration for non-terminal payment channels."
        },
        {
          "name": "Billing-Link Fees",
          "description": "Optional percentage or flat fee applied by supported public billing-link workflows; it is separate from processor pricing."
        },
        {
          "name": "Register Rules",
          "description": "Shows inherited company settings and register-specific online gateway, reporting, or ACH behavior."
        },
        {
          "name": "Overview",
          "description": "Seven-day payment command-center summary and links to the operational detail screens."
        },
        {
          "name": "Transactions",
          "description": "Processor and gateway activity used to verify payment results before a retry."
        },
        {
          "name": "Reporting",
          "description": "Transactions, batches, deposits, statements, and register-closure reconciliation by configured location."
        },
        {
          "name": "Alerts",
          "description": "Supported processor notices and integration issues requiring attention."
        },
        {
          "name": "Redirect boundary",
          "description": "There is no independent CentriPay form under Admin. The old Admin URL resolves to the same dedicated settings workspace."
        },
        {
          "name": "Credential safety",
          "description": "Merchant identifiers, usernames, passwords, API keys, webhook secrets, and security keys remain restricted to authorized administrators and must not appear in screenshots or support messages."
        }
      ],
      "expectedResult": "The Admin shortcut resolves to the canonical CentriPay Settings workspace, the intended settings subsection and business or location context are visible, only that subsection is changed, and one controlled payment follows the saved channel or register rule without exposing or duplicating private configuration.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "contact-settings",
      "url": "https://platform.getcentri.com/centripos/contact-settings",
      "title": "Review Contact Settings",
      "summary": "Read every visible contact-type, lifecycle, CentriCRM-mapping, and smart-view reference on the current schema-preview screen without mistaking planned behavior for saved configuration.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Contact settings uses the Sliders Horizontal navigation icon; the page heading itself uses the Settings 2 icon. The Amelia Grant Harbor & Hearth route is a fully loaded, read-only Schema-ready preview. Its wording describes the model intended for a future database-backed editor and must not be treated as proof that contact types, automatic conversion, saved views, or CRM field mappings are active.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Contact settings using the Sliders Horizontal icon. Confirm /admin/contact-settings loads the Contact Settings heading with the Settings 2 icon and the description about classification, purchaser promotion, and CentriCRM lifecycle mapping.",
        "In Contact types, read the Schema-ready badge and its boundary: these six cards are defaults for the editable type catalog, while the database-backed editor belongs in the next schema release. The cards are reference content, not selectable rows.",
        "Read Lead: Known person or company before a completed purchase. Lead alone carries the Default marker in this preview. There is no visible control to change the default.",
        "Read Customer: Auto-promoted after first completed purchase unless overridden. The wording describes intended behavior; this screen contains no switch, rule editor, event history, or test control that proves conversion is executing.",
        "Read Company: Business account, bill-to entity, or organization record. Read Vendor: Supplier or partner contact that should not be treated as a buyer. These cards do not create, merge, or reclassify actual company or supplier records.",
        "Read Household: Shared account grouping for related household members. Read Archived: Hidden from day-to-day lists without deleting history. These are model descriptions, not actions on a customer or association.",
        "Read Auto-conversion: First completed purchase should promote Lead to Customer while preserving manual admin overrides. The word should is future-model language. Verify any real contact lifecycle from the customer record and activity evidence rather than assuming this preview changed it.",
        "Read CentriCRM mapping: Marketplace install should store field ids for CentriPOS Contact Type, Customer ID, and Customer Since. No marketplace connection, field picker, identifier, synchronization status, or Save action appears here.",
        "Read Smart views: Contact views should filter by type, source, tags, owner, location, channel, purchases, balances, and activity. This card does not create a view or confirm those dimensions are currently filterable together.",
        "Read Next schema release. It explicitly calls for contact_types, per-tenant contact-type settings, saved contact views, and CentriCRM field-mapping persistence before edits are enabled. The visible Editor coming next button is disabled.",
        "Do not search for hidden edit affordances or attempt to persist changes from this page. There are no active inputs, add/delete/reorder controls, color selectors, mappings, Save/Cancel actions, or editable tenant overrides.",
        "Use the live Contacts, Companies & households, Vendors/Suppliers, and CentriCRM-supported workflows for current operations, and verify their behavior independently. If an editable Contact Settings feature was expected contractually, contact support with the tenant, route, visible Schema-ready state, and expected control—without customer data or CRM secrets."
      ],
      "controls": [
        {
          "name": "Sliders Horizontal icon",
          "description": "Exact Admin navigation icon for Contact settings."
        },
        {
          "name": "Settings 2 icon",
          "description": "Icon displayed beside the Contact Settings page heading."
        },
        {
          "name": "Schema-ready",
          "description": "Badge identifying the current contact-type model as a schema preview rather than an editable catalog."
        },
        {
          "name": "Lead / Default",
          "description": "Reference type for a known person or company before purchase; the preview marks it as default without exposing a default selector."
        },
        {
          "name": "Customer",
          "description": "Reference type described as auto-promoted after first completed purchase unless overridden."
        },
        {
          "name": "Company",
          "description": "Reference type for a business account, bill-to entity, or organization."
        },
        {
          "name": "Vendor",
          "description": "Reference type for a supplier or partner that should not be treated as a buyer."
        },
        {
          "name": "Household",
          "description": "Reference type for a shared grouping of related household members."
        },
        {
          "name": "Archived",
          "description": "Reference type intended to hide a record from day-to-day lists without deleting history."
        },
        {
          "name": "Auto-conversion",
          "description": "Future-model statement about Lead-to-Customer promotion; no active configuration or proof of execution appears here."
        },
        {
          "name": "CentriCRM mapping",
          "description": "Future-model statement naming CentriPOS Contact Type, Customer ID, and Customer Since field IDs; no connector or field controls appear here."
        },
        {
          "name": "Smart views",
          "description": "Future-model dimensions: type, source, tags, owner, location, channel, purchases, balances, and activity."
        },
        {
          "name": "Next schema release",
          "description": "Explicit prerequisite list for contact_types, tenant settings, saved views, and CRM mapping persistence."
        },
        {
          "name": "Editor coming next",
          "description": "Disabled button confirming the editor is unavailable in the current screen."
        },
        {
          "name": "No Save action",
          "description": "Nothing on this route writes contact configuration today."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of the loaded schema-preview state; it exposes no customer records, CRM field identifiers, or editable settings."
        }
      ],
      "expectedResult": "The screen accurately documents the current contact-type model and planned conversion, CentriCRM mapping, and smart-view behavior without implying that the future editor or persistence controls are already available.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-contact-settings.png",
        "alt": "Harbor & Hearth Contact Settings showing contact types, conversion behavior, CentriCRM mapping, and smart-view guidance in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "contact-sources",
      "url": "https://platform.getcentri.com/centripos/contact-sources",
      "title": "Create, order, and deactivate Customer Sources",
      "summary": "Maintain the stable attribution choices shown in interaction workflows, control their display order, and retire old values without erasing historical references.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "The navigation label is Contact sources with the Megaphone icon; the page heading is Customer sources. Every tenant member is permitted by the current database policy to view and manage these rows, so establish an internal owner before making changes. Trash does not delete a source—it sets Enabled off. Disabled sources remain in this Admin list with a Disabled badge but are excluded from the current Post-Interaction customer-source picker.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Contact sources. Wait for loading to finish and confirm the Customer sources heading with the Megaphone icon.",
        "Review every existing name, description, Enabled state, and order before adding another. Names are unique within the business, and the page has no search, merge, usage count, or historical-attribution preview.",
        "Choose Add Source or, in the fully rendered empty state, Create your first source. Both open New Customer Source.",
        "Enter the required Name and optional Description. Use a stable origin such as Google / Maps, Referral, Event, or Repeat customer only when it matches the business’s attribution policy; avoid temporary campaign names unless reporting explicitly requires that granularity.",
        "Leave Enabled on when staff should be able to choose the source in supported interaction workflows. Choose Create once and wait for Source created. An exact duplicate tenant/name is rejected; read Failed to save instead of changing punctuation merely to bypass uniqueness.",
        "To revise a source, choose the pencil, update Name, Description, or Enabled, and choose Update. Wait for Source updated. Renaming changes the shared source label referenced by historical sales rather than creating a new historical snapshot.",
        "Understand the ordering behavior. Until any source has a manual sort value of 10,000 or more, the shared hook displays sources alphabetically. Dragging a row over another and ending the drag saves positions as 10,000, 10,010, 10,020, and so on, after which manual order takes precedence.",
        "Reorder on a pointer/drag-capable device. Source order saved confirms the writes. If any update fails, the page restores the previous local list and shows Failed to save source order. Verify the resulting order in the Post-Interaction source picker.",
        "Be careful when editing after reordering: the current upsert hook sends sort_order 0 when the edit form does not provide an order. Updating a source can therefore move that row ahead of manually ordered values on the next refresh. Recheck and drag the complete list back into the intended order after any edit.",
        "To retire a source, choose the trash icon. There is no confirmation dialog. The action updates is_enabled to false, shows Source deactivated, and keeps the row visible with Disabled; it does not delete the row or erase historical sale references.",
        "A disabled source is filtered out of the current Post-Interaction customer-source choices. If a sale context already carries that source ID, the interaction form may retain the ID internally but cannot resolve it as an enabled selected option; preserve historical meaning and use an approved replacement for new attribution.",
        "To restore a deactivated source, choose its pencil, turn Enabled on, and Update. There is no separate restore button.",
        "After creating, renaming, ordering, disabling, or restoring, open Communications → Post-Interaction Form and inspect the Customer source picker. Confirm only enabled sources appear, in the intended order, and run a controlled interaction attribution test before relying on reports."
      ],
      "controls": [
        {
          "name": "Megaphone icon",
          "description": "Exact navigation, heading, and empty-state icon for Contact/Customer sources."
        },
        {
          "name": "Contact sources",
          "description": "Admin navigation label."
        },
        {
          "name": "Customer sources",
          "description": "Page heading and attribution concept."
        },
        {
          "name": "Add Source / Create your first source",
          "description": "Open the same New Customer Source dialog."
        },
        {
          "name": "Name",
          "description": "Required trimmed tenant-wide unique source label."
        },
        {
          "name": "Description",
          "description": "Optional explanation shown under the source in Admin."
        },
        {
          "name": "Enabled",
          "description": "Controls availability in supported new-interaction selection; disabled rows remain in Admin."
        },
        {
          "name": "Pencil",
          "description": "Opens Edit Source for name, description, and Enabled state."
        },
        {
          "name": "Grip handle",
          "description": "Drag-and-drop ordering control; saves manual sort values after drag end."
        },
        {
          "name": "Alphabetical fallback",
          "description": "Used until at least one row has a manual sort_order of 10,000 or more."
        },
        {
          "name": "Manual order",
          "description": "Rows saved at 10-point increments starting at 10,000."
        },
        {
          "name": "Edit-order caveat",
          "description": "Editing currently writes sort_order 0 when no explicit order is passed, so verify/reapply ordering afterward."
        },
        {
          "name": "Trash icon",
          "description": "Immediately deactivates by setting is_enabled false; it does not hard-delete."
        },
        {
          "name": "Disabled badge",
          "description": "Shows a retained source that is unavailable for new selection."
        },
        {
          "name": "Post-Interaction picker",
          "description": "Uses enabled sources only and follows the shared sorted list."
        },
        {
          "name": "Historical reference",
          "description": "Sales.customer_source_id points to the shared row; deactivation preserves it, while renaming changes the displayed shared label."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/customer-sources in a fully rendered empty state. It shows the correct Megaphone icon and creation controls with no customer/source records or dialog exposed."
        }
      ],
      "expectedResult": "The source appears once in the active selection list and can be used consistently for attribution.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-customer-sources.png",
        "alt": "Harbor & Hearth Customer Sources screen showing source management and the fully rendered empty state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "financing-settings",
      "url": "https://platform.getcentri.com/centripos/financing-settings",
      "title": "Configure Financing",
      "summary": "Configure PayTomorrow or Katapult for an exact register, understand what is and is not verified, and avoid exposing credentials or unintentionally copying Katapult configuration across a location.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Financing uses the Banknote icon and stores provider configuration per register. Financing is a sensitive credit/lease workflow. Provider approval, disclosures, pricing, adverse-action handling, eligibility, delivery evidence, settlement, and funding remain governed by the provider and applicable law. The current form has no credential test, delete/reset control, confirmation for location-wide copy, or transactional rollback. It also loads the PayTomorrow API signature from the normal settings payload into browser state when saved, so treat this page as credential-bearing and never capture or share it.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Financing, identified by the Banknote icon. Confirm the signed-in business and obtain written authorization for the exact PayTomorrow or Katapult merchant account before opening or editing credentials.",
        "Read the Location and Register selectors immediately. The page automatically chooses the first location returned by name and then the first register returned for that location; it does not intentionally follow the operating-context register. Select the exact target manually before trusting any displayed provider state.",
        "Changing Location clears the register choice and automatically selects the first register in the new location when available. The provider tabs appear only after a register is selected. If no register appears, configure/authorize the location’s register rather than assuming the provider is disabled.",
        "Choose PayTomorrow or Katapult. Each tab loads only the selected register’s stored rows and initializes a draft. Switching register/provider replaces the draft; save deliberate changes before switching and never paste one merchant’s values into another tenant or register.",
        "Interpret Connected cautiously. PayTomorrow shows Connected when a saved API Username exists. Katapult shows Connected when a saved Merchant ID exists. This does not validate the password/key, API signature, public token, environment, merchant ownership, account status, callback, provider availability, or successful application flow.",
        "The Enabled switch changes only the current draft until Save. Turning it off does not remove credentials or historical applications. Turning it on does not prove provider readiness, customer qualification, legal approval, channel eligibility, or that the payment choice will appear in every cart.",
        "For PayTomorrow, enter the provider-issued API Signature used for the OAuth Basic authorization header, API Username, API Password, and optional Merchant Reference ID. Confirm the exact production/test account and required scopes directly with the provider.",
        "Treat the PayTomorrow API Signature as fully sensitive. Although password-masked, a saved signature is read from the settings payload into this browser and can be revealed with the eye control. The page’s generic credential-encryption wording must not be relied on for that field. Do not use Show on a shared screen, remote session, recording, or screenshot.",
        "A saved PayTomorrow API Password is represented by a masked placeholder and is not populated into the draft. Leaving the password field blank on a later save preserves the stored encrypted column because the field is omitted from the update. The current form provides no explicit clear/delete credential action.",
        "For Katapult, enter the provider-issued API Key, Merchant ID, and Public Token used by its checkout widget. The saved API Key is represented by a masked placeholder and is not loaded into the draft; leaving it blank on a later save preserves the stored key. Merchant ID and Public Token do load into ordinary browser fields.",
        "Use the eye control only to review a newly typed PayTomorrow signature/password or Katapult API key in a private environment. The shared secret-visibility state is reused within each provider form; hide the value immediately and clear clipboard/history under the business’s credential policy.",
        "Set Minimum Cart Value as a whole numeric currency threshold at or above zero. The input has min 0 and step 1, but the draft uses JavaScript numeric conversion and the form has no explicit finite/range/currency validation or maximum. Enter only a reviewed nonnegative amount and test boundary/rounding behavior.",
        "Choose Production only for approved live credentials and transactions. Choose Staging only for a provider-supported test account. The selector stores the label but does not test that the credentials belong to that environment; mismatching them can fail or route to the wrong provider system.",
        "For the selected register, choose Save PayTomorrow Settings or Save Katapult Settings once. The save upserts the provider row for the current tenant/register/provider. Wait for Financing settings saved, then reselect/reopen the same register and verify Enabled, environment, threshold, username/merchant/public-token evidence, and masked secret placeholder.",
        "Understand credential updates. A newly entered PayTomorrow password or Katapult key is written to its corresponding encrypted-named database column; a blank draft omits that field and preserves the prior value. The UI does not prove encryption-at-rest implementation, rotate a credential, revoke the old provider credential, or let you intentionally clear it. Verify those requirements with the authorized platform/provider owner.",
        "Apply to location appears only on the Katapult tab and only when the selected location has more than one register. PayTomorrow has no location-wide copy action. For Katapult, the action targets every other loaded register ID at the selected location; it does not resave the currently selected register. Save the current register first when its draft must also persist.",
        "Before Apply to location, confirm every target register, merchant account, environment, Enabled state, threshold, Merchant ID, Public Token, and API Key policy. There is no confirmation dialog. The operation launches one upsert per other register concurrently and is not all-or-nothing; one failure can leave a partial location rollout.",
        "If the Katapult API Key field is blank during Apply to location, the request omits the key update for each target, so an existing target key can remain rather than inheriting the selected register’s stored key. The function cannot read/copy the stored selected-register key from its masked placeholder. To intentionally align keys, enter the approved key during the controlled operation or use an authorized backend process, then verify every target separately.",
        "Wait for Katapult settings applied to all registers at this location or the failure message. In either case, open each register individually and inspect its Katapult state. A success toast proves the submitted upserts returned without error; it does not prove provider authentication. A failure requires a per-register audit before retrying because earlier concurrent writes may have succeeded.",
        "Run a controlled register matrix without using a real applicant: selected versus other register; Enabled/disabled; below, exactly at, and above the minimum; staging versus production test context; PayTomorrow versus Katapult; eligible sale channel; attached demo customer; and cancellation before external submission. Confirm only intended options appear.",
        "When authorized to test a real provider sandbox flow, use a designated provider-approved demo identity. Verify branded handoff, merchant/environment, requested amount, provider application ID, return/callback, CentriPOS receipt/application linkage, and no duplicate. Do not submit a credit or lease application for an uninformed real person.",
        "After launch, use Admin → Financing Apps for provider status, delivery/pickup evidence, PayTomorrow settlement, and funding lifecycle. Financing setup does not advance an application or prove funding. Reconcile provider records and rotate credentials under an approved process when staff, scope, or exposure changes.",
        "No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth page contains API signature, username, password, merchant reference, environment, and register-specific provider configuration, so the capture was rejected as credential-sensitive rather than redacted, invented, or replaced."
      ],
      "controls": [
        {
          "name": "Banknote icon",
          "description": "Exact CentriPOS Admin navigation and page icon for Financing."
        },
        {
          "name": "Location selector",
          "description": "Automatically starts at the first returned location by name; manually verify the intended scope."
        },
        {
          "name": "Register selector",
          "description": "Automatically starts at the first returned register for the selected location; provider settings are stored per register."
        },
        {
          "name": "PayTomorrow / Katapult",
          "description": "Independent provider tabs for the exact selected register."
        },
        {
          "name": "Connected",
          "description": "Field-presence indicator only: PayTomorrow API Username or Katapult Merchant ID exists."
        },
        {
          "name": "Enabled",
          "description": "Draft availability flag saved with the provider row; not a connection or approval test."
        },
        {
          "name": "PayTomorrow API Signature",
          "description": "Sensitive OAuth Basic-header value stored in the normal settings payload and loaded into browser state."
        },
        {
          "name": "API Username",
          "description": "PayTomorrow credential identity used as the Connected indicator."
        },
        {
          "name": "API Password",
          "description": "Sensitive PayTomorrow value; saved value is not repopulated and blank later saves preserve it."
        },
        {
          "name": "Merchant Reference ID",
          "description": "Optional PayTomorrow merchant reference in the merchant_id field."
        },
        {
          "name": "Katapult API Key",
          "description": "Sensitive value; saved value is not repopulated and blank later saves preserve it."
        },
        {
          "name": "Katapult Merchant ID",
          "description": "Required operational merchant identifier and Katapult Connected indicator."
        },
        {
          "name": "Public Token",
          "description": "Katapult checkout-widget token stored in the provider row and loaded into the browser field."
        },
        {
          "name": "Eye control",
          "description": "Reveals the newly entered secret or loaded PayTomorrow signature; use only in private."
        },
        {
          "name": "Minimum Cart Value",
          "description": "Whole-step numeric draft with no explicit finite/maximum/business-rule validation."
        },
        {
          "name": "Production / Staging",
          "description": "Stored environment selector; it does not validate credential/environment compatibility."
        },
        {
          "name": "Save provider settings",
          "description": "Upserts the selected tenant/register/provider only."
        },
        {
          "name": "Encrypted-named columns",
          "description": "Password/key destinations by schema name; the page itself does not prove encryption implementation or rotation."
        },
        {
          "name": "Apply to location",
          "description": "Katapult-only, no-confirmation concurrent upsert to every other register at the selected location."
        },
        {
          "name": "Selected-register exclusion",
          "description": "Apply to location does not save the currently selected register."
        },
        {
          "name": "Blank Katapult key during copy",
          "description": "Omits key changes and can leave each target’s existing key intact."
        },
        {
          "name": "Partial rollout risk",
          "description": "Concurrent target writes are not transactional; inspect every register after success or failure."
        },
        {
          "name": "Financing Apps",
          "description": "Separate lifecycle page for applications, delivery/pickup, settlement, and funding."
        },
        {
          "name": "No public screenshot",
          "description": "The approved real Harbor & Hearth financing page was rejected because it contains credential-bearing fields and provider/register configuration."
        }
      ],
      "expectedResult": "Only the intended provider appears on the exact register at the reviewed environment and cart threshold; credential ownership and provider authentication are independently verified, no secret is exposed, any Katapult location copy is audited register by register for partial or preserved-key differences, and a controlled provider-approved demo flow follows the correct merchant without creating a real customer obligation.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "financing-apps",
      "url": "https://platform.getcentri.com/centripos/financing-apps",
      "title": "Review and advance Financing Applications",
      "summary": "Filter tenant financing records, refresh one provider application at a time, submit irreversible Katapult delivery evidence, and initiate eligible PayTomorrow settlement.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Financing Apps uses the Banknote icon and can expose customer name, email, phone, requested/approved amounts, dates, provider identifiers, offer links, delivery state, and funding state. The approved Harbor & Hearth screenshot is an empty state only. Refresh All does not contact providers; it only refetches CentriPOS rows. Row-level Refresh status invokes the provider gateway. Never publish an applicant screenshot or copy financing data into an unsecured support channel.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Financing Apps in the intended business. Confirm the Banknote icon and Financing Applications heading. The list is tenant-scoped, newest first, and limited to the first 100 rows matching the current provider/status filters. There is no pagination or date search on this page.",
        "Use All providers, PayTomorrow, or Katapult. Use All statuses, Pending, Approved, Funded, Declined, or Cancelled. Error and Refunded records can display under All statuses but have no dedicated filter choice.",
        "Choose Refresh All when you only need to refetch current financing_applications rows from CentriPOS. This action does not call PayTomorrow or Katapult, does not show a progress state/toast, and may return the same stored values.",
        "Read each card carefully: customer name or email fallback, normalized provider badge, normalized status, optional raw provider-status code, delivery/pickup badge, requested amount, approved amount, created date/time, and external application ID. Customer email, phone, and delivery date can appear on the second row.",
        "Treat the normalized status and raw provider_status as different evidence. A provider code appears when it differs from the normalized CentriPOS status. Do not translate an unfamiliar raw code from memory; use the provider’s documented status or refresh that exact application.",
        "Choose the row-level circular Refresh status icon to invoke check_status on the application’s PayTomorrow or Katapult gateway. Wait for Status updated or an error, then allow the list to refetch. Do not repeatedly click while the row spinner is active.",
        "If an Open application external-link icon appears, it opens the saved offer_url in a new browser tab. Confirm the domain and intended applicant before proceeding. The page does not add noopener/noreferrer in this call, so avoid opening an untrusted or unexpected URL and report it to support.",
        "For Katapult only, Mark Delivered and Picked Up appear when the normalized status is Approved or Funded and no delivery_status exists. Verify the applicant, transaction, merchandise, actual delivery/pickup, amount, and date before choosing either action.",
        "In the Katapult confirmation dialog, review the customer and amount and set Delivery Date or Pickup Date. Blank defaults to today. The dialog explicitly says this notifies Katapult to initiate funding and cannot be undone. Choose Confirm once only when the real-world event occurred.",
        "Wait for the provider response and refreshed row after delivery submission. A toast is not sufficient financial evidence; verify the delivery badge, provider status, funding status, receipt/order, merchandise handoff, and provider portal as required. This page has no undo or correction workflow.",
        "For PayTomorrow, Settle / Fund appears only when provider_status is exactly S and settle_submitted_at is empty. The button invokes settlement immediately without a confirmation dialog. Verify eligibility and provider records before clicking.",
        "If PayTomorrow returns needs_dashboard, CentriPOS says settlement must be completed in the PayTomorrow merchant portal and that status was updated. Finish and verify there; do not treat the information toast as funded. Otherwise verify the Settlement submitted result against the provider and downstream funding evidence.",
        "Use No financing applications yet as a completed empty result for the active provider/status query. Clear both filters before concluding the tenant has no applications. Refresh All can confirm stored rows, but only configuration/provider diagnostics can explain a missing application.",
        "Configure credentials, environment, register scope, thresholds, and availability under Admin → Financing, not here. Financing Applications is a lifecycle screen; it does not edit API keys, merchant IDs, cart minimums/maximums, or register enablement."
      ],
      "controls": [
        {
          "name": "Banknote icon",
          "description": "Exact CentriPOS navigation and page icon for Financing Apps."
        },
        {
          "name": "Provider filter",
          "description": "All providers, PayTomorrow, or Katapult."
        },
        {
          "name": "Status filter",
          "description": "All statuses, Pending, Approved, Funded, Declined, or Cancelled; Error and Refunded remain All-only."
        },
        {
          "name": "100-row limit",
          "description": "Newest matching applications only; no pagination is provided."
        },
        {
          "name": "Refresh All",
          "description": "Refetches CentriPOS database rows only; it does not request provider status."
        },
        {
          "name": "Normalized status",
          "description": "CentriPOS status rendered as Pending, Approved, Funded, Declined, Cancelled, Error, or Refunded."
        },
        {
          "name": "Provider status badge",
          "description": "Raw provider_status code displayed when it differs from normalized status."
        },
        {
          "name": "Open application",
          "description": "Opens stored offer_url in a new tab; verify domain and applicant."
        },
        {
          "name": "Row Refresh status",
          "description": "Invokes check_status for that application through the provider-specific gateway."
        },
        {
          "name": "Requested / Approved amount",
          "description": "Financing values shown on the application card; protect as customer financial data."
        },
        {
          "name": "External application ID",
          "description": "Provider-facing reference displayed in monospace."
        },
        {
          "name": "Delivery badge",
          "description": "Delivered, Picked Up, or Delivery Pending when a delivery status exists."
        },
        {
          "name": "Mark Delivered / Picked Up",
          "description": "Katapult-only actions for eligible approved/funded applications without delivery status."
        },
        {
          "name": "Delivery/Pickup date",
          "description": "Defaults to today if blank; review before irreversible confirmation."
        },
        {
          "name": "Confirm delivery",
          "description": "Notifies Katapult and can initiate funding; cannot be undone from this screen."
        },
        {
          "name": "Settle / Fund",
          "description": "PayTomorrow-only immediate action when provider_status is S and no settlement submission time exists."
        },
        {
          "name": "needs_dashboard",
          "description": "Provider response requiring settlement completion in PayTomorrow merchant portal."
        },
        {
          "name": "No financing applications yet",
          "description": "Completed empty result for the active filters."
        },
        {
          "name": "Admin → Financing",
          "description": "Separate register/provider credential and threshold configuration."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/financing-apps in a fully rendered empty state. It exposes no applicant, delivery, funding, credit, customer, or provider-credential data."
        }
      ],
      "expectedResult": "The financing application belongs to the intended customer and sale, shows its current provider status once, and any approved amount is applied only through the authorized workflow.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-financing-apps.png",
        "alt": "Harbor & Hearth Financing Applications screen showing provider and status filters and the fully rendered empty application list in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-display",
      "url": "https://platform.getcentri.com/centripos/customer-display",
      "title": "Pair and manage a customer display",
      "summary": "Connect an installed checkout display or a temporary phone or tablet to the current open register, approve the device, and verify live customer-safe sale updates.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Customer Display is opened from the monitor icon in the operating-context bar and requires an open register session. The four-digit PIN expires after 10 minutes. Entering a PIN does not grant access by itself: the POS must approve the named device before it can view the sale.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "On the POS, choose the monitor-shaped Customer Display control in the operating-context bar. If the control is disabled or says Customer display unavailable, open the intended register session first. Pairing belongs to that active register session.",
        "Read the status before creating anything. Connected means a display is linked and checking in; Needs approval means a device entered the PIN and awaits POS confirmation; Disconnected means no display is linked; Error means an installed or temporary display stopped checking in or the service could not be reached.",
        "If no display is connected, choose Installed for a dedicated checkout screen that should reconnect automatically with this POS host, or Temp for a one-time phone or tablet. Choose New PIN when you intentionally need a fresh four-digit code. A new code replaces the pending connection for that mode; for Temp it also disconnects the prior temporary pairing for the session.",
        "On the display device, open https://pos.getcentri.com/customer-display. Give it a recognizable Display Name, choose Install on this checkout or Temporary join to match the POS mode, then enter the four-digit Connect PIN. You can instead scan the QR shown on the POS or open the copied branded pairing URL.",
        "The display changes to Waiting for Approval. On the POS, verify the device name, device ID suffix, and requested mode, then choose Confirm Install or Confirm Join. Do not approve a device you do not recognize. The display begins receiving customer data only after this confirmation.",
        "For an installed display, leave the display device on the Customer Display Ready screen when the register is closed or the trusted checkout host is inactive. It reconnects automatically when its linked POS host opens the register. Reset Link on the display removes that device’s installed trust and requires a new install.",
        "For a temporary display, the page remembers the active pairing on that browser and sends a keepalive while open. Disconnect Display ends the display-side connection. Temporary pairings are not a substitute for installing a dedicated checkout screen.",
        "Back on the POS, expand Display Management to review the primary device name, masked device ID, Installed display or Temporary display, current display mode, Live or Stale health, last-seen time, and the count of any additional attached devices. Refresh rechecks status without erasing links.",
        "Add a harmless test item to a new sale. Confirm the display shows the intended store and register, current receipt or waiting state, customer-safe cart items and totals, and a Live indicator. Change the cart once and verify the display updates. Do not use a live payment as the first connection test.",
        "The customer display can change modes when the POS workflow requests customer information, review and signature, or completion. Treat customer edits and signatures as real sale input; verify the customer and receipt before saving or signing.",
        "Use Clear all only when you intentionally want to remove every installed link, connected temporary display, and pending join associated with the current register. It marks installed links reset, removes their trusted device assignment, disconnects pending and connected temporary pairings, then generates a fresh connection flow.",
        "After setup, close and reopen the intended register or restart the display only if that behavior is part of the business’s normal device routine. Confirm an installed display reconnects to the same checkout and does not show another register’s cart."
      ],
      "controls": [
        {
          "name": "Customer Display control",
          "description": "Monitor icon in the POS context bar; enabled only for an open register session."
        },
        {
          "name": "Installed",
          "description": "Dedicated display trusted to the current checkout host and register so it can reconnect automatically."
        },
        {
          "name": "Temp",
          "description": "One-time display pairing for a spare phone or tablet."
        },
        {
          "name": "Connect PIN",
          "description": "Four-digit code valid for 10 minutes and tied to the active register session and selected connection mode."
        },
        {
          "name": "Pairing QR / Copy URL",
          "description": "Branded pos.getcentri.com customer-display link containing the current PIN and mode."
        },
        {
          "name": "Display Name",
          "description": "Human-readable device nickname shown to the POS before approval."
        },
        {
          "name": "Device ID",
          "description": "Masked suffix used with the device name to recognize the requested display."
        },
        {
          "name": "Waiting for Approval",
          "description": "The display entered a valid PIN but cannot view the live sale until the POS confirms it."
        },
        {
          "name": "Confirm Install",
          "description": "Approves and trusts the recognized display device for the checkout."
        },
        {
          "name": "Confirm Join",
          "description": "Approves the recognized temporary device for the current session."
        },
        {
          "name": "Connected",
          "description": "Display is linked and has checked in within the health window."
        },
        {
          "name": "Live / Stale",
          "description": "Health based on the display’s most recent check-in; stale means the screen has not checked in recently."
        },
        {
          "name": "Last seen",
          "description": "Age of the most recent device check-in."
        },
        {
          "name": "Display mode",
          "description": "Current cart, customer information, review/sign, completion, or supported scanner mode."
        },
        {
          "name": "Refresh",
          "description": "Rechecks status and pairing without clearing trusted links."
        },
        {
          "name": "New PIN",
          "description": "Expires the applicable pending flow and creates a new 10-minute code."
        },
        {
          "name": "Clear all",
          "description": "Resets all installed display links and disconnects pending or connected temporary pairings for the current register."
        },
        {
          "name": "Reset Link",
          "description": "Display-side action that removes installed trust for that device."
        },
        {
          "name": "Disconnect Display",
          "description": "Ends the current temporary display pairing and clears its browser pairing state."
        }
      ],
      "expectedResult": "The recognized display is explicitly approved for the intended open register, reports Live in Display Management, shows the correct store, register, and current customer-safe sale state, updates after a controlled cart change, and an installed device reconnects only to its trusted checkout host.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "integrations",
      "url": "https://platform.getcentri.com/centripos/integrations",
      "title": "Manage Integrations",
      "summary": "Read every storefront integration card, distinguish a real connection check from a capability label, and enter the correct provider workspace without authorizing or changing the wrong external account.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Integrations uses the Plug Zap icon. The Overview currently contains eight provider cards—CRM Connect, Wave Apps, CentriReviews Pro, QuickBooks Online, Dialpad, DispatchTrack, WooCommerce, and Shipping—plus a What lives here boundary card. Several badges are fixed capability labels rather than live connection tests, and the Overview performs status reads for only CRM Connect, CentriReviews, QuickBooks, Dialpad, and WooCommerce.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Integrations using the Plug Zap icon. Confirm the active CentriPOS business before reading a status or opening a provider. Every status request on this screen is tenant-scoped, but the external authorization page can still show a different company or account if the browser already has another provider session.",
        "Wait for Checking badges to resolve. CRM Connect, CentriReviews Pro, QuickBooks Online, Dialpad, and WooCommerce request live or stored status for the active tenant. Wave Apps, DispatchTrack, and Shipping do not request their connection status from this Overview; their Independent connector, Optional, and EasyPost badges describe product role only.",
        "Read CRM Connect. Its live badge is Connected when the returned connection status equals connected, Configured when a connection row exists with another status, and Not connected when no row exists. The card always describes Connection type as Server token now, OAuth-ready; that text is architecture guidance, not connection proof.",
        "Choose Manage CRM Connect to open the tenant connection editor. Do not paste a private integration token into support notes or screenshots. Verify the display name, exact external location ID, configured secret status, direction, field behavior, and one known contact/touchpoint before broader synchronization.",
        "Read Wave Apps as an independent connector for closed register reports. The Overview always shows Independent connector and describes sales, tax, discounts, returns, deposits, and the EPX Payment Processing Fee; it does not prove a Wave business is authorized or mapped. Choose Manage Wave Apps and use that screen’s status before sending anything.",
        "Read CentriReviews Pro. Connected requires its returned connection status to equal connected; another stored connection status is displayed with underscores converted to spaces; no connection shows Not connected. Location mappings is the number returned for this tenant, and Per-location provider routing describes the model. Choose Manage CentriReviews for the actual connection, mappings, request, and review-sync controls.",
        "Read QuickBooks Online. The badge is Connected only when the tenant integration row reports active. When inactive, the card offers Connect QuickBooks directly from Overview; that action requests an authorization URL and leaves CentriPOS for the provider sign-in. When active, Settings and Open QuickBooks both enter the CentriPOS QuickBooks detail workspace—they do not directly open a QBO company page from this card.",
        "Before choosing Connect QuickBooks, confirm the intended QBO company, authorized administrator, accounting owner, mapping plan, and rollback approach. On return, verify the CentriPOS tenant and QBO company identity, then refresh reference options and configure mappings in the provider workspace. A successful OAuth return is not proof that receipts or register reports have posted.",
        "Read Dialpad. Connected requires an active returned integration; the card separately shows the number of synced phone-number records. Live SMS and calls is a capability description, not evidence that a particular number, user assignment, webhook, or historical import is ready. Choose Manage Dialpad for the exact connection and number controls.",
        "Read DispatchTrack. Optional and External routing layer are fixed descriptions. Built-in center still primary means CentriPOS Fulfillment Center remains the operational base. Choose Manage DispatchTrack to inspect its actual credential, connection, location mapping, sync, and dispatch behavior before sending delivery data.",
        "Read WooCommerce. Connected requires is_enabled from the returned tenant integration. Store shows the returned store URL or Ready to connect; Order lifecycle: OAuth, webhooks, polling describes supported mechanisms. Choose Manage WooCommerce and verify the exact site URL, environment, webhooks, polling, catalog/location mapping, and a controlled order before enabling broader flow.",
        "Read Shipping. EasyPost, Carrier rates and labels, and Retailer-owned account are fixed product descriptions on Overview—not connection status. Choose Manage Shipping to see the actual status, Test or Live mode, last verification, error, and password-masked retailer-owned API-key field. This built-in shipping connection is independent of WooCommerce Shipping.",
        "Use What lives here as a security boundary. Store-facing provider connections belong in Integrations. Platform-wide credentials such as Mapbox, mail delivery, and provider application credentials belong in restricted Platform API Keys and are not customer-storefront settings. Do not request or copy a platform credential to make a tenant card look connected.",
        "After an authorized connection or setting change, run one small provider-specific test and verify both ends: tenant/business, external account, location/register scope, source record, direction, mapped fields, timestamps, identifiers, duplicates, errors, and rollback. A green card badge alone is never end-to-end proof.",
        "For a mismatch, capture the active CentriPOS business, provider card, visible safe status, intended external account, approximate time, safe record/reference, direction, and exact error. Stop repeated authorization or sync attempts until the tenant and provider identities are reconciled. Never share access tokens, API keys, OAuth codes, webhook secrets, customer private data, or accounting credentials.",
        "The screenshot is the real Amelia Grant Harbor & Hearth /admin/integrations Overview at 1440 × 900. It shows only provider capability and safe connection-status cards; no credentials, account identifiers, OAuth dialogs, mappings, or management screens are exposed."
      ],
      "controls": [
        {
          "name": "Plug Zap icon",
          "description": "Exact CentriPOS navigation icon for Admin → Integrations."
        },
        {
          "name": "Eight provider cards",
          "description": "CRM Connect, Wave Apps, CentriReviews Pro, QuickBooks Online, Dialpad, DispatchTrack, WooCommerce, and Shipping."
        },
        {
          "name": "Checking",
          "description": "A tenant-scoped status request is still loading for a provider that Overview actually queries."
        },
        {
          "name": "CRM Connect Connected",
          "description": "Returned connection status is exactly connected."
        },
        {
          "name": "CRM Connect Configured",
          "description": "A connection row exists but its returned status is not connected."
        },
        {
          "name": "Server token now, OAuth-ready",
          "description": "Fixed connection-model description; not a live readiness result."
        },
        {
          "name": "Independent connector",
          "description": "Fixed Wave Apps product-role badge; inspect the Wave workspace for actual connection status."
        },
        {
          "name": "CentriReviews status",
          "description": "Connected or the returned stored status; Not connected when no connection exists."
        },
        {
          "name": "Location mappings",
          "description": "Count of returned CentriReviews location-routing rows."
        },
        {
          "name": "QuickBooks Connected",
          "description": "The tenant QBO integration row reports is_active."
        },
        {
          "name": "Connect QuickBooks",
          "description": "Starts external QBO authorization directly from Overview when inactive."
        },
        {
          "name": "QuickBooks Settings / Open QuickBooks",
          "description": "Both enter the CentriPOS QBO detail workspace from this card."
        },
        {
          "name": "Dialpad Connected",
          "description": "Returned Dialpad integration reports active."
        },
        {
          "name": "Synced numbers",
          "description": "Count of returned Dialpad number records, not proof every user can send or call."
        },
        {
          "name": "DispatchTrack Optional",
          "description": "Fixed capability badge; not a connection check."
        },
        {
          "name": "WooCommerce Connected",
          "description": "Returned tenant integration reports is_enabled."
        },
        {
          "name": "WooCommerce Store",
          "description": "Returned store URL or Ready to connect."
        },
        {
          "name": "Shipping EasyPost",
          "description": "Fixed provider badge; actual status, mode, verification, and errors live in Manage Shipping."
        },
        {
          "name": "What lives here",
          "description": "Separates storefront connections from restricted platform-wide application credentials."
        },
        {
          "name": "Manage action",
          "description": "Opens the named provider workspace under /admin/integrations/<provider>."
        },
        {
          "name": "Controlled verification",
          "description": "One known workflow checked in both CentriPOS and the exact external account."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real loaded provider-status Overview with no credentials, account IDs, OAuth dialogs, or management screens."
        }
      ],
      "expectedResult": "The integration card reports the expected connection state, and one known record follows the configured data direction and mapping.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-integrations.png",
        "alt": "Harbor & Hearth Integrations screen showing CRM, reputation, accounting, phone, and collaboration connection status in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "crm-connect",
      "url": "https://platform.getcentri.com/centripos/crm-connect",
      "title": "Configure and verify CRM Connect",
      "summary": "Map one CentriPOS business to the correct LeadConnector/HighLevel location, reference its tenant-specific server secret, verify connection status, and test controlled customer/timeline synchronization.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "This is a tenant-wide technical configuration screen. It stores a display label, external CRM location ID, and the name of a server-side secret; it must never contain the raw token. Save CRM sync currently enables the supported calls, SMS, chats, and emails sync flags together—there are no individual sync toggles on this page. Each CentriPOS business needs its own correct location mapping and credential reference; never reuse another customer’s fixed-location connection.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Confirm the active CentriPOS business and the exact CRM/HighLevel sub-account that belongs to it. Obtain the external Location ID from an approved administrator and independently verify the business name/address or account ownership. A syntactically valid location ID can still point customer data to the wrong account.",
        "Have an authorized platform administrator create a uniquely named server secret containing this business’s approved LeadConnector private-integration token with the required scopes. The raw token belongs in the secure server secret store, never in CentriPOS fields, screenshots, chat, email, tickets, or documentation.",
        "Go to Admin → Integrations → CRM Connect. Before editing, read the status badge and summary cards: Contact location, Credential, and Secret present. Not connected, Configured/another status, Connected, Missing, or Not checked describe configuration evidence—not proof that customer records are synchronizing correctly.",
        "Enter a clear Display name, usually CRM Connect or a business-specific administrative label. This label identifies the connection in CentriPOS; it does not rename the external CRM location.",
        "Enter the exact CRM Connect location ID for this CentriPOS tenant. Do not use the current POS location/register ID: this field expects the external CRM sub-account/location identifier. Remove copied spaces and verify every character.",
        "Enter only the Token environment variable name created for this tenant, such as a uniquely named CENTRICRM_…_TOKEN reference. Do not paste the token value. Treat even the environment-variable name as internal configuration and omit it from public screenshots.",
        "Choose Save CRM sync once and wait. CentriPOS upserts the tenant connection with the display name, trimmed external location ID, secret-name reference, and calls/SMS/chats/emails sync flags enabled. Success shows CRM Connect integration saved and refreshes the status summary.",
        "Re-read Contact location, Credential, Secret present, and the status badge after save. Secret present must be Yes before expecting authentication to work. If it says Missing, correct the server secret deployment/reference rather than pasting a token into the field.",
        "Choose Test connection only after a connection record exists; the control is disabled otherwise. Wait for CRM Connect connection verified. This tests server authentication against the saved mapping, then refreshes status. It does not prove that every contact field, receipt, note, message, owner, tag, or custom field maps correctly.",
        "Run a controlled, privacy-safe data test in a designated demo/test customer such as the approved Harbor & Hearth demo—not a real customer. Create or update one distinctive non-sensitive field and verify it lands in the intended external CRM location without creating a duplicate. Record which system is authoritative for each tested field.",
        "Test the customer timeline separately. Add a controlled note or refresh CRM Connect activity where supported and verify direction, timestamp, author/owner, body, external identity, and deduplication. CentriPOS can warn Note saved, but CRM Connect sync needs review: that means the local note succeeded while external sync needs reconciliation, not that the whole save failed.",
        "Test communication sender behavior only when assigned CRM Connect lines exist. In the customer communication card, confirm the sender provider label and number before SMS. CRM Connect sender availability is user-assignment dependent; it does not make the Dialpad-only Call button available.",
        "Verify broader supported outcomes deliberately: contact identity/type, phone/email/address, customer-since, assigned owner, tags/custom-field mapping, receipts, notes, interactions, CRM activity, Dialpad calls/SMS, and smart-list/contact-search behavior. The page describes future email conversations, so do not represent future/placeholder coverage as proven production sync.",
        "If data reaches the wrong CRM location, stop synchronization immediately and escalate as a cross-tenant incident. Preserve the CentriPOS tenant, external location ID, connection label/status, affected demo/contact identifiers, operation/time, and direction. Never include raw tokens. Correct the mapping and assess already-sent records before resuming.",
        "If Test connection fails, check the saved location ID, exact environment-variable reference, Secret present state, token scopes/expiration/revocation, server deployment, and external service status. Do not swap in another tenant’s token as a shortcut."
      ],
      "controls": [
        {
          "name": "Status badge",
          "description": "Checking, Connected, Not connected, Configured/another stored status; connection state is not field-level sync proof."
        },
        {
          "name": "Contact location",
          "description": "Saved external LeadConnector/HighLevel Location ID, not the CentriPOS store/location selector."
        },
        {
          "name": "Credential",
          "description": "Name of the server environment secret referenced by the connection; it is not the raw token and should remain internal."
        },
        {
          "name": "Secret present",
          "description": "Server-reported Yes/Missing/Not checked signal for whether the referenced secret exists. It does not reveal or validate the token by itself."
        },
        {
          "name": "Display name",
          "description": "Friendly administrative label stored for this tenant connection."
        },
        {
          "name": "CRM Connect location ID",
          "description": "Required external CRM sub-account/location destination for this CentriPOS business."
        },
        {
          "name": "Token environment variable",
          "description": "Required server-secret name. Raw secret values never belong in this field."
        },
        {
          "name": "Save CRM sync",
          "description": "Upserts the connection and currently submits calls, SMS, chats, and emails sync flags as true together."
        },
        {
          "name": "CRM Connect integration saved",
          "description": "Configuration write succeeded and status is refetched; follow with Test connection and controlled data verification."
        },
        {
          "name": "Test connection",
          "description": "Available only after a saved connection exists; tests authentication/mapping against the server service."
        },
        {
          "name": "CRM Connect connection verified",
          "description": "Connection test succeeded; it is not proof of every object/field/timeline workflow."
        },
        {
          "name": "Contacts card",
          "description": "Describes identity, type, customer since, owner, tags, and custom-field mapping intent."
        },
        {
          "name": "Timeline card",
          "description": "Describes receipts, notes, interactions, Dialpad calls/SMS, and CRM activity in one customer journey."
        },
        {
          "name": "Smart lists card",
          "description": "Describes CRM-style contact filters and LeadConnector contact-search synchronization."
        },
        {
          "name": "Partial-success note warning",
          "description": "A local note saved while CRM Connect sync failed or needs review; reconcile rather than duplicating the note."
        },
        {
          "name": "Assigned CRM Connect sender",
          "description": "User-available line for supported SMS; sender assignment and provider must be confirmed in the customer profile."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains a safe Integrations overview but no exact CRM Connect configuration page. This guide intentionally does not expose or invent a location ID or secret reference."
        }
      ],
      "expectedResult": "The intended CentriPOS contact and activity fields map to the authorized CentriCRM location, and one controlled record syncs once in the configured direction.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "wave-apps",
      "url": "https://platform.getcentri.com/centripos/wave-apps",
      "title": "Configure Wave Apps",
      "summary": "Authorize one Wave business, map closed-register accounting concepts, and manually send eligible register reports without changing the independent QuickBooks workflow.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "Open Admin → Integrations → Wave Apps. The Integrations navigation uses the Plug Zap icon; the Wave Apps tab and page use the Book Open icon. The current connector sends closed register reports only. It is independent of QuickBooks, does not sync products or customers, and does not offer automatic sync yet.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin → Integrations and choose Wave Apps, or select Manage Wave Apps from the Integrations overview. Confirm the active CentriPOS business before authorizing anything.",
        "Read the Wave connection badge. Checking means status is still loading; Not connected shows Connect Wave; Connected shows Refresh Wave accounts.",
        "Choose Connect Wave. Sign in to the intended Wave account, authorize only the intended business access, and allow Wave to return to the branded CentriPOS callback page. Do not share OAuth callback parameters or access tokens.",
        "After connection, choose Refresh Wave accounts. This reloads the accessible Wave businesses and account reference list. A connected badge alone does not prove the intended Wave business is selected.",
        "Choose Wave business. Selecting a business immediately refreshes its available accounts and stores the returned business ID and name in the current settings state. Verify the exact business name before mapping.",
        "Map Register deposits / clearing to the account that should receive the register-report balancing or deposit amount.",
        "Map Sales income, Discounts, Returns and refunds, and Sales tax payable to the matching Wave accounts approved by the business’s accountant. Do not choose an account only because its name looks similar.",
        "Map EPX payment processing fees to the intended Wave expense account. Reconciled processor fees are labeled EPX Payment Processing Fee in the Wave register-report workflow.",
        "Turn Enable Wave register reports on only after the Wave business and every required account mapping are reviewed. This allows authorized users to send closed register reports to Wave.",
        "Read Automatic sync as unavailable. Its switch is disabled and the description says it is reserved for eligible closed reports after processor reconciliation. Current use is manual from a closed register report.",
        "Choose Save Wave settings and wait for Wave register-report settings saved. Saving is unavailable until the account reference list has loaded.",
        "Close one controlled register session, then open its register closure report. In the Wave Apps card, Not enabled means the connector or register-report option is off; Ready means it can be sent; Synced shows the last successful send time.",
        "Choose Send to Wave only after the register is closed and its sales, tax, discounts, returns, deposits, and reconciled processor-fee evidence have been reviewed. The button remains disabled while the session is open.",
        "Wait for Register report sent to Wave, then open the resulting Wave record and confirm the business, date, description, accounts, debit/credit direction, and total. Do not use QuickBooks history as proof of the Wave result; their settings and sync records are separate.",
        "If the report already shows Synced, the action becomes Resend to Wave. A forced resend can create or update accounting effects depending on the connector response, so compare the existing Wave record and last sync before using it.",
        "If CentriPOS says This report is already in Wave, treat that as an idempotent result and do not keep retrying. If a red last error appears, preserve the closure ID, Wave business name, time, and safe error text for support without including tokens or private account credentials."
      ],
      "controls": [
        {
          "name": "Plug Zap icon",
          "description": "Admin navigation icon for the Integrations area."
        },
        {
          "name": "Book Open icon",
          "description": "Tab, overview-card, and page icon for Wave Apps."
        },
        {
          "name": "Wave connection badge",
          "description": "Checking, Connected, or Not connected authorization state for the current CentriPOS tenant."
        },
        {
          "name": "Connect Wave",
          "description": "Starts Wave OAuth authorization and returns to Admin → Integrations → Wave Apps."
        },
        {
          "name": "Refresh Wave accounts",
          "description": "Reloads Wave businesses and account references for the authorized connection."
        },
        {
          "name": "Wave business",
          "description": "Exact Wave organization that will receive manually sent register reports."
        },
        {
          "name": "Register deposits / clearing",
          "description": "Wave account mapped to the register-report balancing or deposit concept."
        },
        {
          "name": "Sales income",
          "description": "Wave income account for included closed-register sales."
        },
        {
          "name": "Discounts",
          "description": "Wave account for discounts represented by the closure."
        },
        {
          "name": "Returns and refunds",
          "description": "Wave account for return and refund activity represented by the closure."
        },
        {
          "name": "Sales tax payable",
          "description": "Wave liability account for sales tax represented by the closure."
        },
        {
          "name": "EPX payment processing fees",
          "description": "Wave expense account for reconciled processor fees labeled EPX Payment Processing Fee."
        },
        {
          "name": "Enable Wave register reports",
          "description": "Allows authorized users to send eligible closed register reports manually."
        },
        {
          "name": "Automatic sync",
          "description": "Disabled reserved setting; automatic register-report sending is not currently available from this screen."
        },
        {
          "name": "Save Wave settings",
          "description": "Persists selected business, mappings, and enabled state after Wave account references load."
        },
        {
          "name": "Wave settings",
          "description": "Link on a closure report that returns to this integration page."
        },
        {
          "name": "Not enabled",
          "description": "Closure card state when Wave register-report sending is not enabled."
        },
        {
          "name": "Ready",
          "description": "Closed report is eligible for the manual Send to Wave action."
        },
        {
          "name": "Synced",
          "description": "A successful Wave sync record exists and its last-sent timestamp is shown."
        },
        {
          "name": "Send to Wave",
          "description": "Manually sends an eligible closed register report using the saved Wave business and account mappings."
        },
        {
          "name": "Resend to Wave",
          "description": "Forces another send attempt for a report already marked sent; review the existing Wave result first."
        },
        {
          "name": "Last error",
          "description": "Most recent sync failure shown on the closure’s Wave Apps card."
        },
        {
          "name": "QuickBooks boundary",
          "description": "Wave authorization, mappings, enablement, and sync history are independent of QuickBooks Online."
        }
      ],
      "expectedResult": "The intended Wave business is connected, every register-report concept maps to an accountant-approved Wave account, manual sending is enabled while Automatic sync remains unavailable, and one reviewed closed register report reaches Wave once with the expected accounts and total while its CentriPOS card records Synced and the send time independently of QuickBooks.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "shipping-integration",
      "url": "https://platform.getcentri.com/centripos/shipping-integration",
      "title": "Connect EasyPost shipping",
      "summary": "Connect the retailer-owned EasyPost account used by CentriPOS built-in shipping, distinguish Test from Live mode, and verify the stored connection status without exposing the API key.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "This screen supports EasyPost only. It is separate from WooCommerce Shipping and from Admin → Fulfillment Methods → Shipping, where customer-facing shipping methods, prices, tax, and scheduling are configured. The current integration screen has Connect but no separate Test connection, Disconnect, carrier-account, ship-from address, rate, label, tracking, or postage-purchase controls. Do not promise those controls from this page.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Create or select the retailer’s own EasyPost account and obtain an EasyPost API key through the retailer’s approved credential process. Do not use a Centri developer account, another retailer’s key, a key copied from logs, or a credential supplied in chat/email.",
        "Confirm the active CentriPOS business and that you are authorized to change tenant-wide integrations. Go to Admin → Integrations → Shipping. Verify the page heading is Shipping and the provider card says EasyPost and EasyPost only. WooCommerce Shipping stays outside this workflow.",
        "Read the current status badge before changing anything. Also review Provider, Mode, Last verified, and any visible Last error. Capture the status and timestamp without exposing credentials so you can tell whether a new connection changed the state.",
        "Choose Mode deliberately. Use Test with a matching EasyPost test key while validating setup without real postage. Use Live only with the retailer’s live key and explicit approval for production shipping. The selected mode and key must belong together; choosing Live does not convert a test key.",
        "Paste the retailer-owned EasyPost API key into the password field. The existing key is not displayed back to the browser. Re-entering a key and choosing Connect is a credential replacement/connection action, not a harmless status refresh.",
        "Choose Connect once and wait. CentriPOS sends the tenant, trimmed key, selected mode, and account label EasyPost to the secure shipping connection service. If the field is blank, the page shows Enter an EasyPost API key.",
        "On success, wait for EasyPost connected. The key field clears and the status query refreshes. Confirm the status badge, stored Mode, and Last verified time changed as expected. A status of connected or test receives the active badge styling; read the actual text rather than inferring production readiness from color.",
        "If connection fails, read the displayed error or Last error. Recheck key environment, ownership, revocation/permissions, selected mode, tenant context, and service availability. Do not repeatedly paste credentials or switch to Live merely to make a test failure disappear.",
        "Configure the customer-visible shipping choices separately in Admin → Fulfillment Methods → Shipping. Define only the enabled methods, names, base prices, tax behavior, and schedule/capacity rules the business actually offers. Connecting EasyPost does not create those choices or a ship-from address on this page.",
        "Run an authorized end-to-end test from the actual shipping workflow after both configuration areas are ready. In Test mode, use a controlled noncustomer test address/order and confirm the correct business/location context and expected provider behavior. In Live mode, obtain approval before any action that could buy postage. The connection page itself does not provide a rate or label test button.",
        "Verify downstream evidence only where the relevant shipping workflow exposes it: correct ship-to and intended ship-from context, selected shipping method, rate/postage environment, label/tracking identity, and fulfillment/receipt record. Do not assume Last verified proves a particular shipment, carrier, label, or tracking event.",
        "If production behavior is wrong, stop live postage actions and report the tenant, mode, status, Last verified, Last error, affected workflow, time, and privacy-safe identifiers. Never include the EasyPost API key, full customer address, or unredacted label."
      ],
      "controls": [
        {
          "name": "EasyPost",
          "description": "Only provider available on the CentriPOS Shipping integration page. Retailers use their own account; CentriPOS does not resell postage."
        },
        {
          "name": "Status badge",
          "description": "Current connection state returned by the server, such as Not connected, test, connected, or another status string."
        },
        {
          "name": "Provider",
          "description": "Displays EasyPost only; it is not a carrier selector."
        },
        {
          "name": "Mode summary",
          "description": "Stored mode returned by the connection status, or Not set."
        },
        {
          "name": "Last verified",
          "description": "Last server-reported verification timestamp; it does not prove a specific rate, label, or shipment."
        },
        {
          "name": "Last error",
          "description": "Most recent connection/service error returned for this integration when present."
        },
        {
          "name": "Mode → Test",
          "description": "Stores a test-mode connection; pair it with the retailer’s EasyPost test key."
        },
        {
          "name": "Mode → Live",
          "description": "Stores a production-mode connection; pair it with the retailer’s live key and approval for postage-capable workflows."
        },
        {
          "name": "EasyPost API key",
          "description": "Password-style input for a retailer-owned key. Existing secret material is not displayed in the status card."
        },
        {
          "name": "Connect",
          "description": "Saves/replaces the connection using the selected mode and entered key; no separate Test connection button exists on this screen."
        },
        {
          "name": "EasyPost connected",
          "description": "Save succeeded, key input clears, and status is refetched."
        },
        {
          "name": "WooCommerce separation",
          "description": "WooCommerce Shipping is configured and operated outside the built-in EasyPost workflow."
        },
        {
          "name": "Fulfillment Methods → Shipping",
          "description": "Separate place for enabled customer-visible shipping methods, names, base prices, tax treatment, and shipping scheduling."
        },
        {
          "name": "Not on this screen",
          "description": "No Disconnect, carrier account, package preset, ship-from address, rate request, label purchase/void, tracking, or postage history controls are exposed here."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains an Integrations overview capture but no exact Shipping/EasyPost credential page. This guide intentionally avoids a mismatched screenshot and never depicts a real key."
        }
      ],
      "expectedResult": "The authorized carrier or shipping service returns the intended rates and labels for a controlled shipment and writes tracking back to the correct fulfillment record.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "dispatchtrack-integration",
      "url": "https://platform.getcentri.com/centripos/dispatchtrack-integration",
      "title": "Configure DispatchTrack",
      "summary": "Connect DispatchTrack Planner to CentriPOS, verify the saved credentials, and send eligible local-delivery sales from the Fulfillment Center.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "Open Admin → Integrations → DispatchTrack using the Truck icon. This screen saves one tenant-level connection unless a location-specific connection is opened by another supported workflow. CentriPOS remains the fulfillment source of truth; the current customer-visible setup does not contain field-mapping, service-mapping, truck, driver, route-status, or proof-of-delivery controls.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Integrations → DispatchTrack. The status badge reads Checking while CentriPOS loads, then Not connected when no settings exist, Saved when credentials are stored but not verified, or Connected after a successful connection test.",
        "Get the Planner API base URL, API key name, API key secret, and—when inbound delivery updates are being configured—the shared webhook token from the authorized DispatchTrack account administrator. Do not paste credentials into a support ticket or screenshot.",
        "Enter Planner API base URL. The example format is https://planner-youraccount.dispatchtrack.com/external_api; use the exact account URL supplied by DispatchTrack rather than copying the placeholder.",
        "Enter API key name and API key secret. All three connection fields—base URL, key name, and key secret—must contain values before Save connection is enabled. The secret field is masked.",
        "Enter Webhook token only when the DispatchTrack webhook has been configured to send the same shared header token to the branded CentriPOS webhook endpoint. The field is masked and is not required merely to enable Save connection.",
        "Choose whether to enable Auto-export eligible local deliveries. The screen explains that manual export remains available from fulfillment. Enable automatic export only after the controlled manual workflow has been proven for this tenant.",
        "Choose Save connection. Saving encrypts the API key name and secret and stores only credential previews for the browser. A successful save reports DispatchTrack settings saved and changes the badge from Not connected to Saved until the connection is verified.",
        "After a save, read Saved key and Updated to confirm which key name is represented and when the settings last changed. CentriPOS does not display the stored key secret or webhook token again.",
        "Choose Test connection. This control is disabled until settings exist. CentriPOS uses the saved credentials to request the DispatchTrack places endpoint; success reports DispatchTrack connection verified and changes the status to Connected. A failure leaves the connection unverified and shows the returned safe error message.",
        "Open Sales → Fulfillment Center and select the Delivery route for a date containing an eligible local-delivery sale. When DispatchTrack is connected, the route area shows DispatchTrack connected and each delivery stop exposes a DispatchTrack button with the External Link icon.",
        "For the first test, choose DispatchTrack on exactly one controlled delivery stop. CentriPOS groups that sale’s active local-delivery fulfillment lines, requires a customer delivery address, and sends the sale as one DispatchTrack stop group. Success reports Delivery sent to DispatchTrack.",
        "Confirm the correct customer name, phone, delivery address, sale reference, fulfillment items, quantities, and delivery instructions in the authorized DispatchTrack account. Do not repeat the export because the external screen is slow; the export uses the sale as an idempotent reference, and any failure is recorded for investigation.",
        "Continue to manage the sale, line-item fulfillment status, cancellations, returns, and customer record in CentriPOS. DispatchTrack supplies external planning and delivery execution; it does not replace the CentriPOS receipt or fulfillment record.",
        "If Test connection fails, first recheck the full account-specific base URL and whether the key name and secret belong together. Save the corrected credentials before testing again. If delivery export fails after a healthy test, verify that the sale is a local delivery, still has active fulfillment lines, and has a complete delivery address; then give support the safe sale number and exact error text, never the credentials.",
        "If the connection should be rotated, enter the complete new base URL, key name, key secret, and applicable webhook token, save once, and test once. There is currently no Disconnect button on this screen, so contact CentriPOS support when the integration must be disabled or removed rather than entering dummy credentials."
      ],
      "controls": [
        {
          "name": "Truck icon",
          "description": "The exact CentriPOS navigation and page icon for DispatchTrack."
        },
        {
          "name": "Status badge",
          "description": "Checking, Not connected, Saved, or Connected according to the stored settings and most recent successful verification."
        },
        {
          "name": "Planner API base URL",
          "description": "Account-specific DispatchTrack external API root; the visible URL is an example, not a universal endpoint."
        },
        {
          "name": "API key name",
          "description": "Name paired with the authorized DispatchTrack API secret. After saving, its preview appears as Saved key."
        },
        {
          "name": "API key secret",
          "description": "Masked DispatchTrack credential. It is encrypted when saved and is not returned to the browser."
        },
        {
          "name": "Webhook token",
          "description": "Optional masked shared token used to authenticate configured inbound DispatchTrack webhooks. It is not the API key secret."
        },
        {
          "name": "Auto-export eligible local deliveries",
          "description": "When enabled, marks the connection for automatic export behavior; manual export remains available from fulfillment. Prove manual export first."
        },
        {
          "name": "Save connection",
          "description": "Enabled only when base URL, key name, and key secret are present. It stores credentials and connection flags but does not by itself prove the remote account is reachable."
        },
        {
          "name": "Saved key / Updated",
          "description": "Safe credential-name preview and last settings timestamp; neither reveals the stored secret."
        },
        {
          "name": "Test connection",
          "description": "Uses the saved credentials against the DispatchTrack places endpoint. It is disabled until settings exist."
        },
        {
          "name": "DispatchTrack connected",
          "description": "Fulfillment-route notice shown when the saved connection is verified."
        },
        {
          "name": "DispatchTrack stop button",
          "description": "External Link action on an eligible delivery stop that sends the sale and its active local-delivery lines to DispatchTrack."
        },
        {
          "name": "Delivery sent to DispatchTrack",
          "description": "Successful manual-export confirmation. Verify the external stop before sending anything else."
        },
        {
          "name": "CentriPOS source of truth",
          "description": "Sales, fulfillment eligibility and line status, customer context, returns, refunds, and audit history remain in CentriPOS."
        },
        {
          "name": "Not present on this screen",
          "description": "There are no customer-visible field maps, service maps, driver or truck selectors, route-status maps, proof-of-delivery settings, retry log, or Disconnect button in the current interface."
        }
      ],
      "expectedResult": "The status badge reads Connected, one controlled local-delivery sale is sent once from Fulfillment Center, and the resulting DispatchTrack stop matches the CentriPOS customer, address, sale reference, fulfillment items, quantities, and instructions without exposing credentials or inventing configuration controls that are not present.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "online-store-settings",
      "url": "https://platform.getcentri.com/centripos/online-store-settings",
      "title": "Configure the Online Store",
      "summary": "Configure the exact storefront location and register, branded URL, verified domains, identity, SEO, colors, publishing state, and controlled website embedding behavior.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → Online store uses the Globe icon. Page fields are drafts until Save changes, but custom-domain add, use-scope changes, verification, and removal write separately and immediately. Keep every shared customer destination on https://pos.getcentri.com or a verified customer domain routed through the branded service; never publish a Supabase project, Edge Function, storage, or project-reference URL. The real Harbor & Hearth screenshot shows untouched placeholder settings and no private identifier or verified domain.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Online store using the Globe icon. Confirm the heading says Online store and the description says Configure your storefront, domains, and embed widget.",
        "Leave Store published off while configuring. The switch changes the page draft; the public state changes only after Save changes succeeds. Do not publish until the catalog, location/register, domain, identity, tax, fulfillment, payment, and checkout tests are complete.",
        "Under Inventory source, choose the exact Location whose recorded inventory feeds the storefront and against which online sales are recorded. Changing Location clears the selected Register in the draft.",
        "After choosing a Location, choose a Register from that location. Online orders are recorded on this register for register reports. Confirm the register’s taxes, payments, fulfillment settings, numbering, restrictions, and reporting behavior before launch.",
        "Under Platform URL, enter Store slug using only lowercase letters, numbers, and hyphens. Typing removes other characters; Save also trims and normalizes the value. The slug must be unique across every storefront tenant.",
        "Review the complete https://pos.getcentri.com/store/<slug> link shown after a slug exists. Use its external-link action for a controlled preview and Copy only when the branded hostname, merchant, and published state are correct. A saved slug is not by itself a published store.",
        "If Save reports that the slug is already in use, choose a distinct approved variation. Do not imitate another merchant’s domain or add customer/private data to the slug. An empty slug can be saved but provides no usable platform storefront address.",
        "Under Custom domains, enter a customer-facing hostname such as shop.yourdomain.com or pay.yourdomain.com—without a scheme or path—and choose Store + links, Links only, or Store only. The current mobile layout hides this use selector while adding and defaults to Store + links, so verify the resulting row afterward.",
        "Choose Add domain once. This immediately creates a Pending domain with a verification token and SSL pending-validation state; it is not part of Save changes. The first domain added becomes Primary automatically. Adding the hostname does not prove DNS ownership or make it safe to share.",
        "Publish the exact CNAME and TXT records displayed for that Pending domain in the customer’s DNS. Use the Copy controls to avoid transcription errors, but review the hostname and target before saving DNS. If verification returns an additional Cloudflare ownership CF TXT record, add that exact record too.",
        "Choose Verify after DNS propagation. Read the separate CNAME found/missing, TXT found/missing, and SSL active/pending results. DNS can be verified while SSL is still pending; wait for the certificate before sharing an HTTPS customer link.",
        "Read the row badges and SSL text. Verified confirms the current ownership and SSL checks; Pending does not. Primary identifies the first/current primary row but this screen exposes no separate Make primary control.",
        "Change Use for only after reviewing all affected surfaces. Storefront + customer links can cover the store plus supported e-cart, pay, and receipt magic links; Customer links only excludes the storefront; Storefront only excludes those customer-link surfaces. This selector saves immediately and reports Domain use updated.",
        "Use Trash only after resolving the exact hostname and its customer use. Removal writes immediately with no confirmation dialog in this component and can break bookmarks, emails, texts, receipts, e-carts, pay links, or storefront traffic. Preserve or redirect active public paths before removal.",
        "Under General, enter the customer-facing Store name. Choose the Company ID type—EIN, VAT, GST/HST, ABN, ACN, NZBN, company registration number, UTR, CNPJ, RFC, Tax ID, or Other—and enter its value only when authorized. Company ID is stored separately as a private accounting-export field, including supported QuickBooks invoice custom fields; do not show it publicly.",
        "Enter SEO title up to 60 characters and Meta description up to 160 characters; the live counters show the saved draft length. Enter the longer Store description used by supported storefront content. Write accurate customer-facing copy without hidden claims about availability, delivery, returns, or pricing.",
        "Under Storefront theme, choose Primary color and Accent color with the color picker or exact color value. These fields are drafts until Save changes. Verify contrast, focus visibility, button readability, and mobile presentation on the real public storefront.",
        "Under Website embed, leave Enable embed widget off unless an approved external site needs the entire storefront. The switch is saved with the page. When enabled, the page reveals an HTML snippet and Copy action.",
        "Do not publish or share an embed snippet that exposes a Supabase project or Edge Function URL. The current component can generate a direct service-host script source; customer-facing code must first be routed through a branded pos.getcentri.com path or verified customer domain. Escalate to CentriPOS support/engineering for the branded embed endpoint rather than copying the internal address into a public website.",
        "Choose Save changes once. The storefront settings write occurs first and the private Company ID write follows; a failure in the second write can occur after the main settings were already updated. Wait for Online store settings saved, then reopen the page and verify both public settings and authorized private accounting data.",
        "Test the saved platform URL and every verified custom-domain use in a private window. Confirm merchant identity, TLS, catalog, product/variant pages, cart persistence, exact location/register order intake, tax, enabled fulfillment methods, online/card or alternate payment paths, receipt/customer links, mobile layout, SEO metadata, and one controlled completion.",
        "Publish only after the controlled order returns one order number and the same order appears once in the intended Order Intake, Receipts, register reporting, inventory, payment, and fulfillment workflows. If a submission result is uncertain, trace the existing record before retrying."
      ],
      "controls": [
        {
          "name": "Globe icon",
          "description": "Exact Admin navigation icon for Online store and the icon used on domain rows."
        },
        {
          "name": "Save changes",
          "description": "Persists page-level publishing, inventory source, slug, identity, SEO, theme, and embed settings; it does not control the separate domain writes."
        },
        {
          "name": "Store published",
          "description": "Draft switch that makes a saved storefront publicly accessible."
        },
        {
          "name": "Location",
          "description": "Inventory source and operating location for online sales; changing it clears the draft Register."
        },
        {
          "name": "Register",
          "description": "Register under the chosen location used for online orders and register reports."
        },
        {
          "name": "Store slug",
          "description": "Unique lowercase letters/numbers/hyphens path segment for the branded platform URL."
        },
        {
          "name": "Platform URL",
          "description": "https://pos.getcentri.com/store/<slug>; available only when a slug exists and public only when the store is published."
        },
        {
          "name": "External link / Copy",
          "description": "Opens or copies the current branded platform URL; verify merchant and publication state first."
        },
        {
          "name": "Custom-domain hostname",
          "description": "Scheme-free customer subdomain stored as a separate tenant-domain record."
        },
        {
          "name": "Store + links",
          "description": "Uses a verified domain for the storefront and supported e-cart, pay, and receipt magic links."
        },
        {
          "name": "Links only",
          "description": "Uses the verified domain for supported customer links but not the storefront."
        },
        {
          "name": "Store only",
          "description": "Uses the verified domain for the storefront but not other customer-link surfaces."
        },
        {
          "name": "Add domain",
          "description": "Immediate insert that creates Pending validation; the first saved domain becomes Primary."
        },
        {
          "name": "CNAME / TXT / CF TXT",
          "description": "DNS ownership and routing records shown for an unverified domain."
        },
        {
          "name": "Verify",
          "description": "Runs domain ownership and SSL checks; CNAME, TXT, and certificate readiness are reported separately."
        },
        {
          "name": "Pending",
          "description": "Domain is not yet fully verified for customer use."
        },
        {
          "name": "Verified",
          "description": "Current verification service reports the required state, including active SSL."
        },
        {
          "name": "Primary",
          "description": "Automatically assigned to the first domain; no separate primary-selector control appears here."
        },
        {
          "name": "Use for selector",
          "description": "Immediate update of the domain’s customer-surface scope."
        },
        {
          "name": "Trash",
          "description": "Immediate domain deletion without a confirmation dialog in this component."
        },
        {
          "name": "Store name",
          "description": "Customer-facing storefront identity."
        },
        {
          "name": "Company ID",
          "description": "Private accounting-export value stored separately from public storefront settings."
        },
        {
          "name": "SEO title",
          "description": "Customer/search title limited to 60 characters."
        },
        {
          "name": "Meta description",
          "description": "Search summary limited to 160 characters."
        },
        {
          "name": "Store description",
          "description": "Longer customer-facing store description."
        },
        {
          "name": "Primary / Accent color",
          "description": "Saved theme colors for the public storefront."
        },
        {
          "name": "Enable embed widget",
          "description": "Saved switch revealing an external-site embed snippet."
        },
        {
          "name": "Embed snippet safety",
          "description": "Do not publish the current direct service-host source; obtain a branded pos.getcentri.com or verified-domain endpoint first."
        },
        {
          "name": "Partial-save boundary",
          "description": "Main storefront settings save before the private Company ID upsert, so reopen and verify both after any error."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of loaded default settings with no private Company ID, verified domain, credential, DNS token, or saved mutation."
        }
      ],
      "expectedResult": "The branded storefront opens with the intended identity, catalog source, domain, and customer checkout choices.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-online-store.png",
        "alt": "Harbor & Hearth Online Store settings showing publishing, inventory source, store URL, and domain configuration in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "revenue-attribution",
      "url": "https://platform.getcentri.com/centripos/revenue-attribution",
      "title": "Configure Revenue Attribution",
      "summary": "Define how storefront and WooCommerce order economics are assigned between enterprise HQ and a child franchisee based on who fulfills the order.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "This network-only screen stores storefront revenue policies. It does not assign credit to an individual associate, arbitrary location, marketing channel, or receipt source, and it is separate from saved-sale attribution audit events.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Revenue attribution. Confirm you are in the intended network tenant; the page loads policies owned by the current tenant and child tenants whose parent is that tenant.",
        "Read every policy card before adding one. Each card shows its name, whether it is inactive, whether it applies to All franchisees (default) or one specific child, and the HQ-fulfilled and locally fulfilled model values.",
        "Choose New policy. Enter a clear Policy name and set Applies to to All franchisees (default) or one exact child organization. The screen does not explain precedence when several active policies overlap, so avoid ambiguous duplicates unless downstream policy resolution has been separately verified.",
        "Under When HQ/factory fulfills, choose HQ keeps revenue, HQ keeps revenue + franchisee gets credit/rebate, or Split revenue.",
        "If using franchisee credit/rebate, choose No rebate, % of order, Flat $ per order, or Flat $ per unit. Enter Rate only when the rebate type is not None.",
        "Under When franchisee fulfills locally, choose Franchisee keeps revenue, HQ keeps revenue (pays commission), or Split revenue.",
        "If HQ keeps locally fulfilled revenue, choose No commission, % of order, or Flat $ per order. Enter Rate only when the commission type is not None.",
        "Under Additional settings, enter Cost-plus markup % for product cost on inter-company transfers. Choose whether accumulated credits offset royalty invoices and/or reduce network transfer invoices for product purchases from HQ.",
        "Choose Save and wait for Revenue policy saved. Reopen the card and verify every stored field. The current editor does not expose an Active switch or Notes field even though those values exist in the record.",
        "Use Edit for an existing policy. The trash action deletes immediately without a confirmation dialog in this implementation, so treat it as a destructive action and verify the exact policy before choosing it.",
        "Validate with a controlled storefront/WooCommerce order whose fulfilling party and child organization are known. Reconcile the resulting network economic records, rebate/commission or split, and any credit offsets; a saved policy alone does not prove the downstream order applied it."
      ],
      "controls": [
        {
          "name": "Policy scope",
          "description": "Either all child franchisees as the default or one selected direct child tenant."
        },
        {
          "name": "HQ/factory fulfills",
          "description": "The order is fulfilled by HQ or the factory; the policy chooses HQ revenue, HQ plus a child rebate, or a split model."
        },
        {
          "name": "Franchisee credit/rebate",
          "description": "HQ retains revenue while the child receives the configured percentage, per-order amount, or per-unit amount."
        },
        {
          "name": "Franchisee fulfills locally",
          "description": "The child fulfills the storefront order; the policy chooses child revenue, HQ revenue with commission, or split."
        },
        {
          "name": "Local commission",
          "description": "Payment to the fulfilling child when HQ retains revenue: percentage or flat per order."
        },
        {
          "name": "Split revenue",
          "description": "A stored revenue-model choice. This editor does not expose a split percentage or allocation fields, so verify the downstream implementation before relying on an amount."
        },
        {
          "name": "Cost-plus markup",
          "description": "Percentage added to product cost for inter-company transfers."
        },
        {
          "name": "Credits offset royalties",
          "description": "Accumulated policy credits reduce franchise royalty billing."
        },
        {
          "name": "Credits offset product orders",
          "description": "Credits reduce network transfer invoices for product purchases from HQ."
        },
        {
          "name": "Inactive badge",
          "description": "The stored policy has is_active false. This editor displays the state but currently provides no control to change it."
        },
        {
          "name": "Notes boundary",
          "description": "The policy record supports notes, but the current editor does not expose a Notes input."
        },
        {
          "name": "Delete boundary",
          "description": "The trash action deletes the policy immediately and has no confirmation dialog on this screen."
        },
        {
          "name": "Proof of attribution",
          "description": "A reconciled controlled storefront order and its network economic records, not merely the successful policy save message."
        }
      ],
      "expectedResult": "The intended user, location, channel, or source receives credit under the configured rule, and a controlled sale’s attribution agrees across receipt and reporting views.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "ecart-settings",
      "url": "https://platform.getcentri.com/centripos/ecart-settings",
      "title": "Configure and Test E‑Cart Settings",
      "summary": "Control the customer payment-authorization gate, policy links, paid-order email recipients, signed HTTPS webhooks, and the operational release notices created after a branded E‑Cart is fully paid.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Admin → E‑Cart uses the Link 2 icon. Every field is a local draft until Save E‑Cart Settings. This page stores acknowledgment, policy links, recipients, webhook URLs, and signing secret inside the tenant settings JSON; the signing secret is masked in the input but is not written through the encrypted service-credential store. Current checkout renders the acknowledgment only when it is both enabled and required. Treat legal text, recipients, URLs, and secrets as sensitive production configuration and run controlled end-to-end tests.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → E‑Cart, identified by the Link 2 icon. Confirm the intended CentriPOS business before editing; these settings are tenant-wide defaults consumed by public E‑Cart checkout and paid-order notification services.",
        "Read Legally binding digital agreements. Register/store signature requirements, terms display, signature capture, IP/user-agent/timestamp metadata, and payment gating are configured separately. The E‑Cart Payment Acknowledgment here is a distinct checkbox gate and is not a substitute for legal advice or a required signature.",
        "Enable acknowledgment step controls whether the E‑Cart acknowledgment feature is active. Require acknowledgment before payment can be changed only while enabled and gates card, supported ACH, and financing actions until the customer checks the authorization box. Both switches remain unsaved until the bottom Save.",
        "Current checkout behavior is stricter/narrower than the labels imply: the Payment Authorization panel and custom acknowledgment text render only while enabled + required + not yet accepted. If enabled but Require is off, there is no optional acknowledgment panel displayed. Test the actual public checkout before relying on optional consent wording.",
        "Write concise Acknowledgment text describing the exact payment authorization and approved policy relationship. When blank/whitespace is stored, public cart lookup falls back to the system default wording. The customer checkbox label itself remains “I acknowledge and authorize payment processing for this order.”",
        "Acknowledgment acceptance is browser UI state reset when the E‑Cart token changes. This component does not show a separate persisted acceptance record for the E‑Cart checkbox. Do not represent it as equivalent to the register signature audit trail; use the approved signature workflow when durable signed evidence is required.",
        "Under Paid E‑Cart Notices, understand the trigger. The notice service skips a sale without a posted E‑Cart token or with balance due above $0.009. When fully paid, it merges the sale location email, tenant Additional notice recipients, and any location-level ecart_paid_notice_emails, removes duplicates, and discards invalid addresses at send time.",
        "Enter Additional notice recipients one per line or separated by commas/semicolons. The editor deduplicates case-insensitively but does not validate email syntax while typing/saving; invalid entries can remain in tenant settings and will be silently excluded by the notice service. Reopen and independently verify every operational address.",
        "The merchant email subject includes the receipt number and can include a branded public receipt link/PDF plus customer, sale, payment, and pending-fulfillment details. Add only recipients authorized to receive that data. The location email is automatically included when valid; remove/change it under Locations & Registers, not here.",
        "A paid E‑Cart can also generate a customer receipt email separately when an eligible customer/display email exists. Merchant paid notice and customer receipt use different activity-log communication kinds and idempotency checks. Editing recipients does not resend an already recorded notice automatically.",
        "Under Paid E‑Cart Webhooks, enter only approved HTTPS endpoints. The editor keeps newline/comma/semicolon entries beginning with https:// and deduplicates them, but does not fully parse/validate the URL until the sender; malformed or non-HTTPS values are removed from the saved normalized URL list.",
        "Each endpoint receives an ecart.paid JSON event with a stable event_id based on sale ID; occurrence time; tenant, location, register, sale totals/status/IDs/timestamps; customer identity/contact and marketing-opt-in fields; pending fulfillment lines; and branded app/public receipt links. This is customer and transaction data—apply least privilege, retention, monitoring, and vendor agreements.",
        "CentriPOS sends X-CentriPOS-Event, a random X-CentriPOS-Delivery ID, and, when a secret exists, X-CentriPOS-Signature in sha256=<hex> form. The signature is HMAC-SHA256 over the exact raw JSON request body. Verify it using constant-time comparison before parsing/trusting the payload.",
        "Generate a strong unique Webhook signing secret outside the page and deliver it securely to the receiving middleware. The field is masked but Save stores its trimmed value in tenant.settings.ecart; it is not encrypted through the platform service-credential vault in this implementation. Restrict admin access and never expose it in screenshots, tickets, browser logs, or client code.",
        "Webhook deliveries run concurrently and capture URL, delivery ID, HTTP success/status, or request error. A non-2xx webhook does not make the notice function fail; results are written to the merchant notice activity record, which then prevents ordinary duplicate merchant sends. There is no retry schedule or per-endpoint resend control on this settings screen.",
        "When merchant email sending is required and the email service is unconfigured or rejects the message, the notice function returns an error before webhook dispatch/marking in the normal path. Inspect the sale communication/activity evidence and integration logs; do not assume “paid” means every notification arrived.",
        "Policy Links appear at the bottom of supported E‑Cart checkout and open in a new tab. Enter public HTTPS Terms & Conditions and Privacy Policy URLs owned/approved by the business. The settings editor uses type=url but Save performs no explicit URL validation or HTTPS enforcement for these two fields.",
        "Public cart lookup prefers a register-level privacy/terms value when present and otherwise uses these tenant E‑Cart URLs. Review the actual register involved in the sale; changing the tenant value may not change a register override.",
        "Choose Save E‑Cart Settings once. The save rereads the current tenant settings, merges the ecart object, normalizes recipient lists/HTTPS webhooks, trims the secret, and writes the entire merged settings JSON. Wait for E‑Cart settings saved, then reopen the page and confirm every value.",
        "Create a controlled E‑Cart from the exact location/register. Open only a branded https://pos.getcentri.com customer link (or an approved verified customer domain), confirm authorization gating/text, signature/terms behavior, policy links, eligible payment methods, totals/balance, and customer identity.",
        "Complete a small approved test payment. Verify the receipt and payment in CentriPay Transactions before retrying; then verify the sale location email, each additional recipient, customer receipt when expected, browser/web-push notice where configured, webhook raw body/signature/status, activity log, pending Fulfillment Center work, and branded receipt links.",
        "Test negative paths: acknowledgment required/unaccepted, enabled but not required, disabled, blank text fallback, invalid policy URL, invalid/duplicate email, malformed/non-HTTPS webhook, no secret, bad signature, endpoint 4xx/5xx/timeout, missing location email, partial balance, already-sent idempotency, and register policy override.",
        "Harbor & Hearth’s real Amelia Grant screenshot shows the fully loaded /admin/ecart settings at 1440×900 with the actual Link 2 navigation and general configuration sections. It intentionally exposes no recipient addresses, webhook URLs, signing secret, or private policy URLs; no setting was saved and no E‑Cart/payment/notification was triggered."
      ],
      "controls": [
        {
          "name": "Link 2 icon",
          "description": "Exact Admin navigation icon for E‑Cart."
        },
        {
          "name": "Legally binding digital agreements",
          "description": "Boundary between register signature audit behavior and the separate payment acknowledgment."
        },
        {
          "name": "Enable acknowledgment step",
          "description": "Tenant draft flag activating acknowledgment behavior."
        },
        {
          "name": "Require acknowledgment",
          "description": "When enabled, blocks payment/financing until the customer checks the box."
        },
        {
          "name": "Current optional-mode limitation",
          "description": "Enabled + not required does not render an optional acknowledgment panel in current checkout."
        },
        {
          "name": "Acknowledgment text",
          "description": "Customer authorization copy; blank falls back to system default."
        },
        {
          "name": "Acceptance state",
          "description": "Client UI state reset per token; not represented here as the durable signature audit record."
        },
        {
          "name": "Additional notice recipients",
          "description": "Tenant merchant-notice emails merged with sale-location and location-level recipients."
        },
        {
          "name": "Email normalization",
          "description": "Case-insensitive dedupe in editor; valid-email filtering occurs only in sender."
        },
        {
          "name": "Customer receipt",
          "description": "Separate paid E‑Cart email/idempotency path to eligible customer email."
        },
        {
          "name": "Webhook URLs",
          "description": "Normalized/deduplicated HTTPS endpoints for ecart.paid."
        },
        {
          "name": "ecart.paid payload",
          "description": "Customer, sale, location/register, totals, fulfillment, and branded link data."
        },
        {
          "name": "X-CentriPOS-Delivery",
          "description": "Random identifier generated per endpoint request."
        },
        {
          "name": "X-CentriPOS-Signature",
          "description": "HMAC-SHA256 of exact raw body, formatted sha256=<hex>."
        },
        {
          "name": "Webhook signing secret",
          "description": "Masked but stored in tenant settings JSON, not the encrypted service-credential store."
        },
        {
          "name": "Webhook failure boundary",
          "description": "Non-2xx/error is recorded; it does not fail the notice function or automatically schedule retry."
        },
        {
          "name": "Merchant notice idempotency",
          "description": "Activity-log marker suppresses ordinary repeat sends after dispatch is recorded."
        },
        {
          "name": "Terms & Conditions URL",
          "description": "Tenant fallback public link; no explicit Save-time validation."
        },
        {
          "name": "Privacy Policy URL",
          "description": "Tenant fallback public link; no explicit Save-time validation."
        },
        {
          "name": "Register override",
          "description": "Register settings take precedence over tenant policy URLs when present."
        },
        {
          "name": "Save E‑Cart Settings",
          "description": "Reread/merge/write tenant settings; all page controls are drafts until chosen."
        },
        {
          "name": "Branded public host",
          "description": "Customer-facing links and webhook payload links use pos.getcentri.com."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant loaded E‑Cart settings capture with secrets/recipients/URLs excluded and no mutation."
        }
      ],
      "expectedResult": "A controlled E-Cart shows the intended acknowledgment and sends only the configured paid-cart notices or webhook after successful payment.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-ecart.png",
        "alt": "Harbor & Hearth E-Cart Settings showing payment acknowledgment and notification behavior in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "lightspeed-import",
      "url": "https://platform.getcentri.com/centripos/lightspeed-import",
      "title": "Authorize and run Lightspeed X-Series imports safely",
      "summary": "Connect the intended Vend/Lightspeed store, run dependency-ordered background import jobs, interpret job evidence, and avoid destructive purge controls.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Lightspeed Import uses the Arrow Down To Line icon. This is a live migration console, not a preview or dry-run tool: Import and Run preset create background jobs that write tenant data. Cancel preserves records already created or updated. Disconnect immediately clears the stored token. Most purge actions target source-marked imported records, but Purge all receipts is exceptional: the UI calls a full tenant sales purge, deletes all sales and broad related records, clears parked carts, and resets every register’s receipt number to 1. Never use purge in production without an approved migration rollback plan and verified backup.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → Lightspeed Import in the intended CentriPOS business. Confirm the Lightspeed X-Series Import heading and Arrow Down To Line navigation icon. The approved Harbor & Hearth screenshot shows only the untouched unconnected authorization state.",
        "Before authorization, identify the exact Lightspeed X-Series/Vend retailer, its environment, expected domain prefix, CentriPOS tenant, locations, registers, users, payment methods, tax model, products/variants, customers, suppliers, inventory, purchase orders/transfers/returns, historical sales range, and receipt-number policy.",
        "Choose Authorize with Lightspeed only when signed into the intended provider account. CentriPOS requests an OAuth authorize URL and redirects the current page. Complete provider consent without pasting credentials, tokens, or private account details into support notes.",
        "On return, look for Lightspeed connected successfully and verify Connected to <domain>. The callback removes its success/error query parameter from the browser URL. Stop if the displayed store/domain is wrong; do not import and plan to clean it up afterward.",
        "Understand Disconnect: it immediately sets the integration inactive, replaces its stored API token with an empty string, clears the local connection, and shows Disconnected. There is no confirmation. It does not undo imported data or cancel completed jobs.",
        "Choose an ordered preset for normal dependency-aware work. Initial full sync runs Products → Composites → Suppliers → Customers → Sales → Consignments → Inventory → Register Reports. Daily Lightspeed catch-up runs Customers → Sales → Consignments → Inventory → Register Reports. Only one active job/preset is intended at a time.",
        "Use individual Import only for a deliberate resource step: Products includes variants, brands, categories, tags, and supplier links; Customers includes balances/contact info; Receipts includes sale lines, payments, original numbers, and user attribution; Suppliers imports vendors; Consignments maps purchase orders, stock transfers, and supplier returns; Register Reports reconstructs sessions after sales; Inventory Levels applies stock after products; Composites & Case Packs links bundles/case-pack relationships after products.",
        "There is no mapping editor, preview, dry-run, record-selection list, date-range selector, location selector, duplicate-resolution screen, or Apply confirmation in this UI. Starting a job inserts an import_jobs row and invokes the import function asynchronously. Run a controlled migration tenant or approved narrow sequence first, not an unreviewed production full sync.",
        "After starting, wait for Started <resource> import. Imports run in the background and the page polls about every five seconds while a recent job is Pending or Running. You may navigate away, but return to inspect completion rather than assuming the toast means data imported.",
        "Read progress as Processed, Created, Updated, Errors, and optional phase/detail. The progress bar is an estimate capped below completion while running. A Completed row shows created/updated totals, warnings, and completion time. Expand warnings and review every message; they can contain source data identifiers and should not be copied publicly.",
        "Cancel is a request, not rollback. It changes the job status to Cancelled and says the import will stop shortly. The final row reports records created/updated before stopping, and those partial writes remain. Reconcile them before re-importing.",
        "Re-import starts another job for that resource. Do not use it as a blind retry: inspect the previous warnings/errors, source IDs, created-versus-updated counts, and representative records first so duplicate/mismatched or partially imported data is not compounded.",
        "Import History is limited: the page loads the newest 20 jobs and displays only the first 10 in history. Each resource card uses the newest matching job within that loaded window. Absence from the visible history is not proof a resource was never imported.",
        "Treat every Purge all <resource> data action as destructive. The button appears after a failed, cancelled, or completed job with created/updated activity, but it is not scoped to that one job. The confirmation says permanent and cannot be undone. Do not approve it merely to clear a warning or retry.",
        "For Products, Customers, Suppliers, Consignments, Register Reports, Inventory, and Composites, the screen calls purge-data without all:true. The function generally uses source/import markers for those supported resource branches, but it can delete/null linked catalog, stock, pricing, purchasing, and relationship data. Review the exact current function and tenant backup before use.",
        "For Receipts/Sales, stop: the screen calls purge-data with type sales, all true, and reset_receipt_counters true. It deletes all tenant sales regardless of Lightspeed source marker plus line items, payments, fulfillment, layaway/AR/returns/store-credit links and other related records, clears tenant parked carts, nulls some external transaction/order links, removes sale inventory movements, and resets each register receipt counter to 1. This is not a safe “remove the last import” action.",
        "After a completed import, verify each selected resource independently: representative identities and source IDs, variants/SKUs, costs/prices/tax, locations/stock, customer balances/contact data, suppliers, receipts/lines/payments/users/numbers, purchase/transfer/return documents, composite children/quantities, and reconstructed register sessions/closures. Reconcile totals against a Lightspeed export.",
        "Keep migration evidence: tenant/store IDs, authorization time, job IDs, resource/preset, started/completed timestamps, counts, warnings/errors, sample source-to-CentriPOS IDs, reconciliation totals, and signoff. Do not include OAuth tokens, API tokens, full customer data, or payment credentials."
      ],
      "controls": [
        {
          "name": "Arrow Down To Line icon",
          "description": "Exact CentriPOS navigation icon for Lightspeed Import."
        },
        {
          "name": "Authorize with Lightspeed",
          "description": "Requests an OAuth authorization URL and redirects the current page; it does not import by itself."
        },
        {
          "name": "Connected to <domain>",
          "description": "Saved active integration with nonempty token; verify the retailer before any job."
        },
        {
          "name": "Disconnect",
          "description": "Immediately disables the integration and clears its token without confirmation; imported data remains."
        },
        {
          "name": "Initial full sync",
          "description": "Eight-step dependency-ordered first migration preset."
        },
        {
          "name": "Daily Lightspeed catch-up",
          "description": "Five-step customers/sales/consignments/inventory/register-reports preset."
        },
        {
          "name": "Run preset",
          "description": "Creates the first background job with a queued preset sequence; later steps queue automatically."
        },
        {
          "name": "Individual Import",
          "description": "Creates one pending resource job and invokes the importer asynchronously."
        },
        {
          "name": "Products",
          "description": "Products, variants, brands, categories, tags, and supplier relationships."
        },
        {
          "name": "Customers",
          "description": "Customer records, balances, and contact information."
        },
        {
          "name": "Receipts",
          "description": "Sales with receipt numbers, lines, payments, and user attribution."
        },
        {
          "name": "Suppliers",
          "description": "Supplier records."
        },
        {
          "name": "Consignments",
          "description": "Purchase orders, stock transfers, and supplier returns."
        },
        {
          "name": "Register Reports",
          "description": "Reconstructs register sessions from imported sales and should follow sales."
        },
        {
          "name": "Inventory Levels",
          "description": "Current variant/location stock and should follow products."
        },
        {
          "name": "Composites & Case Packs",
          "description": "Bundle/case-pack relationships and should follow products."
        },
        {
          "name": "No preview/mapping",
          "description": "UI has no dry run, date/scope selector, mapping, duplicate-resolution, or proposed-record preview."
        },
        {
          "name": "Progress",
          "description": "Background job processed/created/updated/error counts and phase, polled about every five seconds."
        },
        {
          "name": "Warnings",
          "description": "Expandable job messages requiring reconciliation; may contain source identifiers."
        },
        {
          "name": "Cancel",
          "description": "Marks cancellation requested; partial created/updated data remains."
        },
        {
          "name": "Re-import",
          "description": "Starts another job; it is not rollback or guaranteed idempotent recovery."
        },
        {
          "name": "Import History",
          "description": "Newest 10 displayed from the newest 20 loaded jobs."
        },
        {
          "name": "Purge button",
          "description": "Resource-wide destructive action, not job-specific. Requires explicit confirmation but no typed tenant name."
        },
        {
          "name": "Non-sales purge",
          "description": "Generally source-marker-scoped for supported branches, yet can remove/null extensive linked data; verify code/backup first."
        },
        {
          "name": "Sales purge exception",
          "description": "Passes all:true and reset_receipt_counters:true, deleting all tenant sales and broad dependencies and resetting receipt counters to 1."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/lightspeed-import in the initial unconnected state. It shows no OAuth flow, retailer identity, token, imported data, or job details."
        }
      ],
      "expectedResult": "The reviewed import creates or updates only the intended records, reports skipped and failed rows clearly, preserves source references, and can be reconciled against the import file.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-lightspeed-import.png",
        "alt": "Harbor & Hearth Lightspeed X-Series Import screen showing the initial safe authorization state in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "quickbooks-historical-import",
      "url": "https://platform.getcentri.com/centripos/quickbooks-historical-import",
      "title": "Import historical QuickBooks receipt exports safely",
      "summary": "Parse the exact interleaved receipt-export layout, map every source store to a CentriPOS location, and create historical sale/payment records without assuming products or customers are created.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "QuickBooks Historical Import uses the Arrow Down To Line icon and is separate from QuickBooks Online OAuth/synchronization. It is a direct-write migration tool with no row preview, dry run, duplicate detection, undo, purge, or rollback. Contrary to the screen description, the current function reports products_created 0 and customers_created 0: it creates completed sales, denormalized sale lines, payments, and missing payment-type labels; it only links existing products/customers when exact matching succeeds. Re-importing the same receipt can create a duplicate QB-<receipt> sale.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → QuickBooks Historical Import in the intended business. Confirm the Arrow Down To Line navigation icon and Upload QB Export card. Do not confuse this with Admin → QuickBooks Online or the Lightspeed migration console.",
        "Prepare a reviewed export in the importer’s exact positional structure, not an arbitrary QuickBooks report. It reads only the first worksheet and skips the first row. A sale header must have Receipt # in column C and the literal Sales in column F; it reads Date A, customer G, total L, payment M, and store O. Following item rows read SKU D, product name E, quantity I, and line amount K.",
        "The file control accepts .xlsx, .xls, and .csv even though its visible prompt says .csv or .xlsx. Parsing loads SheetJS from its CDN in a browser worker, ignores formulas/styles/date typing, reads at most 200,000 worksheet rows, and uses only the first sheet. Confirm network/privacy policy permits this client-side parser dependency.",
        "Create a small controlled file externally containing a few representative receipts in the exact layout. The page has no date range, row selector, receipt preview, column mapping, header validation, company identifier, duplicate scan, or file-content redaction before import.",
        "Choose the file and wait for Reading, Parsing spreadsheet, Converting to rows, and Parsing sales to finish. The screen shows only parsed sale and line-item counts, not receipt/customer/item/payment details. “No sales found” means no qualifying headers with item rows were detected; do not import by changing random columns.",
        "Be aware that the UI’s cap toast says 100,000 rows while the current worker actually sets and detects a 200,000-row cap. Treat any capped result as incomplete and split/reconcile the source deliberately.",
        "Review Map QB store codes to locations. The importer detects nonblank store strings from parsed sales and may auto-map by case-insensitive substring against location names. Auto-match is a suggestion, not proof. Select the exact destination for every code; Import remains disabled unless at least one store was detected and all detected codes are mapped.",
        "Before Import, audit existing sales for each planned QB-<receipt number>. The importer does not check for an existing sale number/source receipt and the database write path does not upsert. Running the same file twice can create duplicate completed sales, lines, and payments.",
        "Understand customer matching. It normalizes the export name and existing customer/company names by lowercasing, changing & to and, removing punctuation, and collapsing spaces. Exactly one matched customer ID is attached. Zero matches leaves the sale customer null and records the raw name in the sale note; multiple matches also leave it null and report Ambiguous. No customer is created.",
        "Understand product matching. Each item first looks for an exact tenant product SKU, then an exact product name. A match links product_id. No match still creates a receipt line whose name is suffixed (QB Import), with the source SKU, but creates no catalog product. Variant matching is not performed and cost is always 0.",
        "Understand payment behavior. The importer matches payment types case-insensitively by name and creates an enabled payment_type row when none exists. It then creates one completed payment for the sale total or computed subtotal. Review unsupported/legacy tender names before import so they do not silently become new enabled reporting methods.",
        "Understand historical sale values. Each record is inserted Completed with sale number QB-<receipt>, destination location, subtotal from line amounts, discount and tax 0, total/amount paid from nonzero export total or subtotal, change and balance 0, and a QB Import note. Date text is parsed as M/D/YY or M/D/YYYY at local noon then stored as an ISO timestamp. No register, register session, tax reconstruction, discounts, returns, account balance, or inventory movement is derived here.",
        "Choose Import <N> sales once. The browser sends sequential batches of 50 to the function and updates a percentage. There is no cancel button. A failed batch or individual receipt does not roll back earlier successful batches/rows, and a sale can exist even if one of its later line/payment writes reports a problem.",
        "Read Import Complete as counts, not reconciliation: sales, line items, products created (currently 0), customers matched, unmatched, ambiguous, and up to 20 displayed warnings. The client aggregates batch warnings and appends up to 25 ambiguous/unmatched names; those names are customer data and must not be copied publicly.",
        "If any warning/error occurs, stop. Check whether the affected QB sale and partial child rows already exist before retrying. There is no Import History, job ID, undo, delete-import, or source-batch identifier on this screen beyond the QB sale number/note. Use an approved surgical data-repair process if rollback is required.",
        "After a clean controlled batch, reconcile source versus CentriPOS receipt count/IDs, location, customer link/unmatched note, item names/SKUs/quantities/amounts, subtotal/total, payment type/amount, timestamps, zero tax/discount/cost assumptions, and reporting behavior. Only then proceed with another nonoverlapping reviewed file.",
        "Choose Import Another File only after preserving evidence of the completed batch. It clears the page state; it does not undo or deduplicate anything already written. Maintain an external import ledger of company, file hash/name, row/receipt range, store mappings, time, operator, counts, warnings, and reconciliation signoff."
      ],
      "controls": [
        {
          "name": "Arrow Down To Line icon",
          "description": "Exact CentriPOS navigation icon for QuickBooks Historical Import."
        },
        {
          "name": "Upload QB Export",
          "description": "Direct-write historical receipt importer, separate from QBO sync."
        },
        {
          "name": "Accepted file control",
          "description": ".xlsx, .xls, or .csv; first worksheet only."
        },
        {
          "name": "Expected header row",
          "description": "Date A, Receipt # C, Sales marker F, customer G, total L, payment M, store O."
        },
        {
          "name": "Expected item row",
          "description": "SKU D, product name E, quantity I, line amount K beneath its header."
        },
        {
          "name": "200,000-row parser cap",
          "description": "Actual worker limit; the UI toast currently misstates 100,000."
        },
        {
          "name": "Parsed counts",
          "description": "Sale/header groups with at least one product-name line; not a record preview."
        },
        {
          "name": "Store mapping",
          "description": "Every detected source store must map to one current CentriPOS location; substring auto-map requires review."
        },
        {
          "name": "Import button",
          "description": "Sends direct-write batches of 50; no dry run, confirmation, cancel, or rollback."
        },
        {
          "name": "QB-<receipt>",
          "description": "Generated CentriPOS sale number; no existing-sale duplicate check is performed."
        },
        {
          "name": "Customer matching",
          "description": "Exact one-result normalized name/company match only; unmatched/ambiguous sales have no customer link."
        },
        {
          "name": "No customer creation",
          "description": "Current function returns customers_created 0."
        },
        {
          "name": "Product matching",
          "description": "Exact SKU first, then exact name; no variant match."
        },
        {
          "name": "No product creation",
          "description": "Unmatched items become denormalized sale lines suffixed (QB Import); products_created remains 0."
        },
        {
          "name": "Payment type creation",
          "description": "Unknown nonblank method creates an enabled tenant payment-type label."
        },
        {
          "name": "Imported sale assumptions",
          "description": "Completed, zero tax/discount/cost/change/balance, fully paid, no register/session or inventory reconstruction."
        },
        {
          "name": "Batch partial-write risk",
          "description": "Earlier batches and parent/child writes are not rolled back when a later operation fails."
        },
        {
          "name": "Import Complete",
          "description": "Aggregated counts and warnings; not proof of source reconciliation."
        },
        {
          "name": "Import Another File",
          "description": "Clears local UI state only; previously imported data remains."
        },
        {
          "name": "No built-in history/undo",
          "description": "Screen provides no import job ledger, batch ID, dedupe, purge, or rollback."
        },
        {
          "name": "Harbor & Hearth screenshot",
          "description": "Real Amelia Grant capture of /admin/qb-import in the pristine upload state. It shows no selected file and exposes no accounting, customer, product, receipt, or payment data."
        }
      ],
      "expectedResult": "The reviewed historical import creates only the intended customer-safe accounting history, records source references and exceptions, and does not duplicate existing CentriPOS records.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-qb-import.png",
        "alt": "Harbor & Hearth QuickBooks Historical Import screen showing instructions, pristine file selection, and import controls in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "woocommerce",
      "url": "https://platform.getcentri.com/centripos/woocommerce",
      "title": "Use the WooCommerce integration",
      "summary": "Connect a WooCommerce store, control product, inventory, and order sync, link matching products, route online sales, and configure checkout calculations and payments.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "WooCommerce is managed inside Admin → Integrations. The Integrations item uses the Plug Zap icon; the WooCommerce tab and page use the Shopping Cart icon. This screen changes real catalog, stock, checkout, payment-reporting, and imported-sale behavior, so test with one controlled product and order before a broad sync.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin → Integrations, then choose WooCommerce. If you start on the Integrations overview, select Manage WooCommerce on its Shopping Cart card.",
        "In Connection, enter the complete Store URL and choose Connect with WooCommerce. Approve the connection on the Woo site and return to CentriPOS. Use Test connection to confirm the saved authorization.",
        "Use Manual REST API credentials only when the normal authorization flow is not suitable. Enter both Consumer key and Consumer secret, test them, and keep the secret private. A successful test before the first save does not enable sync by itself.",
        "Turn Integration enabled on only when the intended store and tenant are confirmed. Under Sync options, independently choose Products, Inventory, and Orders, then select Save at the top of the page. Products pushes the POS catalog to Woo; Inventory keeps stock levels synchronized; Orders pulls Woo orders into CentriPOS as sales.",
        "In Product links, choose Scan Woo products to review up to the recent Woo products returned by the audit. Each row shows Linked or Woo only, its Woo ID, SKU or variation SKUs, publication status, and any proposed SKU, variation-SKU, or title match.",
        "Review every proposed match before choosing Link product. Link matching SKUs applies eligible matches in bulk and reports how many linked, matched, and skipped. Linking writes the CentriPOS product ID into Woo product metadata; matching by title is a fallback, not proof that two products are the same.",
        "In Order register, select a CentriPOS Location and an active Register at that location, then choose Save register. Imported Woo sales, sales reporting, and register-level NMI Gateway overrides use this same register.",
        "Configure Checkout calculator only if the Woo cart or checkout plugin is prepared to call CentriPOS. Calculator enabled exposes the branded calculator endpoint; Fulfillment rates returns enabled pickup, delivery, and shipping choices; ZIPTax calculation calculates tax from the destination address.",
        "Generate the Shared secret once, store it securely in the Woo plugin, and send it using the x-centripos-woo-secret header. Rotating the secret invalidates the value previously configured in Woo, so update both sides together.",
        "Under CentriPOS payment gateway, enable Credit / debit card or Bank account / ACH only after the selected order register has the corresponding NMI e-cart capability. Card supports NMI tokenization and 3DS when enabled; ACH requires ACH on that register. The method IDs and checkout labels shown on this page are read-only.",
        "Copy the branded Payment endpoint into the compatible Woo payment bridge. The bridge tokenizes payment details rather than sending raw card or bank data to CentriPOS; do not replace the pos.getcentri.com endpoint with an internal service URL.",
        "In Payment types, choose Refresh after connecting the store or enabling a Woo checkout method. Map each Woo method to the CentriPOS payment type that should appear in sales and register reporting, then choose Save mappings. A method can also appear because it was seen on an imported order.",
        "Use Sync now for a deliberate manual operation: Push products, Sync inventory, Pull orders, or Refresh linked orders. Enterprise, Agency, and Platform tenants also see Push network inventory. Do not click several sync actions repeatedly while one is still running.",
        "After a sync, read the completion message and the Last product sync, Last inventory sync, and Last order sync timestamps. The linked-product count confirms mappings, but it does not prove every Woo item is linked or that every row synchronized without an error.",
        "Place one controlled Woo order using a linked SKU and a mapped payment method. Confirm it appears in CentriPOS sales under the selected location and register with the expected customer, items, fulfillment, tax, payment type, and Woo order reference. There is no separate Woo “Order Intake” queue on this integration page.",
        "If the business uses CentriPOS to return a Woo-origin sale, verify the original Woo reference and watch the refund-sync result. Do not retry a completed refund merely because Woo takes time to refresh; first confirm the CentriPOS receipt and integration status to avoid a duplicate operational action."
      ],
      "controls": [
        {
          "name": "Integration enabled",
          "description": "Master switch for the saved WooCommerce integration. Turning it off pauses configured synchronization without deleting mappings."
        },
        {
          "name": "Store URL",
          "description": "The public HTTPS address of the WooCommerce store being connected."
        },
        {
          "name": "Connect with WooCommerce",
          "description": "Starts the Woo authorization flow and returns to the CentriPOS WooCommerce settings page."
        },
        {
          "name": "Manual REST API credentials",
          "description": "Optional Consumer key and Consumer secret fields for stores that cannot use the normal authorization flow. Both values are required together."
        },
        {
          "name": "Test connection / Test credentials",
          "description": "Checks that CentriPOS can reach the store and identifies the connected WooCommerce version; it does not by itself enable synchronization."
        },
        {
          "name": "Products",
          "description": "Pushes the CentriPOS product catalog to WooCommerce when product sync is enabled or manually run."
        },
        {
          "name": "Inventory",
          "description": "Keeps Woo stock levels synchronized from the applicable CentriPOS inventory scope."
        },
        {
          "name": "Orders",
          "description": "Pulls WooCommerce orders into CentriPOS as sales."
        },
        {
          "name": "Product links",
          "description": "Audit of recent Woo products and their CentriPOS mapping state, Woo ID, SKU, variation SKUs, status, and proposed match."
        },
        {
          "name": "Scan Woo products",
          "description": "Refreshes the product-link audit without linking anything."
        },
        {
          "name": "Link product",
          "description": "Connects one reviewed Woo product to the proposed CentriPOS product."
        },
        {
          "name": "Link matching SKUs",
          "description": "Bulk-links eligible audited matches and reports linked, matched, and skipped counts. Review ambiguous or title-only matches individually."
        },
        {
          "name": "Order register",
          "description": "The location and active register used for imported Woo sales, their reporting scope, and register-level e-cart gateway overrides."
        },
        {
          "name": "Calculator enabled",
          "description": "Allows the compatible Woo plugin to call the CentriPOS checkout-calculation endpoint."
        },
        {
          "name": "Fulfillment rates",
          "description": "Exposes enabled pickup, delivery, and shipping methods to the Woo checkout calculator."
        },
        {
          "name": "ZIPTax calculation",
          "description": "Calculates checkout tax using the destination address."
        },
        {
          "name": "Calculator endpoint",
          "description": "Branded pos.getcentri.com URL used by the compatible Woo cart or checkout plugin."
        },
        {
          "name": "Shared secret",
          "description": "Authenticates checkout-calculator and payment-bridge calls. Generate or rotate it here, then store the same current value securely in Woo."
        },
        {
          "name": "Credit / debit card",
          "description": "Enables the CentriPOS Woo method backed by the selected register’s NMI card configuration and optional 3DS."
        },
        {
          "name": "Bank account / ACH",
          "description": "Enables the CentriPOS Woo ACH method when ACH is configured on the selected register."
        },
        {
          "name": "Payment endpoint",
          "description": "Branded pos.getcentri.com endpoint used by the compatible payment bridge after secure browser-side tokenization."
        },
        {
          "name": "Payment types",
          "description": "Maps Woo checkout method IDs to enabled CentriPOS payment types used in imported sales and reporting."
        },
        {
          "name": "Refresh payment methods",
          "description": "Reloads methods enabled in Woo or discovered on orders."
        },
        {
          "name": "Push products",
          "description": "Runs a catalog push immediately."
        },
        {
          "name": "Sync inventory",
          "description": "Runs inventory synchronization immediately."
        },
        {
          "name": "Push network inventory",
          "description": "Enterprise-level action for supported network tenants; it is not shown to every business."
        },
        {
          "name": "Pull orders",
          "description": "Polls Woo and imports eligible orders into CentriPOS sales."
        },
        {
          "name": "Refresh linked orders",
          "description": "Refreshes the CentriPOS records already mapped to Woo orders."
        },
        {
          "name": "Last sync timestamps",
          "description": "Show when product, inventory, and order sync last completed; Never means no successful timestamp has been recorded."
        },
        {
          "name": "Linked products count",
          "description": "Number of saved CentriPOS-to-Woo product mappings, not a guarantee that the full catalogs are identical."
        }
      ],
      "expectedResult": "The intended Woo store reports a healthy connection; the enabled product, inventory, and order directions match the operating plan; reviewed products are linked to the correct CentriPOS records; imported orders post once to the selected location and register with the mapped payment type; and any enabled calculator or payment bridge succeeds through the branded endpoint with the current shared secret.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "quickbooks",
      "url": "https://platform.getcentri.com/centripos/quickbooks",
      "title": "Configure QuickBooks Online",
      "summary": "Connect the correct QuickBooks company, choose invoice dates and workflow permissions, and map sales, payments, fees, deposits, tax, classes, and supported purchasing.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Integrations",
      "introduction": "QuickBooks configuration changes affect financial records. Coordinate with the business’s accounting owner, test in a controlled period, and never place OAuth credentials or company identifiers in screenshots or support notes.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Go to Admin → QuickBooks Online for the intended storefront. Choose Connect to QuickBooks and complete Intuit authorization for the exact company. Return to CentriPOS and verify Connected, the company identity, and the connection time before mapping anything.",
        "Choose Refresh QuickBooks options to load current accounts, products/services, payment methods, tax codes, and classes into CentriPOS. A missing option can mean the cache needs refresh; it does not justify selecting a similarly named account without verification.",
        "In Invoicing, distinguish the storefront mapping switch, Customer Account invoice sync choice, the CentriPOS-led or QBO-led workflow, and the separate collection and edit-lock choices. Saving these preferences does not itself post a document, import a payment, or activate every integration path. Incoming QuickBooks payment activity can be displayed as accounting evidence; do not assume a setting has created a new CentriPOS tender or reconciled a local balance.",
        "Choose QuickBooks invoice date deliberately: Date of the sale in CentriPOS, Delivered date in CentriPOS, or Date first sent to QuickBooks. The setting applies to new invoice creation and uses the sale location’s business timezone. Delivered date requires all connected fulfillments to be complete with an unambiguous business date; split fulfillment uses the final delivery date, while no connected fulfillment falls back to the sale date. Net terms and default due days start from the selected invoice date; saved delivery deadlines stay unchanged. A first-send date is retained for retries. Changing this setting does not rewrite dates on existing linked invoices or enable automatic sending.",
        "In Sale Information, map the general sales item, optional invoice custom fields, discrepancy, rounding, discount, and any other supported adjustment items. Set the default class, then location classes and register classes; a register mapping overrides its location and the default. Enable summarized register-closure sync only when this is the approved accounting model.",
        "In Expense Information, map cost of goods sold, inventory asset, freight or shipping, purchase discounts, duty, and import-fee accounts used by supported inventory and purchasing entries.",
        "In Vendors & Purchasing, review supplier/vendor matching and the purchase-order, received-PO bill, direct-receive bill, supplier-return credit, Accounts Payable, reference and document-link settings. These are separate workflows. The supported received-PO bill action still requires eligible received stock, the expected vendor and mappings, and a confirmed result. Do not infer that every purchasing option is active because its value can be saved, or infer that an available invoice/payment action is absent solely from a broad Still to wire notice.",
        "In Liabilities, map store-credit issuance expense and liability accounts plus gift-card breakage revenue and gift-card liability accounts. These mappings should match how the accountant recognizes outstanding obligations.",
        "In Payment Types, map each enabled CentriPOS tender to the intended QuickBooks payment method. Disabled tenders remain visible for historical context but should not be mapped casually to an active method.",
        "In CentriPay & Processing Fees, map the processing-fee expense/category, register-invoice fee service item, surcharge item, and approved deposit-matching method. Prefer processor reporting when reliable evidence is available; use any manual fallback only under a documented accounting policy and effective date.",
        "For an enabled EPX invoice-settlement workflow, select Invoice settlement deposit bank account. This is the destination for a staff-reviewed invoice settlement deposit, separate from register-closure deposits. The review verifies an active USD bank account in the connected company and the processing-fee expense mapping before it can post. Saving the account does not create a deposit.",
        "In Sales Taxes, map each CentriPOS tax rate to the exact QuickBooks tax code. Compare name, percentage, jurisdiction, and taxable behavior rather than matching by a similar label alone.",
        "Choose Save Settings. Run one controlled example for each live workflow the business intends to use, then inspect the CentriPOS source record and the resulting QBO customer/vendor, invoice or report document, payment, tax, class, item lines, fees, and total. Keep a recovery path before Disconnect; disconnecting authorization does not delete previously posted accounting records.",
        "Keep manual invoice-send permission separate from connection administration. Send to QB requires an owner, super admin, finance/accounting role, or an explicitly granted invoice-send permission. It adds or links the accounting invoice; it does not send customer email. A collection, deposit confirmation, or customer communication remains its own action and may require different permission."
      ],
      "controls": [
        {
          "name": "Connection",
          "description": "Storefront-level authorization to one verified QuickBooks company."
        },
        {
          "name": "Refresh QuickBooks options",
          "description": "Hydrates the local mapping cache with current QBO values."
        },
        {
          "name": "Invoicing",
          "description": "Customer Account invoice, payment, link, due-date, matching, collection, lock, and exclusion behavior."
        },
        {
          "name": "Invoice custom-field mapping",
          "description": "Maps a supported CentriPOS storefront, customer, or sale value into a named QBO invoice field."
        },
        {
          "name": "General sales / adjustment items",
          "description": "QBO products or services used for sales, discrepancy, rounding, discount, fee, or surcharge lines."
        },
        {
          "name": "Class precedence",
          "description": "Register class overrides location class, which overrides the default class."
        },
        {
          "name": "Expense Information",
          "description": "COGS, inventory asset, freight, purchase discount, duty, and import-fee account mappings."
        },
        {
          "name": "Vendors & Purchasing",
          "description": "Supplier matching and supported PO, bill, direct-receive, return-credit, reference, and link settings."
        },
        {
          "name": "Liabilities",
          "description": "Store-credit and gift-card accounting mappings."
        },
        {
          "name": "Payment Types",
          "description": "CentriPOS tender-to-QBO payment-method mapping."
        },
        {
          "name": "Processor reporting",
          "description": "Uses synchronized processor/deposit evidence for fee and net-deposit treatment."
        },
        {
          "name": "Manual fallback",
          "description": "Documented temporary fee calculation used only when approved and processor evidence is unavailable."
        },
        {
          "name": "Sales Taxes",
          "description": "CentriPOS tax-rate-to-QBO-tax-code mapping."
        },
        {
          "name": "Save Settings",
          "description": "Stores intended mappings; it does not retroactively prove or execute every possible sync."
        },
        {
          "name": "Disconnect",
          "description": "Removes active authorization while leaving previously created QBO records intact."
        },
        {
          "name": "QuickBooks invoice date",
          "description": "Chooses sale, completed-delivery, or first-send date for new invoices using the sale location’s business timezone; retry reuses its saved date."
        },
        {
          "name": "Invoice settlement deposit bank account",
          "description": "Verified active USD bank destination for staff-approved EPX invoice settlements; does not change register-closure deposit settings."
        },
        {
          "name": "Invoice-send permission",
          "description": "Separate authorization for manual Send to QB; it does not grant all QuickBooks administration or send customer email."
        },
        {
          "name": "Incoming QuickBooks activity",
          "description": "Observed invoice/payment/deposit information and timeline evidence, kept separate from local tender posting."
        }
      ],
      "expectedResult": "The authorized QuickBooks company reports a healthy connection, mappings point to the intended accounts and records, and one controlled CentriPOS transaction syncs once.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly.",
        "If Delivered date blocks a send, verify every connected fulfillment and business delivery date. Do not change the accounting date merely to bypass an incomplete delivery.",
        "If a QuickBooks notice conflicts with a supported record-level action, preserve the exact screen and result for support. A broad setup notice is not an all-records status.",
        "If the mapped invoice deposit bank or processing-fee account fails validation, have the accounting owner correct the exact mapping before reviewing the same settlement again."
      ],
      "updated": "2026-11-16",
      "sourceReviewed": "2026-11-16",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "payment-type-settings",
      "url": "https://platform.getcentri.com/centripos/payment-type-settings",
      "title": "Configure Payment Types",
      "summary": "Separate connected processor/financing services from manual reporting tenders, diagnose each provider’s connection-plus-reporting state, and control where a custom type appears and what evidence cashiers must record.",
      "collection": {
        "id": "admin",
        "title": "Settings & administration"
      },
      "section": "Admin",
      "introduction": "Go to Admin → Payment types only with settings.payment_types authority. Credentials, merchant IDs, API keys, terminal identifiers, and connection details are sensitive. The attached Harbor & Hearth screenshot is a real read-only capture showing provider names and not-configured states only; it exposes no credentials or transactions.",
      "beforeYouBegin": "Use an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.",
      "steps": [
        "Open Admin → Payment types. Read the page’s central distinction: Integrated Payment Types are managed by connected services; Custom Payment Types are manual methods that are not driven by an integrated service.",
        "Review each integrated provider card: Payanywhere for connected terminals/card-present payments, NMI Gateway for gateway/ecommerce processing, PayTomorrow for financing reporting, and Katapult for lease-to-own reporting.",
        "For each card, compare Reporting payment type, Status, and Active connections. A provider is Active only when an active connection and an enabled matching reporting payment type both exist. The reporting row alone does not mean processing is connected.",
        "Interpret nonactive states precisely: Needs attention means saved/active service details are incomplete or its reporting row is disabled; Needs reporting type means a connection exists without an enabled matching row; Payment type only means the row exists without active connections; Disabled means the row exists disabled with no active connection; Not configured means neither was detected.",
        "Open Active connections only to inspect the location-level connection summary. Payanywhere derives it from active terminal devices; NMI uses master gateway settings or register overrides; financing uses provider settings on registers. Do not copy identifiers or credentials into support material.",
        "Use Credentials to open the provider’s dedicated secure setup page: in-store CentriPay for Payanywhere, online CentriPay for NMI, or Financing Apps for PayTomorrow/Katapult. Use Method to open the mapped payment-type detail. These are separate controls because a processor connection and reporting row solve different problems.",
        "Under Custom Payment Types, review the name, System status, POS/WEB badges, description, enabled switch, and row menu. An enabled custom row is still manual unless another documented integration actually invokes a processor.",
        "Choose Add type to select a preset or create a custom method. Presets include Cash, card labels, BNPL, digital wallets, Gift Card, Store Credit, Bank Transfer, QR Code, and Other, but choosing a preset creates a payment-type definition—not the third-party integration named by its label.",
        "Enter a unique, cashier-readable Name and optional Description. Choose POS and/or WEB channels, then choose at least one active location when locations exist. If every active location is selected, CentriPOS stores it as unrestricted; a subset becomes an explicit location list.",
        "Choose Add payment type. Success reports Payment type added and opens its detail page. If the new name overlaps an integrated alias such as CentriPay Cloud/Gateway, PayTomorrow, or Katapult, it can be classified into the integrated section; use the canonical reporting name intentionally.",
        "On the detail page, verify Payment information: name, immutable underlying type label, description, POS/WEB channels, and Locations. A Pay-screen method requires enabled status, POS support, current-location assignment, and—when noncash—Show in manual payment list.",
        "For noncash types, set Sell screen visibility. Keep manual exposure off for integrated/reporting/import-only rows unless cashiers truly need to record an already-completed outside transaction. Turning it on does not make CentriPOS call that provider.",
        "Configure Payment reference when the cashier must enter an external ID. Check forces reference collection. For other custom types, enable Collect a payment ID at checkout and set the exact Field label, Placeholder, and Instruction line staff can verify.",
        "For Cash, choose the rounding increment used when cash finishes a balance and decide whether to Conceal totals during register review. Conceal totals hides cash takings until the register is closed; it is not a substitute for permissions or reconciliation.",
        "For a noncash type, treat Gateway URL as an optional external-system endpoint field, not proof that a complete authenticated processor flow exists. Use the supported CentriPay/financing configuration for those named integrations. Terminal pairing for PAX/CentriPay/EPX-like rows is managed per register in Locations & registers.",
        "Use Enabled to make the type eligible under its other filters, then Save payment type. Success reports Payment type saved and refreshes POS/refund choice caches. Test from each allowed and disallowed location/channel; verify checkout visibility, reference requirement, receipt label, reports, refunds, register closure, and accounting export.",
        "Disable a custom type when it should stop appearing while preserving the definition/history. Edit can update name, description, channels, and locations. Delete is unavailable for system rows and permanently removes a custom row after confirmation; prefer disable when historical/reporting continuity is uncertain."
      ],
      "controls": [
        {
          "name": "Integrated Payment Types",
          "description": "Connected-service cards for Payanywhere, NMI Gateway, PayTomorrow, and Katapult."
        },
        {
          "name": "Reporting payment type",
          "description": "CentriPOS row used to label/report the service’s transactions."
        },
        {
          "name": "Active",
          "description": "Both an active service connection and enabled matching reporting row exist."
        },
        {
          "name": "Needs attention",
          "description": "Saved or active service setup exists but required activation/credentials or enabled reporting row is missing."
        },
        {
          "name": "Needs reporting type",
          "description": "Active connections exist without an enabled matching payment row."
        },
        {
          "name": "Payment type only",
          "description": "Enabled reporting row exists without an active service connection."
        },
        {
          "name": "Disabled",
          "description": "Matching payment row exists disabled with no active service connection."
        },
        {
          "name": "Not configured",
          "description": "No active connection or matching reporting row detected."
        },
        {
          "name": "Active connections",
          "description": "Location summaries derived from terminals, gateway master/overrides, or register financing settings."
        },
        {
          "name": "Credentials",
          "description": "Navigates to the provider-specific secure setup; never expose the values."
        },
        {
          "name": "Method",
          "description": "Opens the mapped reporting payment-type detail."
        },
        {
          "name": "Custom Payment Types",
          "description": "Manual definitions not currently classified as integrated provider rows."
        },
        {
          "name": "Add type",
          "description": "Preset search or custom-definition entry point."
        },
        {
          "name": "Preset",
          "description": "Seeds name/description only; it does not connect the named processor."
        },
        {
          "name": "POS / WEB",
          "description": "Channel filters; empty/unrestricted behavior differs from explicitly excluding POS."
        },
        {
          "name": "Locations",
          "description": "All active locations stores no restriction; a subset stores explicit IDs; zero is rejected when locations exist."
        },
        {
          "name": "System",
          "description": "Protected row whose delete control is unavailable."
        },
        {
          "name": "Enabled",
          "description": "Master eligibility switch; other channel/location/manual-list filters still apply."
        },
        {
          "name": "Show in manual payment list",
          "description": "Noncash control exposing a manual cashier record option."
        },
        {
          "name": "Collect a payment ID",
          "description": "Adds an amount/reference step at checkout; Check forces it."
        },
        {
          "name": "Field label / Placeholder / Instruction line",
          "description": "Cashier-facing reference guidance."
        },
        {
          "name": "Rounding",
          "description": "Cash increment applied when cash completes the balance."
        },
        {
          "name": "Conceal totals",
          "description": "Hides cash takings during open-register report review until closure."
        },
        {
          "name": "Gateway URL",
          "description": "Optional external URL field; not evidence of credentials, authentication, or successful processing."
        },
        {
          "name": "Terminal integration",
          "description": "Directs pairing to Locations & registers."
        },
        {
          "name": "Save payment type",
          "description": "Persists configuration and refreshes payment/refund choice queries."
        },
        {
          "name": "Disable vs delete",
          "description": "Disable preserves the definition; delete permanently removes a non-system row."
        },
        {
          "name": "Real Harbor & Hearth screenshot",
          "description": "Read-only Admin → Payment types capture with unconfigured provider statuses and no sensitive credentials, identifiers, or transactions."
        }
      ],
      "expectedResult": "The payment type appears only at its allowed locations and channels, collects the intended reference information, and completes the controlled test correctly.",
      "troubleshooting": [
        "Confirm you are changing the intended business and location before saving.",
        "Record the previous setting when a change affects live selling, payments, tax, or integrations.",
        "Use a controlled test record after saving before rolling the setting out broadly."
      ],
      "screenshot": {
        "url": "https://platform.getcentri.com/assets/screens/harbor/admin-payment-types.png",
        "alt": "Harbor & Hearth Payment Types screen showing available payment providers and safe configuration status in CentriPOS",
        "source": "Harbor & Hearth live CentriPOS demo"
      },
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-display-experience",
      "url": "https://platform.getcentri.com/centripos/customer-display-experience",
      "title": "Understand the Customer Display",
      "summary": "Pair an installed checkout display or temporary browser to the correct open register; approve and monitor the device; and understand every customer-visible cart, account, fulfillment, signature, phone-checkout, and completed-sale state.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "Customer Display is a live customer-facing surface scoped to an open register session and its paired host device. Installed mode establishes trusted checkout hardware; Temporary mode joins a one-time browser. Pair and approve only a device physically controlled for the intended register, keep customer information out of public view, and use destructive reset controls only when their full scope is understood.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Open the intended register session and confirm the business, location, and register in the information bar. The monitor control is disabled and reports Customer display unavailable until the register is open; opening a different register creates a different operating scope.",
        "Choose the monitor icon in the register information bar. Read the current status before generating anything: Customer display not connected is an available setup state, pending install needs POS approval, connected means at least one approved display is attached, and an error means the status service could not be read.",
        "Choose Installed for a dedicated store tablet/display that should retain its trusted checkout relationship, or Temp for a one-time browser connection. Switching the mode changes the kind of pairing requested; it does not convert an already connected device.",
        "Use the current four-digit Connect PIN or let the display device scan the QR. Copy URL copies a branded customer-display URL containing the current PIN and selected mode. The code expires after ten minutes; do not photograph, email, or publish it as a reusable register link.",
        "On the display device, open https://pos.getcentri.com/customer-display, enter the four digits, choose Install on this checkout or Temporary join to match the POS mode, and choose Install Display or Connect Display. Scan Pairing QR Code performs the same pairing request without manually typing the digits.",
        "When the display says Waiting for Approval, return to the POS. Confirm that the requested installed/temporary type and displayed device identity belong to the screen in front of you, then choose Confirm Install or Confirm Join. Check Again only polls; it does not approve the request. Cancel abandons that device-side attempt.",
        "For an installed device, Customer Display Ready means the device retains its checkout trust and is waiting for the linked POS host to open the expected register. Retry reloads the state. Reset Link removes that device’s installed trust and requires a new PIN and approval, so do not use it simply because no cart is active.",
        "Wait for Display connected at the POS. Expand Display Management and verify the primary device nickname, masked ID fingerprint, Installed display or Temporary display type, display mode, Live health, and Last seen value. When additional devices exist, the panel reports how many more are connected.",
        "On a healthy paired screen with no active receipt items, Waiting for your associate to start a sale is the correct idle state. Begin a controlled cart on the linked register and add one safe demo item; do not use a live payment merely to test the display.",
        "Verify the customer-facing merchant header and current cart. The display can show store/location/register identity, customer and fulfillment summary, line names and variants, quantities, unit prices, line totals, discounts, subtotal, savings, tax, cash rounding, and total. Staff-only notes, internal controls, and unrelated customers must not appear.",
        "When a customer is attached, review the account card before leaving the display customer-facing. Supported content can include contact details, balance/store-credit/credit-limit context, linked household or company accounts, recent saved receipts, receipt status and items, and whether the current receipt will enter history after saving. Expose this only to the matched customer.",
        "Use the customer-facing edit controls only with the customer’s participation. Supported changes can update contact fields and fulfillment address, preferred date, or preferred time. Timing is a preference rather than a guaranteed route window. After Save, verify the POS receipt/customer context reflects the intended update before continuing.",
        "Make one safe change at the POS and confirm the paired display updates. The live broadcast carries the active sale, line items, customer information, signature state, and display mode; the display also reloads current data when necessary. If the wrong cart or customer appears, stop use and re-pair from the correct register.",
        "When an eCart link exists, Open This Cart On Your Phone shows a QR that opens the branded receipt checkout on the customer’s phone. This moves payment/checkout to the eCart page; it is not the customer-display pairing QR and scanning it does not install the tablet. After completion it becomes Receipt and Next Steps for the completed sale.",
        "If the register requires a signature, the display shows Review and Sign with store policies and a signature pad. The customer reviews, signs, and chooses Accept & Sign. Signature on File shows the captured image; Reset clears it and can reopen a payment gate, so use Reset only to correct the current customer’s signature.",
        "Complete any payment through the supported POS, terminal, or customer phone workflow. The display itself shows the live receipt and checkout handoff; a QR scan or signature does not prove payment. Verify the processor result and the CentriPOS payment row before relying on the display’s completion state.",
        "After the controlled sale completes, verify the customer display transitions to the completed receipt/next-step state and no prior customer data remains available when the next cart begins. Close or reset the display according to store device policy before leaving a temporary or public-facing device unattended.",
        "Use Refresh or Check first when the POS status looks stale. New PIN creates a fresh setup code. Clear all resets every installed link and disconnects temporary or pending pairings for that register; use it only when the whole register’s display trust must be rebuilt, then pair every intended device again."
      ],
      "controls": [
        {
          "name": "Customer Display monitor",
          "description": "Exact Monitor icon in the register information bar; unavailable until the selected register session is open."
        },
        {
          "name": "Customer display unavailable",
          "description": "Closed/no active register session, so pairing and management cannot proceed."
        },
        {
          "name": "Customer display not connected",
          "description": "Open register with no approved active display."
        },
        {
          "name": "Installed",
          "description": "Pairing mode for a dedicated trusted checkout display."
        },
        {
          "name": "Temp",
          "description": "Pairing mode for a one-time browser display."
        },
        {
          "name": "Connect PIN",
          "description": "Four-digit pairing code with a ten-minute lifetime."
        },
        {
          "name": "Pairing QR",
          "description": "Encodes the same current display PIN and installed/temporary mode for device setup."
        },
        {
          "name": "Copy URL",
          "description": "Copies the branded display launcher with current setup data; it is not a permanent public link."
        },
        {
          "name": "Install on this checkout / Temporary join",
          "description": "Display-side choice that must match the intended pairing relationship."
        },
        {
          "name": "Waiting for Approval",
          "description": "Valid request that still requires explicit confirmation at the POS."
        },
        {
          "name": "Confirm Install / Confirm Join",
          "description": "POS approval for the exact pending display request."
        },
        {
          "name": "Check Again",
          "description": "Display-side status poll; it does not grant approval."
        },
        {
          "name": "Customer Display Ready",
          "description": "Installed trust exists, but the screen is waiting for its linked checkout host/open register."
        },
        {
          "name": "Retry",
          "description": "Reloads the installed display state without removing trust."
        },
        {
          "name": "Reset Link",
          "description": "Removes installed trust from that one display device."
        },
        {
          "name": "Display connected",
          "description": "At least one approved display is attached to the current register scope."
        },
        {
          "name": "Display Management",
          "description": "Register-level device detail and reset panel."
        },
        {
          "name": "Device nickname / masked ID",
          "description": "Human-readable device label plus shortened fingerprint used to verify the physical request."
        },
        {
          "name": "Installed display / Temporary display",
          "description": "Connection type of the attached device."
        },
        {
          "name": "Live / Stale",
          "description": "Health derived from recent check-in; Stale means the device has not checked in within the supported 75-second window."
        },
        {
          "name": "Last seen",
          "description": "Age of the latest display check-in."
        },
        {
          "name": "Additional connected devices",
          "description": "Count beyond the primary device shown in detail."
        },
        {
          "name": "Waiting for your associate to start a sale",
          "description": "Healthy idle display with no active cart items."
        },
        {
          "name": "Customer & Fulfillment",
          "description": "Matched customer details, account context, and supported delivery/pickup/shipping information."
        },
        {
          "name": "Account Snapshot",
          "description": "Linked household/company accounts and saved purchase history for the matched customer; protect it from unrelated viewers."
        },
        {
          "name": "Edit contact / fulfillment",
          "description": "Customer-participation controls for supported profile and fulfillment preferences."
        },
        {
          "name": "Your Items",
          "description": "Customer-safe line names, variants, quantities, unit prices, fulfillment detail, discounts, and line totals."
        },
        {
          "name": "Subtotal / Savings / Tax / Cash rounding / Total",
          "description": "Live persisted receipt calculation presented to the customer."
        },
        {
          "name": "Open This Cart On Your Phone",
          "description": "Receipt-specific eCart QR for continuing checkout on a phone; different from pairing QR."
        },
        {
          "name": "Receipt and Next Steps",
          "description": "Completed-sale version of the customer phone handoff."
        },
        {
          "name": "Review and Sign",
          "description": "Register-required policy and signature workflow."
        },
        {
          "name": "Signature on File / Reset",
          "description": "Captured signature evidence and correction control for the current receipt."
        },
        {
          "name": "Refresh / Check",
          "description": "Status and pairing reread that preserves trusted links."
        },
        {
          "name": "New PIN",
          "description": "Fresh short-lived setup code for a new pairing attempt."
        },
        {
          "name": "Clear all",
          "description": "Destructive register-level reset of all installed trust plus temporary/pending pairings."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no safe exact Customer Display pairing or customer-facing cart capture, so this guide intentionally uses no fabricated or unrelated image."
        }
      ],
      "expectedResult": "The customer sees the correct merchant identity, cart lines, totals, prompts, and payment or receipt state without staff-only notes, controls, or unrelated customer data.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "connected-device",
      "url": "https://platform.getcentri.com/centripos/connected-device",
      "title": "Pair and manage a connected CentriPOS device",
      "summary": "Use the branded /device launcher to pair a dedicated or temporary Customer Display or Barcode Scanner to one active register session, approve the join from the POS, verify health, and safely disconnect or clear stale trust.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Connected devices",
      "introduction": "Connected Device is not a terminal-payment pairing screen. It launches CentriDisplay Customer Display or Barcode Scanner, both backed by the register’s active customer-display session service. The register must be open to create a PIN. A four-digit PIN/QR is short-lived pairing authority: keep it within sight of the intended device and confirm the recognizable device name/ID at the POS. Installed devices retain trusted pairing for automatic reconnection to their checkout host; Temporary joins are session-oriented. Barcode scans add immediately to the live Sell cart, so test with a controlled item and remove it afterward.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "On the POS host, confirm the intended business, location, register, active session, and empty/safe Sell cart. Open the Customer Display monitor control in the operating-context bar. If the register is closed, the control is unavailable and says to open the register first.",
        "Read Customer Display status before creating anything. Connected means at least one live trusted/joined device is attached; Pending install needs POS approval; Disconnected has no active display; Error means the status service could not be read. Refresh status once before assuming the device is gone.",
        "Choose Installed for a dedicated display/scanner that should retain trust and reconnect automatically with its checkout host. Choose Temp for a spare phone/tablet or one-time join. Switching modes changes the type requested for the next PIN/URL; it does not transform an existing connected device.",
        "Generate or refresh the four-digit Connect PIN. The POS also shows a QR encoding the branded https://pos.getcentri.com/customer-display URL with pin and installed/temporary mode. Copy URL only to the device being paired. New PIN requests replace/refresh the pending code; do not publish it.",
        "On the companion phone/tablet/PAX browser, open https://pos.getcentri.com/device. Choose Customer Display to show live cart, customer-facing terms/signature/checkout QR, or Barcode Scanner to send product scans into the connected register. This launcher selection sets the device surface; it does not select the store/register itself.",
        "Enter a recognizable Display Name, up to 40 characters, such as Front Counter iPad or Front Counter Scanner. The page also shows a device-ID suffix. On a shared network, use both name and ID when approving so a nearby unknown device cannot claim the PIN.",
        "Choose Install on this checkout or Temporary join to match the POS mode, then enter the four digits and choose Install/Connect. Alternatively choose Scan Pairing QR Code and scan the POS QR; pasted pairing URL or plain four-digit PIN is also parsed by the scanner dialog. Reject any value that says it is not a CentriDisplay pairing code.",
        "Wait on Waiting for Approval. The device is pending and cannot view the live sale yet. Return to the POS, verify the requested device name, fingerprint/ID, and connection type, then choose Confirm Install or Confirm Join. Never approve an unexpected request.",
        "Wait for Customer display installed or Customer display joined on the POS. On the device, installed mode can show Customer Display Ready while waiting for the trusted checkout host/register to become active; temporary mode connects to the approved current session. Use Check Again/Retry or one status refresh rather than generating repeated codes.",
        "For Customer Display, verify the real store branding and register name, then the Waiting for your associate to start a sale ready state. Add one controlled non-sensitive cart item and verify live item/total/customer display behavior. Do not expose a real customer while testing. Remove/clear the test cart and confirm the display returns to ready.",
        "For Barcode Scanner, verify Connected to [register] and Ready for the next barcode. Scan one controlled product with the camera or paired Bluetooth/USB scanner. The code is sent to the live register and can add immediately; confirm Last Scan, product/variant feedback, and the exact item in Sell. Remove the test line before normal use.",
        "Back on the POS, expand Display Management. Confirm primary nickname, device fingerprint, Live versus Stale health, Installed/Temporary type, display mode, last seen, and any extra connected-device count. A connected badge is not enough—verify the named device and recent heartbeat.",
        "Use Refresh to recheck status without changing trust. New PIN is for a new/pending connection. Clear all calls the register/session link reset, wipes stale trust and pending joins, and then prepares a fresh pairing; it disconnects legitimate displays too, so use only with authorization.",
        "On a companion device, Disconnect ends a temporary pairing through the service. An installed ready screen offers Reset Link, which clears that device’s installed trust. After either action, verify the POS status and that the old device no longer receives cart data or sends scans.",
        "If Sale/Display reports stale or unavailable, confirm network, open register/session, correct host/register, recent last-seen, current device ID, and backend status. An installed device is tied to its trusted host checkout; it may wait when that host is inactive. Do not pair it to a different live register just to hide a host problem.",
        "Treat customer-display data as customer information. The connected display can show live cart, attached customer details, terms/signature, checkout links/QR, and sale context; keep it customer-facing, physically secure, and out of screenshots. The scanner surface can mutate the cart. Disconnect/reset retired, lost, or repurposed devices immediately."
      ],
      "controls": [
        {
          "name": "/device launcher",
          "description": "Branded choice between Customer Display and Barcode Scanner; it does not itself pair or select a register."
        },
        {
          "name": "Customer Display",
          "description": "Live customer-facing cart, supported customer details, terms/signature, and checkout QR experience."
        },
        {
          "name": "Barcode Scanner",
          "description": "Companion scanning surface whose accepted scans add immediately to the connected Sell cart."
        },
        {
          "name": "Open register required",
          "description": "Pairing PIN and live session data depend on an active register session."
        },
        {
          "name": "Installed mode",
          "description": "Dedicated trusted device that can reconnect automatically when its linked checkout host opens the register."
        },
        {
          "name": "Temporary mode",
          "description": "One-time/session-oriented device join."
        },
        {
          "name": "Connect PIN",
          "description": "Short-lived four-digit pairing authority generated for the active session/type."
        },
        {
          "name": "Pairing QR / Copy URL",
          "description": "Branded URL containing PIN and mode; share only with the intended nearby device."
        },
        {
          "name": "Display Name / device ID",
          "description": "Human nickname plus fingerprint suffix used to verify the request at POS approval."
        },
        {
          "name": "Waiting for Approval",
          "description": "Pending device cannot view live sale until POS chooses Confirm Install/Join."
        },
        {
          "name": "Confirm Install / Confirm Join",
          "description": "POS approval binding the named pending device to the active register/session trust model."
        },
        {
          "name": "Customer Display Ready",
          "description": "Installed device is trusted but waiting for its linked checkout host/register to become active."
        },
        {
          "name": "Live / Stale",
          "description": "Health derived from connected-device heartbeat/last-seen evidence."
        },
        {
          "name": "Display Management",
          "description": "Shows primary device, fingerprint, type/mode, last seen, and extra-device count."
        },
        {
          "name": "Refresh / Check",
          "description": "Re-reads pairing/status without intentionally clearing trust."
        },
        {
          "name": "New PIN",
          "description": "Refreshes/creates pending pairing authority; not a device-health repair."
        },
        {
          "name": "Clear all",
          "description": "Resets register display links and pending/trusted connections; disruptive to legitimate devices."
        },
        {
          "name": "Disconnect",
          "description": "Ends the current paired device connection; temporary joins call disconnect_pairing."
        },
        {
          "name": "Reset Link",
          "description": "Clears installed trust on the companion device."
        },
        {
          "name": "Last Scan",
          "description": "Scanner feedback for accepted/rejected code and matched product/variant; confirm the Sell cart."
        },
        {
          "name": "Not payment-terminal pairing",
          "description": "CentriPay terminal devices are managed per location/register elsewhere."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no safe Connected Device pairing capture. A real image would expose an active PIN/QR/device fingerprint or customer cart, so no fabricated or live-secret screenshot is used."
        }
      ],
      "expectedResult": "The branded device path opens the intended CentriPOS surface, pairs or signs in under authorized context, and does not expose internal service or storage URLs.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "ecart",
      "url": "https://platform.getcentri.com/centripos/ecart",
      "title": "Create and send an eCart",
      "summary": "Publish a live, branded customer checkout link; safely send or scan it; keep the receipt synchronized; collect any required acknowledgment or signature; and verify each online payment in CentriPOS.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "An eCart publishes the current receipt as a resumable customer checkout—not a static quote and not proof of payment. Publishing can create or update the saved sale, line items, totals, customer, fulfillment, payments already received, signature metadata, and a secure posted token. Confirm the active business, location, register, customer, cart, and payment setup before exposing the link.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Build or reopen the intended sale in Register → Sell. Attach the exact customer when the order should show or update a customer profile, save a payment method, or use customer-specific fulfillment and financing information. An unattached checkout can still exist, but the customer cannot save profile edits to a missing customer record.",
        "Review every nonzero cart line, variant, quantity, unit price, line and cart discount, promotion, tax, fulfillment type/date/address, note, customer source, prior payment, total, and balance. Publishing saves the receipt in its resumable workflow—normally Parked for a new eCart—rather than completing it.",
        "Choose the cart’s eCart/post action once. If the cart mixes Katapult-leasable and nonleasable products, CentriPOS names the noneligible items and offers Go Back or Post Anyway. Card checkout can remain available, but Katapult stays unavailable until the receipt contains only eligible items and meets its configured minimum.",
        "Wait for E-Cart Checkout Link. CentriPOS creates or reuses the receipt and token, synchronizes persisted sale lines and payments, and attempts to copy the branded pos.getcentri.com cart link automatically. A copied link is only access to the checkout; it is not a sent message or paid order.",
        "Confirm the receipt badge, Paid badge, and Balance badge. Use Open link in new tab to inspect the customer page before sharing. Verify the merchant logo/name, location and register, receipt number, intended customer, fulfillment, items, discounts, taxes, prior payments, and balance without entering a real payment.",
        "To copy manually, choose the Copy icon. The QR beneath Or scan to pay encodes the same eCart link and can be shown on a customer-facing screen or printed for the customer to scan. The separate Customer Display (Tablet/iPad) section contains the persistent display setup URL, not the receipt payment link.",
        "For Text Checkout, verify or enter the phone number, review the editable Customer notice, and keep it short enough for the displayed notice/segment limit. The system adds the checkout link and STOP opt-out text. Confirm the transactional-text consent checkbox and the location’s configured Dialpad or CentriPOS Notifyer sender before choosing Send.",
        "For Email Link, verify the email address and editable message, then choose Send once. A successful text or email records sale communication activity when logging succeeds; Message sent, but the communication log did not save means delivery was attempted but its CentriPOS activity entry failed. Neither result proves the customer opened or paid the eCart.",
        "Use Refresh e-cart link only when the previous customer link must be replaced or the latest persisted receipt needs to be republished. It creates a fresh posted token and link and can re-push current cart lines and totals. Stop distributing the old link, copy the new one, reopen it, and recheck Paid and Balance before sending again.",
        "On the customer page, confirm the merchant identity, associate when shown, receipt number, location contact details, and Live — your associate is editing this cart now or Not currently being edited state. The page subscribes to sale, line-item, payment, and supported customer changes; allow the brief update delay before assuming the link is stale.",
        "Review Customer & Fulfillment Summary. Edit My Profile can change name, email, phone, and address only when a customer profile is attached; Save contact updates those contact fields but does not change account permissions. Confirm fulfillment type and destination after any edit.",
        "Review Your Items, quantities, product/variant identity, fulfillment adjustments, discounts, subtotal, tax, total, Payments Received, Amount Paid, and Balance Due. If the associate changes the receipt, wait for the live update and recheck the complete total rather than paying from an older screenshot.",
        "Complete the Payment Authorization checkbox when it is required. If register settings require a customer signature or gate payments behind it, draw or type the signer’s full name and choose Accept & Sign. Payment controls remain blocked until every required acknowledgment and signature has been saved.",
        "Choose only an eligible configured payment method. North Embedded Checkout may present Card / Bank Account in one secure embedded flow. The alternate gateway can show Credit / Debit Card and, when enabled, a separate Bank Account (ACH) option. Financing appears only when PayTomorrow or Katapult is configured and the current receipt passes its provider rules.",
        "For card or ACH, choose Full balance or Custom amount. A custom amount must be greater than $0.00, use no more than two decimal places, and cannot exceed Balance Due; the page shows what will remain. Complete the secure processor form once. Do not refresh, reopen, or retry while the processor result is uncertain.",
        "For PayTomorrow, confirm the displayed minimum and that only the remaining balance is submitted after prior payments, then complete the application in the newly opened provider tab. For Katapult, confirm every item is leasable, the customer has the required email, phone, street/city/state/ZIP, and the post-tax-removal balance meets the minimum before the provider checkout loads. Provider application or lease approval is separate from a posted CentriPOS payment.",
        "After an approved payment, verify the eCart updates Amount Paid and Balance Due. A partial payment leaves the receipt open with a remaining balance; a fully paid completed receipt shows Payment Complete and its receipt number. Back in CentriPOS, verify the E-cart payment received notification, one payment row with the expected amount/provider/reference, correct receipt status, remaining balance, and any fulfillment-needs-action notice.",
        "If the page shows Cart Not Found or says the link is invalid or expired, ask the store to open the exact receipt and create a fresh eCart link. Never request or share the token separately, and never send screenshots containing customer contact information, signatures, full receipts, or payment credentials to support."
      ],
      "controls": [
        {
          "name": "E-Cart Checkout Link",
          "description": "Staff dialog for the current receipt’s branded customer checkout URL, receipt badge, sharing tools, QR, and totals."
        },
        {
          "name": "Automatic copy",
          "description": "CentriPOS attempts to copy the checkout URL when the dialog opens; clipboard failure leaves the visible Copy control available."
        },
        {
          "name": "Receipt badge",
          "description": "Sale number attached to the published eCart."
        },
        {
          "name": "Paid / Balance badges",
          "description": "Amounts already collected and still due when the dialog was prepared; recheck after refreshing or editing."
        },
        {
          "name": "Open link in new tab",
          "description": "Read-only preview opportunity for the exact customer checkout before it is shared."
        },
        {
          "name": "Copy",
          "description": "Copies the current eCart URL; it does not message the customer."
        },
        {
          "name": "Refresh e-cart link",
          "description": "Creates a fresh posted token and can republish current lines/totals; replace the prior distributed URL deliberately."
        },
        {
          "name": "Text Checkout",
          "description": "Transactional SMS workflow with phone, editable notice, system-added link/STOP text, consent confirmation, length guard, and configured sender routing."
        },
        {
          "name": "Email Link",
          "description": "Customer-link email workflow with recipient and editable message."
        },
        {
          "name": "Communication activity",
          "description": "Records the channel, recipient, sale, communication kind, link, and supported sender metadata after sending; logging can fail separately from send."
        },
        {
          "name": "Or scan to pay",
          "description": "QR representation of this receipt’s eCart link."
        },
        {
          "name": "Customer Display (Tablet/iPad)",
          "description": "Optional persistent register-display setup URL; it is different from the receipt checkout QR."
        },
        {
          "name": "Live editing state",
          "description": "Shows whether an associate is actively editing and the most recent activity context."
        },
        {
          "name": "Edit My Profile",
          "description": "Customer contact-field editor available for an attached customer; it does not change permissions or create a missing profile."
        },
        {
          "name": "Customer & Fulfillment Summary",
          "description": "Customer identity/contact/account context plus carry out, delivery, pickup, shipping, or other fulfillment details."
        },
        {
          "name": "Your Items / Fulfillment Adjustment",
          "description": "Customer-safe persisted receipt lines, including supported fulfillment charge and credit presentation."
        },
        {
          "name": "Payments Received / Amount Paid / Balance Due",
          "description": "Existing payment evidence and remaining customer obligation returned by the live cart lookup."
        },
        {
          "name": "Payment Authorization",
          "description": "Required checkbox when the eCart acknowledgment policy is enabled and required."
        },
        {
          "name": "Customer Signature",
          "description": "Drawn or typed full-name acknowledgment; register settings can require it and block payment until saved."
        },
        {
          "name": "Card / Bank Account",
          "description": "North Embedded Checkout presentation when North eCart is connected and enabled for supported tenders."
        },
        {
          "name": "Credit / Debit Card / Bank Account (ACH)",
          "description": "Alternate secure gateway choices; ACH appears only when separately enabled and eligible."
        },
        {
          "name": "Full balance / Custom amount",
          "description": "Card/ACH amount choice. Custom must be positive, no more than the balance, and is normalized to two decimal places."
        },
        {
          "name": "Financing",
          "description": "PayTomorrow and/or Katapult choices shown only when configured and eligible for the receipt."
        },
        {
          "name": "Katapult eligibility",
          "description": "Requires provider setup, minimum balance, customer contact/address fields, and all leasable items; mixed carts name noneligible products."
        },
        {
          "name": "Cart Not Found",
          "description": "The posted token cannot load a valid current receipt; obtain a fresh branded link from the store."
        },
        {
          "name": "Payment Complete",
          "description": "Customer confirmation for a fully paid completed receipt; still verify the CentriPOS payment row and receipt activity."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains an Admin E-Cart Settings screen, not a safe customer checkout or staff link dialog, so this guide intentionally uses no substituted image."
        }
      ],
      "expectedResult": "The intended customer receives one branded E-Cart link whose items, quantities, prices, tax, fulfillment, acknowledgment, balance, and status match the reviewed cart.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "online-store",
      "url": "https://platform.getcentri.com/centripos/online-store",
      "title": "Use the CentriPOS Online Store",
      "summary": "Browse a published merchant catalog, select product options, manage the local browser cart, choose an available fulfillment and payment path, and retain the confirmed order number.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "The public storefront does not require a Centri Account. It is available only when the merchant publishes it on its branded pos.getcentri.com/store address or verified custom storefront domain. The current shopper pages do not display inventory counts, an in-stock promise, customer order history, or a self-service tracking portal.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Open the merchant’s published storefront link and confirm the store name and domain before entering information. Store not found means the address is wrong, the slug or domain no longer resolves to that merchant, or the store is not published.",
        "On the storefront home, use Search products and choose the search button or press Enter. Select a category pill to filter the catalog; select the same category again to clear it, or choose All to clear category and brand filter state. Although product brand names can appear on cards, the current home page does not show a separate brand-filter control.",
        "Read each product card’s image, brand when present, name, and price. A multi-variant product can show a price range. Select the card to open its product page. No products found is a valid empty result for the current search, category, or published catalog.",
        "On the product page, review the image gallery, product name, brand, categories, description, displayed price, and SKU. If Options appears, select one active variant before choosing Add to cart; the selected variant can change the price and SKU. The page does not currently show an inventory quantity or availability promise.",
        "Choose Add to cart. The cart opens from the right and shows each item, selected variant, unit price, quantity, and subtotal. Use minus or plus to change quantity, or the × control to remove an item. Quantity zero removes that product-and-variant line.",
        "The cart is saved in this browser’s local storage. It can remain after closing the page, but it is not a reserved order and it does not prove the product, price, or fulfillment is still available. Review the cart again when returning on another day.",
        "Choose Checkout. Enter First name and Email; those are the fields visibly marked and validated as required. Last name and Phone are optional on the form. For shipping or local delivery, enter the address, city, state, and ZIP accurately even though the current fields are not visibly marked required, because tax and fulfillment depend on them.",
        "Choose Ship to address, Pickup in store, or Local delivery when that option is available. Pickup requires a location and pickup date. Local delivery appears only when an enabled delivery method applies to the configured online-store location and register; select the method and delivery date. The displayed delivery fee follows the method’s current price setting.",
        "Review Tax in the Order summary. CentriPOS looks up tax when the merchant is configured to collect for the entered state or always collect. A blank or zero tax amount can reflect the merchant’s nexus settings or an incomplete/failed address lookup; it is not a shopper guarantee that tax is legally unnecessary.",
        "Review the available payment choices. Credit / Debit appears only when the merchant has a connected online gateway and tokenization key; 3D Secure may ask for bank verification. PayTomorrow or Katapult appears only when enabled for the online-store register and redirects to the provider after the CentriPOS order is created.",
        "If no card gateway is available, the button says Place order and the page states Payment will be collected upon fulfillment. That creates a pending storefront order; it does not mean the balance was paid. Do not send card numbers by email, chat, or a support screenshot.",
        "Before submitting, compare every product, variant, quantity, subtotal, delivery or pickup choice, tax, and total in Order summary. Choose Pay, Apply for financing, Apply for lease, or Place order once and wait. Repeated submission after a timeout can create uncertainty; contact the merchant with the exact time and total before trying again.",
        "Completion is proven by Order placed! and the displayed order number. Save that number or take a customer-safe screenshot. The page says a confirmation will be sent to the email, but the current storefront checkout path does not itself prove delivery of a confirmation message; do not close the page relying only on an expected email.",
        "Choose Continue shopping to return to the storefront. The current public storefront has no sign-in, order-history page, or tracking screen. For status, payment, changes, cancellation, pickup, delivery, or return questions, contact the merchant and provide the order number. CentriPOS staff receive the order in the configured online-store location/register and can work it from Order Intake, Receipts, and Fulfillment Center as appropriate."
      ],
      "controls": [
        {
          "name": "Published storefront",
          "description": "Public merchant catalog resolved from the platform slug or verified custom storefront domain."
        },
        {
          "name": "Store not found",
          "description": "The host or slug does not resolve to a published storefront."
        },
        {
          "name": "Search products",
          "description": "Runs the entered catalog search when the search button is chosen or Enter is pressed."
        },
        {
          "name": "Category pill",
          "description": "Filters products by one published category; choosing it again clears that category."
        },
        {
          "name": "All",
          "description": "Clears active category and brand filter state."
        },
        {
          "name": "Product card",
          "description": "Published image, brand when present, product name, and price or variant price range."
        },
        {
          "name": "Product page",
          "description": "Image gallery, brand, name, categories, description, active options, price, and SKU."
        },
        {
          "name": "Options",
          "description": "Active product variants; one must be selected when more than one is available."
        },
        {
          "name": "Add to cart",
          "description": "Adds the selected product and variant or increases the matching line’s quantity."
        },
        {
          "name": "Browser-local cart",
          "description": "Cart saved on that device/browser; it does not reserve stock or create an order."
        },
        {
          "name": "Minus / plus",
          "description": "Changes the line quantity; reducing to zero removes it."
        },
        {
          "name": "Cart subtotal",
          "description": "Current line prices before delivery and tax."
        },
        {
          "name": "Ship to address",
          "description": "Standard shipping selection; current storefront shows no configurable shipping-rate charge on this path."
        },
        {
          "name": "Pickup in store",
          "description": "Requires a pickup location and a date no earlier than tomorrow."
        },
        {
          "name": "Local delivery",
          "description": "Shown only when an enabled method applies to the configured online-store location/register; requires method and date."
        },
        {
          "name": "Contact information",
          "description": "First name and email are required by the visible checkout validation; last name and phone are optional."
        },
        {
          "name": "Tax",
          "description": "Address-based amount calculated only when the merchant’s collection configuration says the entered state has nexus or tax is always collected."
        },
        {
          "name": "Credit / Debit",
          "description": "Tokenized NMI/CentriPay-style online card path when connected; may include 3D Secure issuer verification."
        },
        {
          "name": "PayTomorrow",
          "description": "Enabled financing path that creates the storefront order and then opens the provider application."
        },
        {
          "name": "Katapult",
          "description": "Enabled lease-to-own path that creates the storefront order and then opens the provider application."
        },
        {
          "name": "Payment will be collected upon fulfillment",
          "description": "No online card gateway is available; the order is recorded as pending rather than paid."
        },
        {
          "name": "Order summary",
          "description": "Items, variants, quantities, subtotal, applicable delivery charge, pickup indicator, tax, and total."
        },
        {
          "name": "Order placed!",
          "description": "Success state returned after CentriPOS creates the storefront order."
        },
        {
          "name": "Order number",
          "description": "Primary customer reference to retain for merchant support."
        },
        {
          "name": "Continue shopping",
          "description": "Clears the completed cart and returns to the storefront."
        },
        {
          "name": "No customer order portal",
          "description": "The current public storefront does not provide sign-in, order history, or tracking."
        },
        {
          "name": "Staff handoff",
          "description": "Merchant staff work the submitted record from their configured online-store context and operational CentriPOS screens."
        }
      ],
      "expectedResult": "The published storefront shows the intended merchant and eligible catalog, the shopper submits the reviewed product, variant, fulfillment, tax, and available payment choices exactly once, and the Order placed screen returns an order number that can be matched to the merchant’s CentriPOS order record.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-portal",
      "url": "https://platform.getcentri.com/centripos/customer-portal",
      "title": "Use the Customer Account Portal",
      "summary": "Access the correct business account, review enabled invoices and receipts, prepare or open statements, and use only the payment and saved-method actions available to that account.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "The Customer Account Portal is separate from staff CentriPOS. Customers can use an authorized private account link or the customer sign-in methods offered at /my. Available sections and payment choices depend on the business and account. Keep every private account, invoice and statement link confidential; a page or document is not proof of settlement.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Open the customer portal link supplied by the business, or open the branded pos.getcentri.com/my customer sign-in page. Confirm the business and account identity. Do not enter staff credentials into a customer payment form or forward someone else’s private link.",
        "When signing in, use an offered method associated with your verified customer identity: Email code, an established Password, an emailed sign-in link, or optional Text me a code for an already verified phone. Enter a one-time code only on the legitimate sign-in page. The generic code-sent message does not disclose whether another person has an account.",
        "If your verified identity has access to more than one account or business, choose the intended customer profile and business before reviewing balances. A profile at one business does not grant access to another business’s records.",
        "If an account link is unavailable or expired, request fresh access through the business. Do not edit a token or repeatedly try another customer’s URL. Keep private links and sign-in codes out of screenshots and support messages.",
        "After loading, confirm the merchant and customer/company name, then read Open balance, Store credit, receipt history and other enabled summary cards. Store credit is separate from money owed, and a displayed balance must be reconciled if its itemized obligations disagree.",
        "Use the sections actually offered for the account. Overview and Balances are the core tabs; the business can also enable Receipts, Payments, Deliveries, Warranties, Events and Loyalty. Changing tabs updates the customer-portal route while retaining the same authorized account.",
        "Use Overview for account information, recent documents and available statement tools. Review the date, type and scope on a statement rather than assuming every statement covers the last 30 days. A prepared historical statement can differ from today’s open balance.",
        "Use Balances to inspect each open sale/invoice, date, due date, status and remaining balance. Open the exact document to compare line items, payments, attachments and any delivery evidence returned for that invoice. A document number by itself is not proof of payment.",
        "Use Receipts for the available customer document history. A record can represent a receipt, open invoice or paid invoice. Open the branded document or its offered PDF/attachment actions; files can contain private financial and delivery details.",
        "Use Pay only on an eligible current open item. The portal can prepare a new secure payment link for a payable receipt rather than requiring an existing stored link. If no payment path is available, contact the business; do not construct a link from an invoice ID.",
        "When selection controls and combined checkout are enabled, choose only the intended eligible items, review their count and combined balance, and continue through the offered secure checkout. Some invoices must be paid separately, and some accounts only show payment instructions. The presence of open items does not guarantee bulk payment is available.",
        "Before confirming payment, review the merchant, selected invoices, amount, method and any displayed fee. Enter new payment details only in the provided secure payment fields. If the page says Payment not enabled or shows a preview, no charge should be attempted there.",
        "If saved cards or bank accounts are offered, complete the required identity verification and choose the exact masked method. Saving a method, making it a default and authorizing automatic collection are separate choices. Use only controls actually enabled for this account.",
        "Use the available billing and statement tools to review enrolled schedules, statement type/history and secure statement links. A historical statement is a dated report; payment actions use current payable balances. Transaction Statement activity totals are not themselves an amount due.",
        "Use delivery, warranty, event or loyalty sections only for records returned to this customer. Event payment-plan or registration actions can have separate purchaser/participant permissions; never assume a link authorizes access to someone else’s private registration information.",
        "After a payment, wait for the original attempt’s result and refresh/reopen the account before deciding to retry. The page refreshes periodically and can briefly show cached data. Match the exact invoice and payment reference with staff if the result is uncertain; do not charge again merely because a headline balance has not changed.",
        "Use the portal’s security/account controls when available. On a shared device, Sign out and close private documents. If sign-out warns that revocation or browser cleanup could not be confirmed, follow the warning and contact the business before leaving the device unattended.",
        "For support, provide the business/account name, approximate time, visible section, safe invoice/receipt reference and exact error. Do not provide full private URLs, sign-in codes, account tokens, card/bank details or saved-method credentials."
      ],
      "controls": [
        {
          "name": "Customer sign-in",
          "description": "Offered email code, established password, sign-in link or optional verified-phone method; separate from staff access."
        },
        {
          "name": "Business/account chooser",
          "description": "Selects an authorized customer profile at the intended business."
        },
        {
          "name": "Overview / Balances",
          "description": "Core account summary and itemized current obligations."
        },
        {
          "name": "Available sections",
          "description": "Receipts, Payments, Deliveries, Warranties, Events and Loyalty depend on business configuration and account access."
        },
        {
          "name": "Pay / combined checkout",
          "description": "Only eligible current items and enabled payment flows can proceed; some invoices require separate checkout."
        },
        {
          "name": "Saved methods",
          "description": "Masked cards/bank accounts require the supported verification and collection permissions."
        },
        {
          "name": "Statement",
          "description": "Type/date/location-scoped report, distinct from the current payable balance."
        },
        {
          "name": "Sign out",
          "description": "Ends the customer session and attempts supported token/browser cleanup; heed any warning."
        }
      ],
      "expectedResult": "The authorized customer opens the intended business account, sees only its enabled records and actions, understands historical statements versus current payable balances, and can confirm document or payment outcomes without exposing private access links.",
      "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."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "public-receipt",
      "url": "https://platform.getcentri.com/centripos/public-receipt",
      "title": "Open a public receipt or fulfillment slip",
      "summary": "Use the correct branded bearer link, understand exactly what each public document reveals, download its matched PDF, and capture fulfillment acknowledgement without confusing a receipt with a payment-free slip.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "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.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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.",
        "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."
      ],
      "controls": [
        {
          "name": "Receipt Link",
          "description": "Unauthenticated bearer page with financial sale, item, fulfillment, payment, total, balance, policy, and PDF details."
        },
        {
          "name": "Fulfillment Slip",
          "description": "Unauthenticated bearer page focused on customer, fulfillment, items, notes, acknowledgement, and PDF without payment totals."
        },
        {
          "name": "pos.getcentri.com",
          "description": "Only approved customer-visible link host."
        },
        {
          "name": "Receipt prefix",
          "description": "`/r/` or supported tenant-scoped receipt path returned by link generation."
        },
        {
          "name": "Fulfillment prefix",
          "description": "`/f/` for public fulfillment slips."
        },
        {
          "name": "Token",
          "description": "Lowercase hexadecimal 20–64 character bearer secret; possession can grant document access."
        },
        {
          "name": "No Centri Account sign-in",
          "description": "Public document authorization is the token, not customer authentication."
        },
        {
          "name": "Receipt robots policy",
          "description": "noindex, nofollow, noarchive, nosnippet, and noimageindex set by Public Receipt."
        },
        {
          "name": "Fulfillment robots gap",
          "description": "Current Public Fulfillment Slip component does not set an equivalent robots meta policy."
        },
        {
          "name": "Logo palette",
          "description": "Receipt attempts to derive primary/secondary colors from the store logo, with fallback colors."
        },
        {
          "name": "Fulfillment block",
          "description": "Type/status and optional delivery address/phone for non-carry-out customer fulfillment."
        },
        {
          "name": "Visible merchandise",
          "description": "Nonzero-quantity lines excluding detected fulfillment-charge items."
        },
        {
          "name": "Fulfillment fee",
          "description": "Detected charge lines summarized outside merchandise subtotal."
        },
        {
          "name": "Line discount detail",
          "description": "Shown only when the selected receipt template enables it."
        },
        {
          "name": "Payment detail",
          "description": "Method/amount; CentriPay Cloud can also expose transaction ID, authorization code, brand, and last four."
        },
        {
          "name": "Store policies",
          "description": "Sanitized returned/template rich HTML."
        },
        {
          "name": "Receipt Download PDF",
          "description": "`/receipt-pdf/<token>` using the same bearer authorization."
        },
        {
          "name": "Expired receipt experience",
          "description": "410 contextual or generic 404/403/429/failure presentation; wording does not prove cause."
        },
        {
          "name": "Fulfillment customer details",
          "description": "Name/phone plus location and optional served-by identity."
        },
        {
          "name": "Item notes",
          "description": "Public on fulfillment slip and potentially sensitive."
        },
        {
          "name": "Fulfillment Download PDF",
          "description": "`/fulfillment-slip-pdf/<token>` with payment-free intent."
        },
        {
          "name": "Sign",
          "description": "Opens contained acknowledgement signature pad when no signature exists."
        },
        {
          "name": "Signature payload",
          "description": "Data URL, capture mode, and optional device information posted with the bearer token."
        },
        {
          "name": "Signed",
          "description": "Stored signature image exists; public page does not show signer identity/time or undo."
        },
        {
          "name": "Unavailable slip",
          "description": "Generic GET failure/no-data state with no cause distinction."
        },
        {
          "name": "No public screenshot",
          "description": "No exact privacy-safe Harbor & Hearth public document capture exists."
        }
      ],
      "expectedResult": "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."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "fulfillment-slip",
      "url": "https://platform.getcentri.com/centripos/fulfillment-slip",
      "title": "Use a public fulfillment slip safely",
      "summary": "Open or share a branded token link for a scoped set of fulfillment lines, verify exactly which customer/store/item details are exposed, download the no-price PDF, and capture one fulfillment acknowledgment signature.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Shared links",
      "introduction": "A fulfillment-slip URL is a bearer link: anyone who has its active token can open the scoped slip without signing into CentriPOS and, while unsigned, submit the customer acknowledgment signature. It is marked noindex/nofollow/noarchive and responses are no-store, but those headers do not make a forwarded link private. The page hides payment totals, prices, cost, tax, discounts, tender, and broad sale notes; however it does show customer name/phone, store/location contact information, served-by identity, product/variant/SKU, quantities, and each included line item note. Review notes and recipients before sharing.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "For an associate, open Sales → Fulfillment Center and locate the exact fulfillment group. Verify receipt, customer, fulfillment type/method, origin location, items, quantities, and current status before generating a link. A group link is scoped to the line_item_ids captured at creation; it is not automatically every line on the sale.",
        "Choose the fulfillment link/share action. CentriPOS creates a new cryptographically random token in receipt_public_links with kind fulfillment_slip, sale/tenant, fulfillment type/method, optional adjustment sale number, exact line IDs, creator, and timestamps. Production links use the branded https://pos.getcentri.com host and tenant-scoped /f/ route.",
        "Before sending, open the new link yourself in a private/customer-style view. Confirm the store branding, receipt/slip number, customer name and phone, fulfillment label/date, public location name/address/phone/email, Served by identity, and every included product, variant, SKU, quantity, and line note. Remove inappropriate line notes in the operational record and regenerate/refresh the link if needed.",
        "Remember what is intentionally absent: item prices, sale subtotal/total, payments, balance, discounts, tax, vendor cost, administrative panels, and broad sale note are not returned by the public slip service. Customer email/address are loaded internally but the current web page displays only customer name/phone; the fulfillment destination is not displayed in this page’s customer block. Do not claim the link is anonymous or contains no private data.",
        "Copy, Text Link, or Email Link only to the verified recipient through an approved channel. Recheck the phone/email in the send form. The sender workflow can create another refreshed token; treat old links as active until their record expires or is revoked by an authorized process. Never paste a live link into public notes, tickets, analytics, or screenshots.",
        "For the recipient, open the exact branded link. A malformed, expired, revoked, wrong-kind, missing-line, or missing-sale token shows This fulfillment slip is unavailable. Contact the merchant using a trusted known number rather than sharing the token with an unknown third party.",
        "Confirm the merchant/logo and Fulfillment slip #. Then verify Customer, phone, fulfillment method/date, location/contact, Served by, and item table. The shown date is sale fulfillment_date when present, otherwise sale created_at. Method label prefers the link’s captured fulfillment method name.",
        "Review each line’s product name, variant, SKU, quantity, and note. The note is printed verbatim with whitespace formatting in the web view and included in the PDF. Stop and contact the merchant if the wrong item, variant, quantity, recipient, location, date, or instruction appears; do not sign an incorrect slip.",
        "Choose Download PDF when a fixed copy is needed. It opens/downloads a server-generated fulfillment PDF named from the sale number. The PDF includes store/location details, receipt number, customer name/phone, fulfillment/date, items/variants/SKUs/quantities/notes, and existing signature/date; it likewise omits payment totals and pricing. Store or forward it only under the business’s privacy policy.",
        "If unsigned and the customer is physically acknowledging pickup or receipt of fulfilled merchandise, choose Sign. Read the acknowledgment text, draw the customer’s own signature with consent, and submit once. Do not sign on a customer’s behalf or use this as authorization for payment, financing, return terms, warranty waiver, or delivery condition beyond the displayed acknowledgment.",
        "On success, Signature saved appears and the slip reloads to show Signed plus the signature image. CentriPOS stores the signature on the sale with source fulfillment_slip, signed time, signature/policy hashes, evidence package, client IP/user agent, line-item IDs, receipt number, and acknowledgment text. The link page does not provide undo, clear, resign, signer-name, or dispute controls.",
        "Understand that any existing sale signature causes this slip to display Signed, even if it originated from another supported signature flow. The UI then hides the Sign button. Verify the source/evidence in the authorized receipt/fulfillment workflow if the signature’s purpose is important.",
        "After acknowledgment, the associate should refresh the fulfillment/receipt record and verify signature presence/source/time and the correct line scope. Signing the public slip does not by itself mark items Ready, Out for delivery, Shipped, Picked up, Delivered, or Completed; update fulfillment status through the approved internal workflow.",
        "If the link reached the wrong person or exposes incorrect data, stop further sharing and have an authorized administrator revoke/replace it, then assess exposure using link metadata/last_accessed_at. Changing the visible token text or relying on noindex is not revocation."
      ],
      "controls": [
        {
          "name": "Bearer token link",
          "description": "Active hex token grants unauthenticated read access to the scoped slip and unsigned signature action. Possession is authorization."
        },
        {
          "name": "Branded host",
          "description": "Customer-facing production URL uses https://pos.getcentri.com with a tenant-scoped fulfillment route."
        },
        {
          "name": "Line scope",
          "description": "Exact line_item_ids stored when the link is created; only those lines are returned."
        },
        {
          "name": "Last accessed",
          "description": "Public service updates last_accessed_at whenever a valid slip is loaded."
        },
        {
          "name": "Expiry / revocation",
          "description": "Expired or revoked links are rejected; no public recipient control manages these states."
        },
        {
          "name": "Noindex/no-store headers",
          "description": "Discourage indexing/caching but do not prevent copying, screenshots, forwarding, or unauthorized use of a leaked token."
        },
        {
          "name": "Visible customer data",
          "description": "Customer name and phone. Customer email/address are not rendered in the current page."
        },
        {
          "name": "Visible store data",
          "description": "Store/logo, public location name/address, phone/email, and Served by display name/email fallback."
        },
        {
          "name": "Visible item data",
          "description": "Product name, variant, SKU, quantity, and line-item note for each scoped line."
        },
        {
          "name": "Hidden financial data",
          "description": "No item prices, subtotal/total, tax, discount, payment, balance, or vendor cost is returned/rendered."
        },
        {
          "name": "Line note exposure",
          "description": "Line note is customer-visible on web and PDF; it is not an internal-only field on this link."
        },
        {
          "name": "Download PDF",
          "description": "Generates a no-price PDF containing the same core identity/fulfillment/item/note/signature information."
        },
        {
          "name": "Sign",
          "description": "Unsigned-only customer acknowledgment that merchandise was picked up or received."
        },
        {
          "name": "Signed",
          "description": "Any existing resolved sale signature displays as signed; check evidence source when context matters."
        },
        {
          "name": "Signature evidence",
          "description": "Stores signature image/source, signed time, hashes, evidence package, IP/user agent, scoped lines, receipt, and acknowledgment metadata."
        },
        {
          "name": "Not a status update",
          "description": "Signature capture does not change fulfillment workflow status."
        },
        {
          "name": "Unavailable",
          "description": "Malformed, missing, expired, revoked, wrong-kind, unscoped, or missing-sale link."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no public fulfillment-slip capture. A real link would expose a live bearer token and customer/fulfillment data, so no fabricated or unsafe screenshot is published."
        }
      ],
      "expectedResult": "The generated slip contains the intended order, customer-safe destination, items, quantities, schedule, instructions, and barcode or reference for that fulfillment record.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "price-book-order-form",
      "url": "https://platform.getcentri.com/centripos/price-book-order-form",
      "title": "Submit a public price-book order request",
      "summary": "Unlock a store-branded price book, choose quantities, and send a request for the merchant to review and follow up on.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Shared ordering",
      "introduction": "A public order form is not a checkout. Submitting it records a reviewable request; it does not create a completed sale, reserve inventory, collect payment, schedule fulfillment, or guarantee acceptance. Every current link requires the separate six-character PIN generated by the store. Treat the link and PIN as customer-specific access details.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Open the branded price-book or order-form link supplied by the store. If the page says Order form unavailable, ask the store for a current link; the link may be expired, revoked, or mistyped. Do not alter or share its token.",
        "Enter the six-character Access PIN exactly as provided and choose Continue. The PIN may be numeric or use letters and numbers. It is not a Centri Account password. If the page says the store has not generated its PIN, ask the store to open the saved form and save or regenerate the access PIN.",
        "After unlocking, verify the form title, effective dates, store identity and contact details, and any header note. The Customer card can contain the customer or company name, address, phone, and email linked by the merchant; stop and contact the store if it is the wrong customer.",
        "Read the item table by section. Each row can show item number or SKU, product and variant, a line note, minimum or maximum guidance, quantity, unit price, and line total. The merchant decides whether prices are displayed. A Price Sheet is view-only and has no quantity or submission controls.",
        "For an Order Form, enter a whole-number quantity greater than zero for each requested item. Choose at least one item. Read any displayed minimum or maximum before submitting; the public screen shows this guidance, but the store still reviews the request.",
        "Enter the Submitter email used for order communication and, if needed, comma-separated addresses under Send a copy to. Review any customer information already shown rather than re-entering it into unrelated fields.",
        "Complete the merchant-configured Additional fields and Signatures / approvals that appear online. A signature box accepts a typed name or approval note; it is not a drawn signature or a processor authorization. Fields configured as print-only do not appear on this page.",
        "Review the Estimated subtotal. When prices are included, it is quantity multiplied by the displayed price; when prices are hidden, the page says Review required. In either case, the figure is an estimate and no payment is collected here.",
        "Choose Submit order request once. A valid request must include at least one item. Wait for the green Order request submitted message and note that the store will review and follow up. The button then becomes unavailable on that loaded page.",
        "If the confirmation is uncertain, do not repeatedly resubmit. Contact the store with the form title, customer name, approximate time, and requested items so staff can check Order Intake for an existing submitted request."
      ],
      "controls": [
        {
          "name": "Public link",
          "description": "Store-created tokenized URL for one saved price-book form. It can expire or be revoked and should be shared only with the intended recipient."
        },
        {
          "name": "Access PIN",
          "description": "Store-generated six-character numeric or alphanumeric code required by every current public form. It is separate from Centri Account sign-in."
        },
        {
          "name": "Price Sheet",
          "description": "View-only template that shows the merchant catalog and optional prices but no quantities, customer/order fields, or submit button."
        },
        {
          "name": "Order Form",
          "description": "Interactive template that can collect item quantities, contact details, configured fields, and typed approvals before creating a submission."
        },
        {
          "name": "Customer",
          "description": "Merchant-linked customer snapshot that may show company, name, address, phone, and email after PIN verification. Verify it belongs to the intended recipient."
        },
        {
          "name": "Order contact",
          "description": "Submitter email plus optional comma-separated copy recipients stored with the request for communication."
        },
        {
          "name": "Item Number / Item",
          "description": "SKU and product or variant identity supplied by the linked price book."
        },
        {
          "name": "Min / Max",
          "description": "Merchant-provided quantity guidance displayed beneath an item. Review it before submitting; final acceptance remains with the store."
        },
        {
          "name": "Additional fields",
          "description": "Online merchant-configured text inputs. Print-only fields are omitted from the public page."
        },
        {
          "name": "Signatures / approvals",
          "description": "Online text areas for a typed name or approval note. They do not charge a payment method."
        },
        {
          "name": "Estimated subtotal",
          "description": "Sum of requested quantity times price when prices are visible. Review required appears when the merchant hides pricing."
        },
        {
          "name": "Submit order request",
          "description": "Creates a submitted price-book intake record containing the customer snapshot, entered fields and approvals, selected line items, and calculated subtotal."
        },
        {
          "name": "Order Intake",
          "description": "Staff-side review workflow where the merchant can inspect and process the submission; the public submit action itself is not a sale."
        },
        {
          "name": "Order request submitted",
          "description": "Confirmation that the request was recorded and the store will review and follow up."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no exact public price-book form capture. A real form would expose a customer-specific token, PIN-protected customer data, and order details, so this guide does not use an invented or mismatched image."
        }
      ],
      "expectedResult": "The submitted order belongs to the intended merchant and price book, preserves reviewed items, quantities, prices, customer details, and fulfillment request, and enters Order Intake once.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "pay-invoice",
      "url": "https://platform.getcentri.com/centripos/pay-invoice",
      "title": "Pay a franchise invoice online",
      "summary": "Use the private /pay/<token> Network Billing page to review one HQ-to-franchise invoice and pay its full remaining balance plus the configured card or ACH convenience fee through secure NMI tokenization.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "This is the public Franchise Invoice page for Network Billing, not a retail Customer Account invoice, statement, or general A/R payment page. The current implementation shows a view-only notice unless franchise payment mutations are explicitly enabled and a tokenization key is available. If a payment form is enabled, its amount is the full returned invoice balance plus the selected method’s configured fee.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "Start from the authorized Network Billing invoice workflow and confirm the invoice number, HQ/franchisor, billed franchisee, status, due date, billing period, line items, current balance due, recipient, and whether the link is still valid. Do not use a Customer Account portal link for this workflow.",
        "Send only the branded https://pos.getcentri.com/pay/<token> URL created for that invoice. Treat the token as a private payment credential: do not post it in public support, analytics notes, screenshots, or shared documents, and do not change its characters or reuse another invoice’s link.",
        "When the page opens, wait for the spinner to finish. Invoice Not Found means the token is invalid or expired, the invoice is missing, or it has already been paid. The page does not distinguish those cases; return to the authorized invoice record before generating or sending another link.",
        "Confirm the header displays the intended HQ name and Franchise Invoice. Review Invoice number and status, Billed To franchisee, optional Due Date, optional Period, and every line-item description/amount before entering payment data. Stop if any identity, period, line, or total is unexpected.",
        "Read Total Due carefully. The base is the invoice’s remaining balance, not its original total. When the selected method has an enabled fee, the page adds either the configured percentage of balance due rounded to cents or the configured flat amount. It then rounds balance plus fee to cents.",
        "First check whether a payment form is available. This invoice is currently view-only / Online franchise payment collection is temporarily paused means no online collection should be attempted from this page. Contact the franchisor through the authorized billing workflow. Card/ACH choices apply only when the page actually enables its payment form.",
        "For Credit Card, enter Card Number, Expiration, and CVV only inside the NMI Collect.js-hosted fields. For ACH / Bank, enter Name on Account, Routing Number, and Account Number inside those hosted fields. CentriPOS receives a payment token rather than the raw field values from this form.",
        "Wait for the hosted fields to become ready. Pay <Total Due> remains disabled until Collect.js reports fields available and is disabled again while the payment request is pending. Do not double-click, reload, switch methods, or open a second payment tab after submission.",
        "Choose Pay <Total Due> once. The page starts the NMI token request, then sends the invoice token, one-time payment token, and selected cc or ach method to the public Network Billing payment action. An on-screen spinner means the mutation is still pending.",
        "If Payment failed: <message> appears, preserve the safe invoice number, selected method, amount/fee, time, and message. Check the invoice and processor evidence before retrying. Never send raw card/bank data, CVV, routing/account numbers, browser storage, or the payment token to support.",
        "If Payment Successful! appears, the page states that the invoice number has been paid. This is a customer-facing response from the payment action; an authorized billing user must still verify the invoice status, payment record, processor transaction, fee treatment, register/accounting impact when applicable, and bank settlement.",
        "If the form is replaced by the view-only notice, do not paste gateway keys into the URL, reuse another merchant’s link, or assume that adding a payment method elsewhere will activate this invoice. Franchise billing availability and the separate retail account invoice workflow must be verified independently.",
        "Invoice notes, when present, appear as small text below the payment area. Treat them as invoice context, not processor confirmation, payment instructions that override the form, or authorization to change amount/method outside the approved workflow.",
        "This checkout always attempts the full returned balance plus fee. It does not offer a partial/custom amount, apply store credit, select invoices, pay several items, show prior payments, save a card/bank account, issue a refund, or cancel/void the invoice. Use authorized Network Billing controls for later corrections.",
        "No screenshot is published because the approved Amelia Grant Harbor & Hearth set contains no safe exact /pay/<token> franchise invoice. A real capture would expose a private token, billing identities, invoice number, period, line items, amounts, and payment configuration; no generic A/R or fabricated checkout image is substituted."
      ],
      "controls": [
        {
          "name": "/pay/<token>",
          "description": "Branded public Network Billing checkout for one franchise invoice."
        },
        {
          "name": "Franchise Invoice",
          "description": "HQ/franchisor-to-franchisee billing document, not a retail Customer Account item."
        },
        {
          "name": "Invoice Not Found",
          "description": "Combined invalid/expired/missing/already-paid outcome; inspect the authorized invoice record."
        },
        {
          "name": "HQ name",
          "description": "Franchisor identity displayed above the invoice."
        },
        {
          "name": "Invoice / status",
          "description": "Invoice number and current returned billing status."
        },
        {
          "name": "Billed To",
          "description": "Franchisee business responsible for the invoice."
        },
        {
          "name": "Due Date / Period",
          "description": "Optional invoice due date and billing-period dates."
        },
        {
          "name": "Line items",
          "description": "Descriptions and amounts returned for this invoice."
        },
        {
          "name": "Convenience Fee",
          "description": "Method-specific enabled percentage or flat fee added to balance due."
        },
        {
          "name": "Total Due",
          "description": "Full remaining invoice balance plus the selected method fee, rounded to cents."
        },
        {
          "name": "Credit Card",
          "description": "NMI Collect.js fields for card number, expiration, and CVV."
        },
        {
          "name": "ACH / Bank",
          "description": "NMI Collect.js fields for account name, routing number, and account number."
        },
        {
          "name": "Secure tokenization",
          "description": "Hosted fields return a one-time payment token; raw values are not submitted by the React page."
        },
        {
          "name": "Pay <amount>",
          "description": "Single full-balance submission; disabled until fields are ready and while pending."
        },
        {
          "name": "Payment failed",
          "description": "Processor/billing action did not report success; reconcile before retrying."
        },
        {
          "name": "Payment Successful!",
          "description": "Customer-facing success for the invoice; still verify billing and processor records."
        },
        {
          "name": "Online payment is not available",
          "description": "No tokenization key was returned for the invoice."
        },
        {
          "name": "Invoice notes",
          "description": "Optional display text beneath the form; not settlement proof or an amount override."
        },
        {
          "name": "No partial payment",
          "description": "The page has no custom-amount control and submits invoice.balance_due plus fee."
        },
        {
          "name": "No exact screenshot",
          "description": "Private franchise billing/payment surface was not safely captured."
        },
        {
          "name": "This invoice is currently view-only",
          "description": "Payment form is unavailable unless franchise billing mutations and tokenization are both enabled."
        }
      ],
      "expectedResult": "The intended franchise billing contact can review the correct invoice. A view-only invoice remains uncharged; when a payment form is explicitly enabled, one confirmed payment must reconcile to the invoice, processor and accounting records.",
      "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."
      ],
      "updated": "2026-11-17",
      "sourceReviewed": "2026-11-17",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "driver-app",
      "url": "https://platform.getcentri.com/centripos/driver-app",
      "title": "Use the CentriPOS Driver workflow",
      "summary": "Open today’s local-delivery lane, contact the customer, navigate to each address, and update the fulfillment status from a focused mobile screen.",
      "collection": {
        "id": "customer-tools",
        "title": "Customer-facing tools"
      },
      "section": "Customer-facing tools",
      "introduction": "CentriPOS Driver has two access modes: a signed-in Centri Account at /driver, or a temporary route link protected by its separate six-character PIN. A temporary link does not create a POS account. Share its URL and PIN only with the assigned driver.",
      "beforeYouBegin": "Use only branded pos.getcentri.com links supplied by CentriPOS and confirm the link belongs to the intended merchant and transaction.",
      "steps": [
        "A manager, owner, or super admin prepares the route in Sales → Fulfillment Center. Select the delivery date, confirm the ordered stops, and choose Save Route if the order changed. The route contains local-delivery line items scheduled for that date.",
        "For a driver without a Centri Account, choose Driver link. CentriPOS creates a branded pos.getcentri.com driver URL and a six-digit PIN, copies both when browser clipboard access is available, and displays them in Temporary driver route access. The link expires after 36 hours; create a fresh link if the driver sees Route link unavailable.",
        "For signed-in access, the driver signs in to their authorized Centri Account and opens /driver. This mode loads the current day’s open local deliveries. The Center button returns the signed-in user to Sales → Fulfillment.",
        "When opening a temporary link, enter the six-character route PIN and choose Unlock route. The PIN unlocks only that dated route. Until it is verified, the route’s customer and stop details are not returned to the screen.",
        "Read the top summary: Stops is the number of route stops, Done is the number whose status is Delivered, and Location shows Live only while foreground location sharing is active. The badge identifies Temporary route access or Signed-in account.",
        "The first available stop opens as Next stop. Review the customer or receipt identifier, current status, delivery address, phone number, delivery method, and preferred time. Select another numbered stop in the list when you need to work out of sequence.",
        "Choose the address or Navigate to open driving directions in Google Maps. Navigate is unavailable when the sale has no saved delivery address. Choose the phone number to open the device’s supported phone action.",
        "Choose Loaded when the stop’s items are on the vehicle. Choose On the way when travel begins; in temporary-link mode this also starts foreground GPS sharing and sends device location events while the page remains open and the browser has permission. Signed-in mode shows foreground location status locally but does not send the public-link location events.",
        "Choose Delivered only after every item in that stop has actually been delivered. CentriPOS applies the selected status to all line items grouped into the stop, refreshes the route, and increases Done when the stop becomes completed. A completed stop cannot be changed again from this driver screen.",
        "Keep the driver page open while foreground location is expected. The browser may ask for precise location permission. Background or closed-page tracking is not represented by this screen; Foreground GPS is the stated operating boundary.",
        "If Today’s lane says No local deliveries scheduled for today, return to Fulfillment Center and verify the fulfillment type is Local delivery, its fulfillment date matches the route date, the receipt is not draft, voided, or parked-abandoned, and the items remain in an open fulfillment status.",
        "Use the Fulfillment Center for route optimization, stop reordering, signatures, DispatchTrack export, detailed item handling, and other manager workflows. The CentriPOS Driver screen itself does not currently capture arrival, exception reasons, notes, signatures, delivery photos, or other proof-of-delivery evidence."
      ],
      "controls": [
        {
          "name": "Driver link",
          "description": "Manager-created branded route URL for the selected delivery date."
        },
        {
          "name": "Route PIN",
          "description": "Separate six-character code required to unlock a temporary route; it is not a Centri Account password."
        },
        {
          "name": "36-hour expiry",
          "description": "Temporary route links become unavailable 36 hours after creation."
        },
        {
          "name": "Signed-in account",
          "description": "Authorized Centri Account route showing today’s open local deliveries."
        },
        {
          "name": "Temporary route access",
          "description": "PIN-protected dated route that does not create a POS account."
        },
        {
          "name": "Stops",
          "description": "Number of grouped customer destinations on the loaded route."
        },
        {
          "name": "Done",
          "description": "Stops whose grouped fulfillment status is completed and displayed as Delivered."
        },
        {
          "name": "Location Live / Off",
          "description": "Whether foreground location watching is currently active on the driver page."
        },
        {
          "name": "Foreground GPS",
          "description": "Location collection while the page is open and browser permission is granted; not a promise of background tracking."
        },
        {
          "name": "Next stop",
          "description": "Currently selected customer destination and its grouped items."
        },
        {
          "name": "Address",
          "description": "Saved delivery destination; opens Google Maps directions when present."
        },
        {
          "name": "Phone",
          "description": "Customer delivery phone number exposed after authorized route access."
        },
        {
          "name": "Navigate",
          "description": "Opens Google Maps driving directions for the saved address."
        },
        {
          "name": "Loaded",
          "description": "Sets every line item in the selected stop to loaded."
        },
        {
          "name": "On the way",
          "description": "Sets every line item in the stop to in progress and starts foreground location watching."
        },
        {
          "name": "Delivered",
          "description": "Sets every line item in the stop to completed; use only after the complete stop was delivered."
        },
        {
          "name": "Center",
          "description": "Signed-in-only control returning to the Fulfillment Center."
        },
        {
          "name": "No local deliveries scheduled for today",
          "description": "Completed empty state when no qualifying open local-delivery items match the route day."
        },
        {
          "name": "Fulfillment Center boundary",
          "description": "Route planning, signatures, DispatchTrack, detailed fulfillment work, and manager controls live outside the focused driver screen."
        }
      ],
      "expectedResult": "The authorized driver sees only the stops returned for the signed-in day or PIN-protected dated route, opens the intended address or phone action, and the selected Loaded, On the way, or Delivered status updates every fulfillment line item grouped into the correct stop. Foreground location appears only while the page is open and permitted.",
      "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."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "refresh-reset",
      "url": "https://platform.getcentri.com/centripos/refresh-reset",
      "title": "Refresh CentriPOS safely",
      "summary": "Choose the least disruptive recovery action, protect an active cart or payment, and understand exactly what CentriPOS Hard refresh removes from this browser.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "The navigation Refresh button and User Hub → Refresh data both run the same hard-refresh routine despite the softer User Hub description. It clears the local cart and Sell workspace state, personal theme and UI-scale overrides in this browser, all session storage, browser caches, and registered service workers before replacing the current URL with a cache-busting parameter. It does not intentionally delete completed sales, catalog records, customers, inventory, or other server records. Never use it during an active or uncertain payment.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Before any refresh, stop and classify the problem. If a payment was submitted, a terminal is processing, a confirmation is unclear, or the customer may already have been charged, do not reload or retry. Check the processor/payment evidence and receipt status first or escalate.",
        "Record the active business, location, register, user, route, exact error text, and current time. Capture a privacy-safe screenshot when useful. This context can disappear after a reload and is essential for support.",
        "Protect in-progress work. Complete or deliberately save the cart where supported, copy any unsaved notes or form values, and close dialogs that have an explicit Save/Cancel decision. A local autosave is not enough before Hard refresh because its cart/Sell keys are cleared.",
        "Use a screen-specific Refresh, Retry, or refetch control first when it clearly reloads only that view’s data. Wait for the request to finish once. Do not hammer Refresh or repeat a submit action while the first request may still be running.",
        "If the issue is a stale visual route and no transaction or unsaved work is at risk, perform one normal browser/app reload. Reopen the same route and verify the business, location, register, user, and register-session state before continuing.",
        "Use CentriPOS Hard refresh only when a normal reload did not recover the app or support directs it. On desktop, use Refresh at the bottom of the navigation rail or User Hub → Refresh data → Refresh. On mobile, open More and choose Refresh. All three call the same cleanup routine.",
        "Expect Hard refresh to remove the browser-local cart and Sell workspace state, the local app-theme and app-ui-scale values, all session-storage values, Cache Storage entries, and service-worker registrations. It then waits briefly and replaces the current route with an _app_refresh timestamp. Do not expect the previous draft cart or modal state to return.",
        "After the app reloads, confirm identity and operating context before touching records. Re-select the business, location, or register if prompted; confirm whether the register session is open; restore the intended personal appearance if the cleared local override mattered.",
        "Return to the failed screen and test the smallest safe read-only action first. Do not repeat a payment, refund, import, sync, message, order submission, or other write until you have checked whether the original request completed on the server or external provider.",
        "If the issue remains, stop cycling refreshes. Contact support with the captured context, what control you used, whether it was a page refetch, normal reload, or Hard refresh, and what changed afterward. Include identifiers that are safe and relevant, but never passwords, API keys, full card data, or OAuth tokens."
      ],
      "controls": [
        {
          "name": "Screen-specific Refresh / Retry",
          "description": "Reloads the current screen’s query or retries that view when implemented; it is normally the least disruptive option."
        },
        {
          "name": "Normal browser reload",
          "description": "Reloads the application route but does not intentionally run the CentriPOS cleanup routine."
        },
        {
          "name": "Navigation Refresh",
          "description": "Desktop rail action whose tooltip is Hard refresh app; it runs the full cleanup routine."
        },
        {
          "name": "User Hub → Refresh data",
          "description": "Runs the same Hard refresh app routine even though the card says Reload the latest records without leaving this page."
        },
        {
          "name": "Mobile More → Refresh",
          "description": "Mobile entry point to the same Hard refresh routine."
        },
        {
          "name": "Hard refresh cleanup",
          "description": "Removes app-theme, app-ui-scale, local cart state, Sell workspace state, every session-storage value, Cache Storage entries, and registered service workers in this browser."
        },
        {
          "name": "_app_refresh",
          "description": "Timestamp query parameter added when the routine replaces the current URL, helping bypass stale route assets."
        },
        {
          "name": "What is not intentionally deleted",
          "description": "Completed server-side sales, customers, catalog, inventory, and other tenant records are not the target of client-state cleanup. Verify uncertain writes before retrying."
        },
        {
          "name": "Active payment stop condition",
          "description": "Never refresh while terminal or processor outcome is pending or unclear; reconcile first to avoid duplicate charges or receipts."
        },
        {
          "name": "Context recheck",
          "description": "Confirm account, business, location, register, and session after any reload before resuming work."
        },
        {
          "name": "Escalation evidence",
          "description": "Screen/route, time, user, business/location/register, exact error, privacy-safe image, action already attempted, and whether external processing may have occurred."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no privacy-safe exact Hard refresh sequence, so this guide intentionally publishes without an unrelated image."
        }
      ],
      "expectedResult": "The same CentriPOS route reloads with the intended business context and current saved data while unsaved work is either preserved by the supported flow or deliberately discarded.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "sign-in-access",
      "url": "https://platform.getcentri.com/centripos/sign-in-access",
      "title": "Fix sign-in or missing-access problems",
      "summary": "Separate identity authentication from active business membership, selector context, downstream data scope, security policy, and individual role permissions before changing access.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "Do not share passwords, paste invitation/reset tokens into support, weaken MFA or switching policy as a shortcut, or assign Owner broadly. Also do not assume the location/register picker itself proves row-level authorization: the current selectors list active records for the chosen tenant, while downstream screens can apply separate user-location and restricted-register scopes.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Start at the branded /login screen and confirm the exact invited email. The current flow uses Email and Password only. If Login failed appears, distinguish a bad credential from Signed in as a different account, which means CentriPOS rejected an authenticated identity that did not match the email requested or an active matching profile.",
        "If the password is unknown, choose Forgot password?, submit the existing account email once, and use the newest branded recovery message. Password recovery changes an existing credential only; it cannot activate a profile, add a business membership, assign a role, or grant a location/register permission.",
        "After authentication, examine the business step. A user with one active profile enters that tenant directly. Multiple active profiles produce Choose your business. If the intended business is absent, an authorized administrator must verify that the invited identity is linked to an active profile in that tenant; searching cannot reveal an inactive or nonexistent membership.",
        "On Choose a location, No locations configured yet means the selector returned no active location rows for the active tenant. A missing location can therefore indicate an inactive/missing record or wrong business. The current selector itself does not filter its location query through user_locations, so seeing a location card is not proof that every downstream report or action will include that location.",
        "On Choose a register, only active registers belonging to the selected location are listed. Exactly one is auto-selected. The current selector itself does not exclude restricted registers through user_registers; downstream queries can separately exclude restricted registers for unassigned non-owner users. Treat selector visibility and operational authorization as different checks.",
        "Open User Hub to confirm the effective name, email, and role label, then confirm the active business/location/register separately in the operating-context bar because User Hub does not print the business name. Use Sign out / switch user for the wrong identity, Switch store for another membership, and Switch for another location/register.",
        "For missing navigation or a disabled action, compare the effective user’s roles and explicit permissions inside the active tenant. Admin requires Owner, Super Admin, or settings.manage (Manage settings). Other screen and action permissions are independent; granting Admin access does not automatically grant every receipt, sale, contact export, financial, or register action.",
        "For scoped data discrepancies, compare the page’s query rules with user_locations and restricted register assignments. The shared location-scope hook gives Owners/Super Admins all locations; for other users, assigned location IDs are used when present. With no assignments, many callers treat the user as unrestricted unless that screen requests strict assignment. Restricted registers are excluded downstream only when marked restricted and the user lacks a user_registers assignment.",
        "Review Admin → Security only with an authorized Owner, Super Admin, or Manage settings role. Defaults include Log in access, switching policy, authentication method, and inactivity re-authentication. Role-specific login and authentication overrides supersede defaults; the system Owner role always reports Has access to log in. Changes save immediately to the security settings stored on a tenant location record.",
        "If a role is set to Only has access to log in through user switching, do not treat failed direct login as a forgotten-password problem. If Password + MFA or inactivity re-authentication is configured, follow that policy rather than disabling it to test. Retain an authorized owner recovery session before changing security settings.",
        "If the correct identity, active membership, context, role, and page-specific scope are all verified but the screen still fails, capture the safe page name, timestamp with time zone, business/location/register names, exact message, device/browser, and smallest repeatable steps. Never include a password, OTP, invitation token, reset URL, session token, API credential, or customer/payment screenshot."
      ],
      "controls": [
        {
          "name": "Authentication",
          "description": "Email-and-password proof of identity on the branded CentriPOS login screen."
        },
        {
          "name": "Signed in as a different account",
          "description": "Protective sign-out when the authenticated identity differs from the requested account and no active matching profile exists."
        },
        {
          "name": "Active profile",
          "description": "Tenant-specific CentriPOS membership row connecting one authenticated user to one business."
        },
        {
          "name": "Single active profile",
          "description": "Enters that business directly without showing the business picker."
        },
        {
          "name": "Choose your business",
          "description": "Multiple-membership selector containing the account’s active tenant options."
        },
        {
          "name": "Choose a location",
          "description": "Active tenant-location selector; card visibility is not proof of every downstream location scope."
        },
        {
          "name": "No locations configured yet",
          "description": "No active tenant locations were returned to the selector."
        },
        {
          "name": "Choose a register",
          "description": "Active registers for the selected location; one active register is auto-selected."
        },
        {
          "name": "Restricted register",
          "description": "Register marked is_restricted; downstream scope can exclude it when the effective user lacks a user_registers assignment."
        },
        {
          "name": "user_locations",
          "description": "Assignments used by scoped page queries for non-owner users, not by the current location selector itself."
        },
        {
          "name": "No location assignments",
          "description": "Many shared-scope callers interpret this as all locations unless they explicitly request strictAssigned behavior."
        },
        {
          "name": "Effective user",
          "description": "Proxy identity when supported proxy mode is active; otherwise the signed-in account identity."
        },
        {
          "name": "Operating-context bar",
          "description": "Separate confirmation of the active business, location, register, and session state."
        },
        {
          "name": "Storefront role",
          "description": "Baseline tenant role used in navigation and permission evaluation."
        },
        {
          "name": "Explicit permission",
          "description": "Named capability such as settings.manage or a page/action-specific sale, receipt, contact, financial, or register permission."
        },
        {
          "name": "Admin access required",
          "description": "Admin is limited to Owner, Super Admin, or a custom role with Manage settings."
        },
        {
          "name": "Security defaults",
          "description": "Login access, switching policy, authentication method, and inactivity re-authentication applied unless a role override exists."
        },
        {
          "name": "Role override",
          "description": "Per-role login-access or authentication-method choice that supersedes the default."
        },
        {
          "name": "User switching only",
          "description": "Role can enter only through the configured in-app switching flow, not normal direct login."
        },
        {
          "name": "Password + MFA",
          "description": "Configured authentication method requiring the business’s supported second-factor flow."
        },
        {
          "name": "Support evidence",
          "description": "Safe screen/context/time/error/device details only; never secrets or private customer/payment data."
        },
        {
          "name": "No public screenshot",
          "description": "Security and user-access screens are sensitive, and the approved Harbor & Hearth manifest explicitly rejected them; this article intentionally has no fabricated replacement."
        }
      ],
      "expectedResult": "The user signs in with the invited identity and sees exactly the businesses, locations, registers, and navigation allowed by the current role.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "printer-labels",
      "url": "https://platform.getcentri.com/centripos/printer-labels",
      "title": "Fix receipt or label printing",
      "summary": "Identify whether the failure belongs to CentriPOS record data, template selection, native or browser print handoff, system printer configuration, physical media, or barcode content—and prove the correction with one controlled receipt or label before continuing a batch.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "CentriPOS builds the receipt or label HTML and initiates printing, but the browser/native shell, operating system, driver, printer, and loaded media control the final physical output. Repeated Print actions can create duplicate paper, label override barcodes, or customer documents without fixing the original layer. Stop after one failed attempt, identify the boundary, and test with safe data.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Reopen the exact source record. For a receipt, verify sale/receipt number, customer-safe identity, location/register, line items, quantities, totals, payment state, fulfillment, policies, and signature evidence. For a product label, verify saved product, selected variant/SKU, barcode, prices, warranty, and store branding. For a sold-item label, verify the receipt and exclude returned lines.",
        "Confirm the printer itself before changing CentriPOS: it is powered on, online, not paused, has the intended roll/sheet/labels loaded in the correct orientation, has no jam, and is selected on the device. A successful printer self-test with wrong CentriPOS output points back to template/media settings; a failed self-test is outside the app.",
        "For receipts, open Print receipt and wait for Loading receipt templates and storefront print settings to finish. If Could not load receipt templates appears, record that exact message and retry the context load after confirming network access. If No receipt templates were found for this storefront yet appears, an administrator must create/activate the required template before printing.",
        "Choose Print style. Sales receipt uses the selected standard template. Gift receipt hides prices. Delivery sheet produces a fuller fulfillment-oriented page and does not offer the thermal/letter selector in this dialog. Confirm that the chosen document is appropriate before exposing it to a customer or fulfillment team.",
        "For Sales receipt or Gift receipt, choose Paper size: Template default, Thermal receipt, or 8.5 x 11 paper. Template default follows the selected template’s thermal versus a4_letter style. Selecting another option changes the generated page style but cannot change the physical roll or driver paper configured in the system dialog.",
        "Choose Store policies: Storefront uses the tenant/storefront terms, Register uses the policy assigned to the original printing register, and None omits policy content. Verify the original register when historical receipts are printed from another workstation; the currently selected register is not automatically the policy source.",
        "For a Sales receipt, search templates by template name, type, or assigned register. Read each template’s description and assignment count. Assigned register template identifies the template configured for the original register. Template selection is disabled for Gift receipt and Delivery sheet; those styles should not be described as using an arbitrary standard-template choice.",
        "Read the signature note. When the sale required a signature, the output includes the saved signature when one exists or a blank signature line when it was required but not captured digitally. Confirm the signer belongs to this receipt; do not print another customer’s signature while troubleshooting.",
        "Choose Print receipt once. In the native iOS shell, CentriPOS can hand HTML to the native print bridge. In a normal browser it prints from a generated frame and may expose print controls if automatic handoff cannot proceed. If the app reports Could not open the print window, allow the pos.getcentri.com print/popup action and retry once after confirming no hidden print dialog is already open.",
        "On an iPad/iPhone user agent, Star PassPRNT is a separate button. It hands encoded receipt HTML to the starpassprnt URL scheme and requires the compatible PassPRNT app/printer workflow. If it does not open, confirm PassPRNT is installed/configured; the normal Print receipt route remains a different system/native destination.",
        "In the operating-system print dialog, choose the exact physical printer and paper/label size. Start with 100% or Actual size, default orientation, and no extra headers/footers when the tested template does not call for them. Browser Fit to page, unexpected margins, driver scaling, or Letter selected for a thermal roll can clip, shrink, rotate, or paginate otherwise correct HTML.",
        "For a product price label, first save the product. Open its Labeling/Shipping print panel, choose the saved label template or Built-in price label when no tenant templates exist, then choose Product label, All SKUs, or one exact variant SKU. Enter the number of copies; blank or invalid quantity normalizes to one.",
        "Treat One-off sale price, Compare at, and Print callout as print-time overrides. When any override is used, CentriPOS creates a unique label-scan override barcode for each printed copy before opening the print surface. If barcode creation fails, no label window opens. Do not repeatedly click Print because that can create additional override records with different codes.",
        "Check product-label data before printing: product/brand, custom fields, variant attributes, SKU, barcode/product code, regular/sale/compare-at price, callout, supplier code, warranty or AS IS state, store name/logo, and the template’s exact width, height, orientation, margins, and element bindings. A missing source value is a data/template issue, not a printer-driver issue.",
        "For Print sale labels from a receipt, select only non-return receipt lines that need tags, set each label quantity, and add optional print-time remarks. The built-in sold-label output includes customer, receipt, item, amount due, fulfillment/current date, SKU/barcode, notes, and a label counter based only on selected printed labels. No selected lines produces Select at least one receipt item to print.",
        "Choose Print once. Product and sale labels use the native iOS print bridge when available; otherwise CentriPOS writes a hidden print frame at the template’s physical inch dimensions, waits for fonts/images/barcodes to be ready, focuses it, and calls the system print dialog. A false start reports Could not open the print window; it does not prove the printer received a job.",
        "Print one receipt or one label as the calibration test. Inspect merchant/customer privacy, correct record, page count, clipping, rotation, margins, font fit, logo/images, price visibility, policies, signature block, notes, and counter. For a label, scan the printed code back into the intended safe product workflow and verify it resolves to the correct product/variant and override price/callout.",
        "If the job reaches the queue but nothing prints, inspect system queue status, printer connection, driver, media sensor/calibration, and device permissions. If the wrong printer receives it, change Destination in the system dialog rather than editing CentriPOS templates. If the queue never receives a job, inspect the native/browser handoff and console-safe error—not the printer mechanics.",
        "If layout is wrong on every printer, verify the CentriPOS template style/dimensions, selected paper override, and source content. If only one printer is wrong, verify that device’s driver paper, scaling, margins, orientation, density, and calibration. If only one record is wrong, compare its sale/product data, signature, policies, images, barcode, and variant fields.",
        "Continue a batch only after the single test is correct. Record the working CentriPOS template/style/policy, device and OS/browser, destination printer, driver paper size, scale, margins, orientation, and physical media. When contacting support, provide those settings and a redacted output photo—never full customer details, signatures, payment credentials, or reusable public links."
      ],
      "controls": [
        {
          "name": "Source record",
          "description": "Receipt, product/variant, or sale-line data used to construct the printable document."
        },
        {
          "name": "Loading receipt templates and storefront print settings",
          "description": "Context query is still resolving; wait before choosing a template."
        },
        {
          "name": "No receipt templates were found",
          "description": "Completed empty state requiring template configuration, not repeated printing."
        },
        {
          "name": "Print style",
          "description": "Sales receipt, price-hiding Gift receipt, or Delivery sheet."
        },
        {
          "name": "Paper size",
          "description": "Template default, Thermal receipt, or 8.5 x 11 for non-delivery receipt styles."
        },
        {
          "name": "Template default",
          "description": "Uses the selected template’s thermal or a4_letter default."
        },
        {
          "name": "Storefront / Register / None policies",
          "description": "Storewide terms, original-register terms, or omitted policy content."
        },
        {
          "name": "Receipt template search",
          "description": "Search by template name, type, or assigned register for the standard receipt style."
        },
        {
          "name": "Assigned register template",
          "description": "Template ID configured on the original receipt register."
        },
        {
          "name": "Signature output",
          "description": "Saved signature when present or blank line when required but not digitally captured."
        },
        {
          "name": "Print receipt",
          "description": "Native iOS bridge or generated browser-frame print initiation; not proof of physical output."
        },
        {
          "name": "Star PassPRNT",
          "description": "iOS-only separate starpassprnt scheme handoff requiring a compatible installed workflow."
        },
        {
          "name": "System Destination",
          "description": "Physical or virtual printer chosen outside CentriPOS."
        },
        {
          "name": "Driver paper size",
          "description": "System/driver media definition that must match the generated template and loaded stock."
        },
        {
          "name": "Scale / margins / orientation / headers",
          "description": "System settings that can distort or add content to a correct template."
        },
        {
          "name": "Built-in price label",
          "description": "Fallback product label when no saved tenant label template exists."
        },
        {
          "name": "Product label / All SKUs / SKU",
          "description": "Product-label target selection."
        },
        {
          "name": "Label quantity",
          "description": "Copies per selected product/SKU; blank or invalid becomes one."
        },
        {
          "name": "One-off sale price / Compare at / Print callout",
          "description": "Print-time label overrides that cause unique scan-override barcodes to be created per copy."
        },
        {
          "name": "Label template dimensions",
          "description": "Physical width/height, orientation, margin, background, and bound elements used by the hidden print frame."
        },
        {
          "name": "Print sale labels",
          "description": "Receipt-level sold-tag workflow that excludes returned lines and requires explicit line selection."
        },
        {
          "name": "Selected label counter",
          "description": "Counts only copies of selected receipt lines."
        },
        {
          "name": "Hidden label print frame",
          "description": "Browser print surface sized in physical inches and delayed until fonts/images/barcodes are ready."
        },
        {
          "name": "Native iOS print bridge",
          "description": "Company shell callback used for receipt/label HTML when available."
        },
        {
          "name": "Print queue",
          "description": "Operating-system evidence that the handoff reached a printer destination."
        },
        {
          "name": "Calibration test",
          "description": "One controlled output used to prove content, scan behavior, and physical layout before a batch."
        },
        {
          "name": "No substituted screenshot",
          "description": "The approved Harbor & Hearth capture is the Receipt Templates admin screen, not a receipt print dialog or label workflow, so this troubleshooting guide intentionally uses no mismatched image."
        }
      ],
      "expectedResult": "The selected printer produces one readable receipt or label at the intended size using the correct template and current record data.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "scanner",
      "url": "https://platform.getcentri.com/centripos/scanner",
      "title": "Use and troubleshoot barcode scanning",
      "summary": "Choose the correct scanner path for selling, catalog setup, or purchase-order receiving, then isolate camera, keyboard-wedge, catalog-code, duplicate-match, availability, and case-pack problems.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "CentriPOS has multiple scanner behaviors. The general camera dialog captures one code and closes; purchase-order receiving scans continuously; a USB/Bluetooth scanner types into the focused field; a remote customer-display scan adds only one unambiguous sellable match.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "First identify the workflow. In Sell, the barcode button beside Search products or scan barcode… opens the one-code camera dialog. In a product or variant form, the camera captures a code into that field. In Receive Stock, Scan Barcode opens continuous receiving mode.",
        "For camera scanning, allow camera access and point the rear/environment camera at the full code inside the scan box. The general dialog closes after a successful decode. If it cannot read the label, type the printed MFC, UPC, or barcode and choose Capture code or press Enter.",
        "In Sell, a normal captured code becomes the search value; review and choose the intended result. A USB/Bluetooth scanner behaves as typed input, so keep the Sell search or intended Barcode field focused. Do not assume the scanner’s Enter suffix completes or adds a normal search result.",
        "A printed label-override code has the form LBL- plus eight letters/numbers. In Sell, an active, unexpired override can add its exact product/variant automatically with the saved unit-price override and callout note. If the product is unavailable at the current register, CentriPOS refuses it.",
        "A remote customer-display scan adds directly only when exactly one exact barcode match resolves among products allowed at the current location/register. Checkout activity or a live sale lock pauses remote scanning; no match or multiple matches returns Needs review and tells the register user to resolve it with search.",
        "For Receive Stock, choose Scan Barcode and scan product or case-pack barcodes continuously. A product/variant barcode adds one unit; a packaging barcode adds its configured units-per-pack, capped at the remaining PO quantity. The same code is ignored for two seconds to prevent camera duplicate reads. Choose Done Scanning when finished.",
        "If receiving says No matching product for barcode, confirm the code belongs to a remaining PO line or a packaging-unit barcode mapped to that same product and variant. Receiving’s camera dialog has no manual-code input, so enter the quantity directly when the camera cannot decode.",
        "For a catalog field, scan or manually capture the code, then save the product/variant form. Product-level matching uses the product barcode and active product codes without a variant; variant matching uses the variant barcode and active codes assigned to that variant.",
        "When characters do not appear from a USB/Bluetooth scanner, test in a plain text field, then check power, pairing/cable, keyboard mode, focus, and scanner suffix. When the camera preview does not start, recheck browser camera permission, secure-site access, and whether another app owns the camera; the current dialogs log camera-start errors but do not show a detailed on-screen error.",
        "When a code finds no result, compare the exact trimmed code without assuming SKU is a barcode alias. Check product Barcode, variant Barcode, and active additional product-code rows. Search can find broader product identifiers, but exact automatic matching uses barcode aliases.",
        "When a remote scan reports no single matching product or a normal search shows several candidates, look for duplicate product- and variant-level barcode aliases. Correct the catalog data rather than choosing an arbitrary item. Retest at the same location and register because sellable availability is part of exact remote resolution."
      ],
      "controls": [
        {
          "name": "General camera dialog",
          "description": "Uses the environment-facing camera at 10 fps, captures one decoded value, calls the screen’s scan action, and closes."
        },
        {
          "name": "Capture code",
          "description": "Manual fallback for the general camera dialog; trims the entered value and submits it."
        },
        {
          "name": "Keyboard-wedge scanner",
          "description": "USB/Bluetooth scanner that types characters into whichever field currently has focus."
        },
        {
          "name": "Normal Sell scan",
          "description": "Populates Sell search; the cashier reviews and selects the intended product unless a specialized override path applies."
        },
        {
          "name": "Exact barcode alias",
          "description": "Case-insensitive trimmed product barcode, active product code, variant barcode, or active variant-assigned product code."
        },
        {
          "name": "Product-level code",
          "description": "Product barcode or active additional code with no variant_id."
        },
        {
          "name": "Variant-level code",
          "description": "Variant barcode or active additional code assigned to that exact variant."
        },
        {
          "name": "LBL override",
          "description": "Active label_scan_overrides record matching LBL-[A-Z0-9]{8}; it can carry product, variant, price override, and callout note."
        },
        {
          "name": "Remote scan",
          "description": "Customer-display broadcast that adds only one unique exact match among products sellable at the active location/register."
        },
        {
          "name": "Continuous receive scanner",
          "description": "Stays open for repeated PO scans and suppresses the same decoded text for two seconds."
        },
        {
          "name": "Packaging barcode",
          "description": "Receiving-only mapped code whose scan increments the PO line by units-per-pack rather than one."
        },
        {
          "name": "Remaining cap",
          "description": "Receiving never increments a line above its still-receivable quantity."
        },
        {
          "name": "No visible camera error",
          "description": "Camera-start failures currently go to the browser console; use permissions/device checks or manual input where offered."
        },
        {
          "name": "Duplicate match",
          "description": "More than one exact alias resolves the same scanned code; automatic remote add returns no match and requires catalog correction."
        }
      ],
      "expectedResult": "A controlled barcode scan enters the complete code once and resolves to the correct CentriPOS product or configured override without adding an unrelated item.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "terminal",
      "url": "https://platform.getcentri.com/centripos/terminal",
      "title": "Fix a payment terminal problem",
      "summary": "Identify the active terminal and request, distinguish a confirmed decline from an unknown final state, safely clear an abandoned prompt, and reconcile any manual or late processor result without duplicating a charge.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "Never retry, clear, manually record, void, or refund an uncertain terminal payment until the physical terminal, CentriPOS payment intent/transaction status, processor activity, and receipt all agree on what happened. A POS timeout is not proof that the card was not approved. Manual completion records payment while processor details are still pending and must be used only after the cashier sees a genuine approved result on the terminal.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Keep the Pay screen, cart, and physical terminal visible. Confirm business, location, register, open session, amount, sale/refund mode, selected payment type, and terminal name. If No terminals paired appears, stop and have an administrator assign/pair the terminal under Admin → Locations; do not record a terminal payment as an unrelated manual type.",
        "When more than one terminal is available, choose the intended device from the terminal picker. The default label identifies the resolved terminal. Verify the physical device name/identifier before choosing Send to [terminal] or Send refund to [terminal].",
        "After sending, read both screens. CentriPOS progresses through Sending to terminal and Waiting for customer card; the terminal should show the amount and accept dip, tap, swipe, or keyed entry on the device. If the terminal screen is asleep, wake it rather than sending another request.",
        "CentriPOS creates a payment intent before sending and stores a separate terminal transaction ID after acknowledgement. Keep the displayed Terminal transaction reference and any response code. Polling checks status roughly every second and realtime updates can also finalize the same request; duplicate finalization is suppressed by intent/transaction/result keys.",
        "If the result is Approved, CentriPOS captures the intent, adds one CentriPay Cloud payment with processor or terminal reference, and closes the receipt when the balance reaches zero. If the payment is approved but receipt closing fails, the screen explicitly says to review and tap Pay to retry closing the receipt; do not send another card charge.",
        "If Declined or Failed appears, read the formatted response message and response code. CentriPOS marks the intent declined/failed and does not add the payment. Resolve card/customer/processor conditions before a new request. A confirmed decline is different from a timeout or lost response.",
        "If Terminal did not acknowledge the request or the send fails before a transaction ID exists, inspect the terminal for an old prompt and verify connectivity/assignment. Do not assume nothing happened if the device still shows a payment. Clear the blocking intent only after confirming the old request should be canceled.",
        "If the request remains waiting, allow polling to continue. The manual-completion control is intentionally delayed for 10 seconds. Do not use it merely because the customer is impatient; first wait for an approved/declined final status and check the terminal display.",
        "At the terminal timeout boundary, CentriPOS performs one final processor status lookup before marking the request Expired. When that lookup cannot prove approval or failure, the status remains operationally uncertain. Search Payanywhere/CentriPay transaction activity using amount, time, terminal, and terminal transaction/payment-intent reference before retrying.",
        "Choose Complete manually only when the physical terminal clearly shows the exact payment was approved but CentriPOS is still waiting. The control checks status again first; if approval is now available it completes normally. Otherwise it records manual_pending_processor_confirmation, closes the receipt as paid, and expects processor details to update receipt history later.",
        "After manual completion, verify the receipt contains a single CentriPay Cloud payment for the intended amount, preserves the terminal transaction/payment-intent reference, and later receives processor transaction, approval, card last four/brand, batch, and response details. Escalate if reconciliation does not arrive; never create a second payment to make the metadata appear.",
        "Use Stop waiting and send again only when CentriPOS can cancel the active payment intent and you have confirmed the old terminal prompt/result is not an approval. On success, dismiss the old prompt on the physical PAX before sending the new sale. If Failed to stop waiting appears, do not retry until the blocking request is investigated.",
        "Use Clear terminal request in CentriPOS for a known stale/blocking request. It cancels the stored intent and resets local state; it does not remotely guarantee an old prompt disappeared or reverse a processor approval. Dismiss the physical prompt and confirm transaction history before sending again.",
        "If the cart is cleared while a request is active, CentriPOS attempts to cancel that payment intent. Still inspect the terminal and processor history because clearing the cart is not a payment reversal. Likewise, closing the Pay screen or losing network does not prove a request failed.",
        "For a refund terminal problem, keep the original receipt, return/refund amount, original-card eligibility, new-card terminal choice, processor reference, and sign of the payment aligned. Do not run a sale to compensate for a failed refund or a refund to test terminal connectivity.",
        "For support, preserve amount, local timestamp/time zone, business/location/register, session, terminal name/masked ID, sale or safe receipt reference, payment intent and terminal transaction references, response code/message, what each screen showed, and whether manual completion/clear/stop was used. Never send full PAN, bank data, credentials, API keys, or an unredacted payment screen."
      ],
      "controls": [
        {
          "name": "Terminal picker",
          "description": "Chooses among available devices; the resolved device can be labeled default."
        },
        {
          "name": "No terminals paired",
          "description": "No usable terminal is assigned/resolved for the current context; configure it in Admin → Locations."
        },
        {
          "name": "Send to terminal",
          "description": "Creates a CentriPay Cloud payment intent and sends it to the selected device for the capped remaining amount."
        },
        {
          "name": "Send refund to terminal",
          "description": "Creates the corresponding negative/refund request for a new card in refund mode."
        },
        {
          "name": "Sending to terminal",
          "description": "Payment intent is being created or delivered; do not submit again."
        },
        {
          "name": "Waiting for customer card",
          "description": "Terminal acknowledged the request and CentriPOS is polling for customer/processor completion."
        },
        {
          "name": "Terminal transaction",
          "description": "Reference returned by the device send and used for polling, realtime status, support, and reconciliation."
        },
        {
          "name": "Payment intent",
          "description": "CentriPOS request record tracking provider, amount, terminal, state, and eventual capture/cancel/failure."
        },
        {
          "name": "Response code",
          "description": "Processor/terminal result code shown with approved, declined, or failed status when available."
        },
        {
          "name": "Approved",
          "description": "Confirmed approval; one payment is added and the receipt closes when fully allocated."
        },
        {
          "name": "Approved but receipt did not finish closing",
          "description": "Card payment already exists; retry receipt closure with Pay, not another terminal charge."
        },
        {
          "name": "Declined",
          "description": "Confirmed processor decline; no payment is added."
        },
        {
          "name": "Failed",
          "description": "Confirmed or request-level failure; read message/code and verify the terminal before resending."
        },
        {
          "name": "Expired / timed out",
          "description": "POS stopped waiting after a final lookup; may still require processor reconciliation before any retry."
        },
        {
          "name": "10-second manual delay",
          "description": "Safety window before Complete manually is enabled."
        },
        {
          "name": "Complete manually",
          "description": "Checks processor status again, then records an observed terminal approval as pending processor confirmation only when still unresolved."
        },
        {
          "name": "manual_pending_processor_confirmation",
          "description": "Receipt is recorded paid while detailed processor confirmation is expected later."
        },
        {
          "name": "Stop waiting and send again",
          "description": "Cancels the active intent before resetting POS state; dismiss the old physical prompt and verify no approval first."
        },
        {
          "name": "Clear terminal request",
          "description": "Cancels a known blocking intent and resets POS state; does not reverse a processor transaction or guarantee the device prompt cleared."
        },
        {
          "name": "Cart clear cancellation",
          "description": "Best-effort intent cancellation when the cart resets; not proof of reversal or non-approval."
        },
        {
          "name": "Polling and realtime",
          "description": "Parallel status sources that can finalize the same intent; the UI deduplicates repeated final results."
        },
        {
          "name": "Duplicate-charge risk",
          "description": "A second request can charge again when the first outcome is unresolved."
        },
        {
          "name": "Safe reconciliation evidence",
          "description": "Amount, time zone, context, terminal, receipt, intent/transaction references, status and response code—never full card/bank data or credentials."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Harbor & Hearth manifest contains no safe final-state payment-terminal error capture, so this guide uses no fabricated image."
        }
      ],
      "expectedResult": "The terminal and CentriPOS agree on connection and transaction state, the device is assigned to the intended register, and a controlled payment reaches that device once.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "customer-display-troubleshoot",
      "url": "https://platform.getcentri.com/centripos/customer-display-troubleshoot",
      "title": "Fix a customer display connection",
      "summary": "Diagnose an unavailable control, expired PIN, approval wait, stale device, wrong register, missing cart, or lost live update without clearing healthy displays unnecessarily.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "Start with the status shown by the POS and use the least disruptive recovery. Refresh does not erase links; New PIN replaces a pairing attempt; Clear all removes every display link for the current register. Never approve an unknown device or expose customer details in screenshots sent to support.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Confirm both devices are using https://pos.getcentri.com and can load it over the network. On the POS, verify the business, location, and register in the context bar. On the display, verify the store and register names shown after connection. A display connected to the wrong register should be disconnected and paired again from the correct register.",
        "If the monitor control is disabled or says Customer display unavailable, open the register session. Pairing codes and display status are resolved against an active session; closing or switching registers changes the operating context.",
        "If the POS says Customer display not connected, choose Installed or Temp and use the current four-digit PIN or QR on the display. The PIN lasts 10 minutes. PIN not found or expired means return to the POS, choose New PIN, and enter only the newest code.",
        "If the display says Waiting for Approval, return to the POS. Confirm the displayed nickname and device ID suffix, then choose Confirm Install or Confirm Join. Check Again on the display only rechecks; it does not replace the required POS approval. Cancel abandons that display-side attempt.",
        "If an installed screen says Customer Display Ready and is waiting for the linked checkout host, confirm the intended POS device has opened the intended register. Retry reloads the display. Use Reset Link only when the installed trust is wrong or damaged, because the device must be paired and approved again afterward.",
        "Open Display Management on the POS. Live means the device checked in recently; Stale means it has not checked in within the current 75-second health window. Read Last seen and distinguish a momentary delay from a device that stopped responding.",
        "For Customer display not responding or Temporary display lost connection, keep the display page open, wake the device, confirm it remains online, and reload the branded /customer-display page. Choose Refresh on the POS to recheck. If the temporary pairing cannot restore, use Disconnect or Reset Pairing on the display, create a New PIN on the POS, and approve the new join.",
        "If the display is connected but says Waiting for your associate to start a sale, begin a new sale on the linked register and add one harmless test item. That waiting screen is correct when there is no active cart or no line items.",
        "If the display shows a cart but stops changing, confirm the header’s activity label is Live rather than an older Last updated state. Make one safe cart change, wait for the live broadcast or the visible-page fallback refresh, and choose Refresh on the POS. Do not repeat or alter a payment to test display synchronization.",
        "If the display shows the wrong cart, stop customer use immediately. Confirm the register context, disconnect the temporary display or reset the incorrect installed link, then pair from the correct register. Do not use Clear all on a different register in an attempt to fix it.",
        "Use Clear all on the POS only after Refresh, reload, and a fresh PIN have failed or when the register’s device trust is known to be wrong. Clear all resets every installed link and disconnects all pending or connected temporary pairings for that register, so every intended display must reconnect.",
        "If the POS reports Unable to reach customer display service or Customer display status unavailable while both devices have working network access, collect the exact status title and message, business, location, register, display mode, device nickname, masked device ID suffix, Last seen value, browser/device type, and time of failure. Do not include the PIN, customer information, full receipt, credentials, or internal service URLs. Send those details through the support path on this help center."
      ],
      "controls": [
        {
          "name": "Customer display unavailable",
          "description": "The register has no open session, so a connect code cannot be created or managed."
        },
        {
          "name": "Customer display not connected",
          "description": "Open register with no approved display link."
        },
        {
          "name": "PIN not found or expired",
          "description": "The four-digit code is invalid, replaced, or older than its 10-minute lifetime."
        },
        {
          "name": "Waiting for Approval",
          "description": "Valid device request pending explicit approval on the POS."
        },
        {
          "name": "Customer Display Ready",
          "description": "Installed display is trusted but waiting for its linked POS host and open register."
        },
        {
          "name": "Connected — live updates",
          "description": "Display is paired and listening for the register’s live sale."
        },
        {
          "name": "Waiting for your associate to start a sale",
          "description": "Healthy connection with no active cart items to show."
        },
        {
          "name": "Live",
          "description": "Display or active sale is checking in within its supported freshness window."
        },
        {
          "name": "Stale",
          "description": "Display has not checked in within 75 seconds."
        },
        {
          "name": "Last seen",
          "description": "Time since the latest display check-in."
        },
        {
          "name": "Customer display not responding",
          "description": "Installed link exists but its display stopped checking in."
        },
        {
          "name": "Temporary display lost connection",
          "description": "Temporary pairing exists but its browser stopped checking in."
        },
        {
          "name": "Retry / Check Again",
          "description": "Reloads or polls the current display state; does not approve a device or create a new PIN."
        },
        {
          "name": "Refresh",
          "description": "POS-side status recheck that preserves links."
        },
        {
          "name": "New PIN",
          "description": "Creates a fresh 10-minute connection code and replaces the applicable pending pairing."
        },
        {
          "name": "Reset Pairing / Disconnect",
          "description": "Clears the temporary display’s local pairing and, when possible, disconnects its active temporary pairing."
        },
        {
          "name": "Reset Link",
          "description": "Removes installed trust from that display device."
        },
        {
          "name": "Clear all",
          "description": "Destructive register-level recovery that resets all installed links and disconnects all temporary or pending pairings."
        },
        {
          "name": "Safe support details",
          "description": "Status message, operating context, device nickname and masked ID, last-seen age, browser/device type, and timestamp—never PINs, credentials, customer data, or internal URLs."
        }
      ],
      "expectedResult": "The intended display reports Live for the correct open register, shows the expected waiting or current-cart state, and receives a controlled cart update without resetting a healthy device on another register or exposing customer information.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "support-checklist",
      "url": "https://platform.getcentri.com/centripos/support-checklist",
      "title": "Contact CentriPOS support with useful details",
      "summary": "Send one safe, reproducible support request through CentriAI, the support site, email, or phone with enough operating context to investigate without exposing credentials or customer/payment data.",
      "collection": {
        "id": "troubleshooting",
        "title": "Troubleshooting"
      },
      "section": "Troubleshooting",
      "introduction": "Never send passwords, one-time codes, invitation or reset links, session tokens, API keys, processor credentials, full card/bank data, database credentials, or an unredacted customer/payment screen. Support does not need those secrets to identify the account or reproduce a customer-visible workflow.",
      "beforeYouBegin": "Record the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.",
      "steps": [
        "Start with the exact CentriPOS page and action. Write one sentence for what you expected and one for what actually happened, preserving the exact on-screen error text when it is safe. Distinguish a visible error from a loading state, missing control, incorrect result, or uncertain external transaction.",
        "Record the operating context before switching or refreshing: business name, location, register, open/closed register-session state, effective user role, device/browser or installed app, and the timestamp with time zone. Do not send internal tenant IDs unless support explicitly requests one through a secure channel.",
        "List the smallest repeatable steps from a known starting point. Include the exact control labels and whether the problem occurs every time, only for one record, one register/location, one role, one device, or one payment/integration provider. Mention any safe workaround already tested.",
        "Describe business impact and urgency factually: one user inconvenienced, a workflow blocked, multiple locations affected, customer waiting, register unable to sell, reporting discrepancy, or possible duplicate/uncertain payment. Choose Urgent only when immediate operational or financial risk genuinely requires it.",
        "Use a safe reference when it materially narrows the record: receipt/order/invoice number, customer code without unnecessary contact details, product SKU, purchase-order number, support ticket number, masked processor reference, or QBO document number. Never attach a full card number, bank account, password, token, or credential-bearing URL.",
        "Capture a screenshot only when it adds evidence. Crop to the CentriPOS page, include the relevant control/message and safe context label, and redact customer names, email, phone, street address, messages, signatures, balances, card details, credentials, QR/PIN codes, and unrelated browser tabs. Do not recreate or fabricate the screen when a safe capture is impossible.",
        "For CentriAI, choose the Sparkles Centri AI control → Support. Enter at least three useful characters, choose Normal, High, or Urgent, and choose Open support ticket once. CentriPOS includes the page/account context, current thread when present, plan, and effective email; record the returned ticket number/status and review Related knowledge.",
        "From this help center, open /support to email support@getcentri.com, call (614) 769-7619, or return to this checklist. An article’s Contact support link pre-fills the guide title in the email subject; still add the actual business/location/register and observed behavior.",
        "If emailing, use one descriptive subject such as CentriPOS support — [page] — [short symptom]. Put the context, expected/actual behavior, repeatable steps, impact, and safe references in the body. Send one clean request rather than separate fragments, and reply on the same thread with new evidence.",
        "For phone support, have the same context and safe reference ready. Never read a password, full card/bank number, OTP, API secret, or invitation/reset token aloud. If investigation must continue after the call, ask for or provide the ticket/thread reference so evidence stays together.",
        "For an uncertain payment, terminal timeout, duplicate-charge risk, register closure, deposit, QBO sync, or financial discrepancy, do not retry, void, refund, relink, close, or repair merely to create evidence. Preserve the current state and include amount, time, register, masked processor/QBO reference, and visible status so support can trace the full path safely.",
        "After submitting, keep the ticket/email reference and avoid changing the affected record unless normal business safety requires it. Add new timestamps, safe screenshots, or reproduction results to the same request. When resolved, verify the original workflow in the same business/location/register and confirm any financial or customer-facing result independently."
      ],
      "controls": [
        {
          "name": "CentriAI Support",
          "description": "In-product contextual ticket path that includes current page/account context and routes to the CentriPOS Support channel."
        },
        {
          "name": "Normal",
          "description": "Routine question or issue without immediate material operational impact."
        },
        {
          "name": "High",
          "description": "Significant workflow impairment needing prompt attention but without a stated immediate emergency."
        },
        {
          "name": "Urgent",
          "description": "Immediate operational, customer, security, or financial risk; describe the concrete impact."
        },
        {
          "name": "Ticket number and status",
          "description": "Primary reference returned after a successful in-app support request."
        },
        {
          "name": "Related knowledge",
          "description": "Customer-facing help matches returned with the ticket for immediate self-service."
        },
        {
          "name": "/support",
          "description": "Branded help-center contact page combining email, phone, and checklist paths."
        },
        {
          "name": "support@getcentri.com",
          "description": "Published CentriPOS product-support email."
        },
        {
          "name": "(614) 769-7619",
          "description": "Published Centri onboarding and product-support phone number."
        },
        {
          "name": "Article Contact support",
          "description": "Email link prefilled with the current guide title; it does not automatically include operating context or reproduction details."
        },
        {
          "name": "Operating context",
          "description": "Business, location, register, session state, effective role, device/browser, and timestamp with time zone."
        },
        {
          "name": "Expected / actual",
          "description": "Short factual comparison of the intended result and observed result."
        },
        {
          "name": "Reproduction steps",
          "description": "Smallest repeatable sequence using exact screen and control names."
        },
        {
          "name": "Business impact",
          "description": "Specific staff, customer, location, selling, reporting, fulfillment, payment, or integration consequence."
        },
        {
          "name": "Safe reference",
          "description": "Minimum non-secret identifier needed to locate the record."
        },
        {
          "name": "Safe screenshot",
          "description": "Cropped/redacted evidence containing no unnecessary customer, payment, credential, PIN/QR, or unrelated browser information."
        },
        {
          "name": "Uncertain financial event",
          "description": "State that must be investigated before retry, void, refund, close, relink, or repair to avoid compounding harm."
        },
        {
          "name": "Same support thread",
          "description": "One ticket/email/call reference that keeps later evidence and resolution together."
        },
        {
          "name": "No customer screenshot required",
          "description": "When privacy prevents a safe capture, send text context and a minimal safe identifier instead of exposing or fabricating an image."
        }
      ],
      "expectedResult": "The support request identifies the exact screen, time, business location, expected behavior, actual behavior, repeatable steps, and only the minimum safe record references needed to investigate.",
      "troubleshooting": [
        "Capture the exact screen, time, expected result, and smallest repeatable steps.",
        "Remove unnecessary customer and payment information from screenshots.",
        "Include only safe receipt, order, or record references when contacting support."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "use-centri-ai",
      "url": "https://platform.getcentri.com/centripos/use-centri-ai",
      "title": "Use CentriAI and contact support",
      "summary": "Ask a page-aware CentriAI question, inspect its sources and proposed actions, continue private conversation history, or open a contextual ticket routed to the CentriPOS Support channel.",
      "collection": {
        "id": "getting-started",
        "title": "Getting started"
      },
      "section": "Help where you work",
      "introduction": "CentriAI receives the active tenant, page path and label, location, and register when available. It can answer with live or knowledge-backed context, but a response is not authorization to change customer, inventory, payment, accounting, or register data. Actions that require confirmation are presented as review controls. Never put passwords, card data, tokens, or unnecessary customer information into a prompt or ticket.",
      "beforeYouBegin": "Sign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.",
      "steps": [
        "Choose the Sparkles Centri AI control in the operating-context bar. On mobile it opens as a bottom sheet; on larger screens it opens from the right. The header states the current page label, such as Sell, Market Intelligence, Engage, Sales, Products, Inventory, Admin, or Dashboard.",
        "Choose Ask for a question. Use a rotating page-specific suggestion or enter your own prompt. CentriPOS sends the question with the current tenant, location, register, page path and label, local time zone, and the current day’s UTC boundaries to the answer service.",
        "Wait while Checking live CentriPOS data… is shown. Read the answer and inspect Sources used when present. Verify dates, scope, customer identity, receipt, register, location, and totals against the underlying CentriPOS screen before acting.",
        "If an answer returns a pending action requiring confirmation, use its review control rather than assuming the action already occurred. Current review routes can open location/register selection, Sell, Products, a matching customer profile, or a report. Multiple matching customers are presented separately.",
        "Use the clock/history button to open up to 12 recent conversations for the current tenant and effective user. Pinned threads sort first. Choose a thread to continue it, use the Star to pin or unpin, or choose New to avoid adding unrelated context to an older thread.",
        "If Saved conversations are not available yet or This conversation could not be saved yet appears, a local response can still be visible, but do not assume it will survive refresh. If the answer request fails, CentriAI states that no POS action was performed and offers retry or support.",
        "Choose Help for product guidance. Related knowledge can link back to customer-facing articles on support.centripos.com. Use the article itself for the maintained step-by-step procedure and exact screenshot boundary.",
        "Choose Support when a person needs to investigate. Describe what happened using at least three trimmed characters, select Normal, High, or Urgent based on real business impact, and choose Open support ticket once.",
        "The ticket request includes the active tenant, current thread when present, a first-line summary capped at 200 characters, full description, priority, page context, public plan name, and effective profile email. On success, record the Ticket number and status. It is saved in CentriPOS and routed to the CentriPOS Support channel.",
        "Open any Related knowledge links supplied with the ticket result. If ticket creation fails, copy the safe description and use support@getcentri.com or (614) 769-7619 from the support site. Include page, context, time zone, expected and actual result, repeatable steps, impact, and only a safe record reference."
      ],
      "controls": [
        {
          "name": "Centri AI / Sparkles",
          "description": "Exact in-product launcher in the operating-context bar."
        },
        {
          "name": "Page-aware header",
          "description": "Names the supported product area from which CentriAI was opened."
        },
        {
          "name": "Ask",
          "description": "Question-and-answer mode using current page and operating context."
        },
        {
          "name": "Prompt suggestions",
          "description": "Rotating page-specific starting questions."
        },
        {
          "name": "Checking live CentriPOS data…",
          "description": "Answer request is still running."
        },
        {
          "name": "Sources used",
          "description": "Returned evidence labels, optional details, and counts supporting the response."
        },
        {
          "name": "Pending action",
          "description": "Structured proposal requiring confirmation and opening a review destination; it is not proof that an operation already happened."
        },
        {
          "name": "Matching customers",
          "description": "Separate identity choices when a profile request has multiple matches."
        },
        {
          "name": "Conversation history",
          "description": "Up to 12 tenant/user-scoped recent threads with pinned items ordered first."
        },
        {
          "name": "Star",
          "description": "Pins or unpins a saved conversation."
        },
        {
          "name": "New",
          "description": "Starts a draft thread without adding to the open conversation."
        },
        {
          "name": "Persistence warning",
          "description": "Saved thread or message storage is unavailable or failed; local content may not survive refresh."
        },
        {
          "name": "Help",
          "description": "Product-guidance mode connected to published knowledge paths."
        },
        {
          "name": "Support",
          "description": "Contextual ticket mode inside CentriAI."
        },
        {
          "name": "Support note",
          "description": "At least three trimmed characters; the first line becomes a summary limited to 200 characters."
        },
        {
          "name": "Normal / High / Urgent",
          "description": "User-selected ticket priority based on business impact."
        },
        {
          "name": "Open support ticket",
          "description": "Sends the tenant, thread, description, priority, page/account context, plan, and effective email."
        },
        {
          "name": "Ticket number and status",
          "description": "Confirmation that the request was saved and routed to the CentriPOS Support channel."
        },
        {
          "name": "Related knowledge",
          "description": "Help-center matches returned with the created ticket."
        },
        {
          "name": "support@getcentri.com",
          "description": "Published human email fallback."
        },
        {
          "name": "(614) 769-7619",
          "description": "Published Centri support phone number."
        },
        {
          "name": "No exact screenshot",
          "description": "The approved Amelia Grant Harbor & Hearth manifest contains no safe final-state CentriAI drawer, so this guide uses no invented image."
        }
      ],
      "expectedResult": "This workflow is complete only after CentriPOS reflects the intended result. Final checkpoint: Open any Related knowledge links supplied with the ticket result. If ticket creation fails, copy the safe description and use support@getcentri.com or (614) 769-7619 from the support site. Include page, context, time zone, expected and actual result, repeatable steps, impact, and only a safe record reference.",
      "troubleshooting": [
        "Use the newest invitation or password-reset link; older links may no longer be valid.",
        "Confirm the email address matches the account your administrator invited.",
        "If a business or location is missing, ask an administrator to review your role and access."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "scheduled-offerings-overview",
      "url": "https://platform.getcentri.com/centripos/scheduled-offerings-overview",
      "title": "Plan events and scheduled offerings",
      "summary": "Model a one-off event, recurring class, camp, after-school program, or large conference as an offering with occurrence series, durable dated instances, sellable ticket products, shared capacity, registration, publication, and calendar records.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Events overview",
      "introduction": "Events is a controlled-rollout workspace. When the feature is enabled for the selected business, its records remain tenant-bound and role-controlled. An offering describes what is sold; occurrences describe when attendance happens; ticket options connect normal CentriPOS products of type event_ticket to one or more occurrences.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Events → Overview and confirm the business and timezone shown in the operating-context bar. If the Events navigation is absent, the scheduled-offerings entitlement or rollout is not enabled for this business.",
        "Choose New offering. Select the operating pattern that best describes the program: one-off event, camp, class or after-school series, conference, appointment-style offering, or another merchant-defined event kind. The pattern organizes the setup; it does not create a separate database or payment system.",
        "Enter a stable public slug, name, short summary, full formatted description, delivery format, status, and visibility. Public appears in eligible published feeds, Unlisted requires the direct published link, and Private stays out of public discovery.",
        "Set the offering timezone before creating occurrences. Enter the venue and structured location, online meeting URL for online or hybrid attendance, support email and phone, registration opening and closing times, and optional age boundaries.",
        "Add a primary image with meaningful alt text, then use Assets for approved images, documents, attachments, maps, video links, or downloads. Choose Public only for files any visitor may receive. Choose Attendees only for files intended for an authorized registration portal. Forms, waiver evidence, medical details, private notes, and ticket credentials are never publication assets.",
        "Configure portal settings for the purchaser and participant experience. Decide which registration summary, calendar link, ticket, instructions, and public attachments an authorized household can see. Portal settings do not override contact authorization or make sensitive registration answers public.",
        "Create one or more occurrences in the builder. Use one occurrence for a one-off event, daypart occurrences for a camp, normalized room-and-track sessions for a conference, or an IANA-timezone recurrence rule for a class or after-school series. A recurring occurrence is the authoring series; CentriPOS materializes each actual date as a durable instance before date-specific enrollment, admission, or calendar evidence.",
        "Create ticket options only after the required event_ticket products exist. Connect each ticket option to its applicable occurrences and capacity pools, then set its sale window, order minimum and maximum, seats per ticket, eligibility, portal behavior, and display order.",
        "Review the offering from Overview before publishing: content, timezone, occurrences, exceptions, ticket products and prices, shared capacity, registration window, assets, feed placement, portal exposure, and calendar projection must agree.",
        "Publish only after a complete internal registration test. A Published offering can enter selected public feeds and downstream integrations; Draft and Scheduled records remain staff-controlled, and Cancelled or Archived records must not be advertised as bookable.",
        "After launch, use Registrations, Check-in, Waitlist, Event reports, Publishing, Configuration, and Master calendar as connected views of the same records. Configuration authors versioned forms and waivers, participant add-ons, people and roles, rooms, tracks, and audience-scoped assets. Do not create duplicate products or contacts to compensate for a filter or status problem.",
        "For a recurring schedule, use Manage exceptions to cancel, reschedule, or modify one generated date while preserving its original series identity. Use staged reconcile-series for a broad series rewrite; do not shift already materialized dates by a fixed UTC offset across daylight-saving boundaries.",
        "Create a reusable venue before assigning a physical location. Store its structured address, country code, map provider/place identity or approved map URL, coordinates when authorized, public contact details, arrival instructions, accessibility summary, and valid IANA timezone. An occurrence can deliberately override the offering venue for one room, day, or campus.",
        "For native private event files, managers upload at most 25 MiB into the protected event-assets store. Native files use Attendees or Staff visibility only. Authorized attendees receive a branded five-minute download URL; public and integration payloads never receive a bucket name, object path, Supabase hostname, or project URL."
      ],
      "controls": [
        {
          "name": "Events",
          "description": "Entitlement- and role-controlled workspace for offerings, calendar, registration, attendance, reporting, and publication."
        },
        {
          "name": "Offering",
          "description": "Full-content program or event definition shared by its dates, tickets, registrations, assets, publication, and portal settings."
        },
        {
          "name": "Event kind",
          "description": "Merchant-defined classification such as camp, conference, class, after-school program, appointment, or one-off event."
        },
        {
          "name": "Delivery format",
          "description": "In person, online, or hybrid."
        },
        {
          "name": "Visibility",
          "description": "Public, unlisted, or private discovery boundary."
        },
        {
          "name": "Occurrence",
          "description": "Authored attendance block or recurrence series with schedule, location, status, and enrollment policy."
        },
        {
          "name": "Occurrence instance",
          "description": "Durable concrete date under an occurrence, preserving original_start_at when its effective time changes."
        },
        {
          "name": "event_ticket product",
          "description": "Normal CentriPOS product type used for a sellable ticket or registration choice."
        },
        {
          "name": "Ticket option",
          "description": "Offering-specific configuration that links one event_ticket product to occurrences and capacity pools."
        },
        {
          "name": "Assets",
          "description": "Images and approved public attachments associated with an offering or occurrence."
        },
        {
          "name": "Portal settings",
          "description": "Authorized customer-portal presentation rules; never a substitute for identity and privacy checks."
        },
        {
          "name": "Publish",
          "description": "Makes an eligible offering available to selected publication feeds and event integrations."
        },
        {
          "name": "Controlled rollout",
          "description": "Feature and API operations remain unavailable unless the selected business has been explicitly enabled."
        },
        {
          "name": "Configuration",
          "description": "Offering-level manager for forms, waivers, add-ons, event people and roles, rooms, tracks, and assets."
        },
        {
          "name": "Manage exceptions",
          "description": "Staff editor for one-date cancellation, reschedule, or modification beneath a recurring series."
        },
        {
          "name": "Reusable venue",
          "description": "Structured Place record shared across offerings, occurrence overrides, maps, metadata, calendar locations, layouts, and reporting."
        },
        {
          "name": "Asset audience",
          "description": "Public for anonymous feed delivery, Attendees for an authorized registration portal, or Staff/private when the file must not leave operations."
        },
        {
          "name": "Native event asset",
          "description": "Manager-only protected upload, at most 25 MiB, stored outside anonymous publication and delivered through a short-lived branded capability URL."
        }
      ],
      "expectedResult": "The selected business has one coherent offering whose content, occurrences, ticket products, capacity, registration window, publication, portal, and calendar settings pass a controlled internal registration before publication.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "event-ticket-products-capacity",
      "url": "https://platform.getcentri.com/centripos/event-ticket-products-capacity",
      "title": "Configure event-ticket products and capacity",
      "summary": "Sell admission through normal event_ticket products while preventing morning, afternoon, full-day, room, session, meal, equipment, or venue choices from overselling the same scarce resource.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Tickets & capacity",
      "introduction": "A ticket is a product type, but availability is event-specific. The catalog product supplies the price and receipt identity; the ticket option maps that product to attendance; capacity pools represent the seats or resources consumed. One ticket can consume several pools, and several tickets can compete for one pool.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Products & Catalog and create or review each sellable registration choice as product type event_ticket. Give the product a durable name, SKU, price, tax behavior, images, reporting category, and active status. For a separately published normal storefront sale, also enable Sell online, publish the product, give it a valid SEO slug, and publish the tenant storefront. Do not use a zero-dollar merchandise line as a substitute for paid admission.",
        "Return to Events → Offerings, open the offering, and choose Ticket options. Connect each option to exactly one active same-business event_ticket product. When the product and storefront are published and the registration definition is complete, the public feed returns checkout_status ready plus a branded purchase path into the normal CentriPOS storefront. Missing storefront, product, capacity, or registration prerequisites fail closed with a non-ready checkout status.",
        "Set the option code and customer-facing label. Configure Draft, Active, Paused, Sold out, or Archived status; sales opening and closing times; minimum and maximum per order; seats per ticket; eligibility rules; and sort order.",
        "Choose every occurrence the option admits. A conference pass may cover a large agenda; a morning camp ticket covers morning, an afternoon ticket covers afternoon, and a full-day ticket covers morning, the supervised lunch bridge, and afternoon. Early arrival and late pickup are separate entitlements unless the merchant deliberately includes them. Mark attendance-required occurrences explicitly.",
        "Create a capacity pool for each genuinely scarce resource: total campers, morning seats, afternoon seats, room occupancy, bus seats, robot kits, meal seats, or conference workshop capacity. Choose offering-wide capacity when all dates share one limit or occurrence capacity when each date is independent.",
        "Set capacity, optional overbook allowance, waitlist behavior, and Active, Paused, or Closed status. An overbook allowance expands the enforceable ceiling and should be used only with an explicit operating plan.",
        "Allocate each ticket option to every pool it consumes. Set units per seat when one attendee consumes more than one unit of a resource. A registration is accepted only when all linked pools can cover its seat count.",
        "For camp dayparts, avoid double counting. Morning consumes the morning pool, afternoon consumes the afternoon pool, and full day consumes both plus any lunch-specific pool. Early-arrival and late-pickup choices consume their own care pools. Add an overall camper, building, or staffing pool only when that shared physical limit really exists.",
        "Configure optional T-shirts, take-home robots, meals, parking, kits, or supplies as participant add-ons backed by ordinary published products and variants. Checkout creates real receipt lines and assigns the selected units to the attendee, preserving product revenue, tax, return, inventory, and unit reporting separately from admission.",
        "Run controlled tests before opening sales: one ticket, several ticket units, the last seat, an over-capacity request, an adult self-attendee, a youth attendee with guardian authority, a deferred group pass, required forms and waiver, a session choice, and an add-on variant. Each integer ticket unit must become one receipt-linked registration; pending payment keeps a finite hold, final payment confirms and issues credentials, and a void, return, refund, or quantity reduction reverses only its matching entitlements.",
        "Use Reports to compare ticket units, seats, capacity consumed, remaining capacity, registration revenue, discounts, refunds, and linked merchandise units. Ticket quantity, seat count, and capacity units can differ; choose the correct measure for each question.",
        "Use assignment_policy at_checkout for one-seat ticket units that collect an attendee during checkout. Use deferred_allowed only for multi-seat group passes; it reserves the documented seats and requires later explicit attendee, form, waiver, add-on, and session assignment instead of pretending one name represents the group.",
        "For a recurring occurrence-wide pool, CentriPOS measures attendee-selected session usage by the peak concrete occurrence instance, not by summing the entire series. This reuses the physical ceiling on each date without making a weekly class appear cumulatively sold out.",
        "Start repeated admission choices from a reusable ticket preset. Applying a preset copies a versioned snapshot of its label, assignment, quantity, price, capacity, inventory, admission, and sales-window defaults into the ticket option; later preset edits never silently rewrite an already published option.",
        "Use the visual purchase-rule builder for bounded groups, conditions, and actions such as eligibility, quantity, discount, access-code, or inventory behavior. Preview evaluation explains the rule graph for staff, but only the storefront quote can authorize the final purchaser, price, code reservation, capacity, and checkout state.",
        "For general admission, continue to use shared capacity pools. For a physical venue, publish one reusable seating layout with sections, rows, exact seats, accessibility attributes, companion relationships, and pricing zones; attach a versioned on-sale seating configuration to the offering, occurrence, or concrete instance, then map each ticket to permitted zones.",
        "A reserved seat moves through available, held, assigned, released, blocked, or maintenance state with append-only inventory evidence. Checkout holds are short-lived and bound to their quote intent; payment finalization converts the exact hold to a registration and ticket, while expiry, failure, cancellation, transfer, or refund uses the authoritative release lifecycle."
      ],
      "controls": [
        {
          "name": "Product type: event_ticket",
          "description": "Catalog classification required for products linked to event ticket options."
        },
        {
          "name": "Ticket option",
          "description": "Offering configuration around a sellable product, admission coverage, eligibility, order limits, and display order."
        },
        {
          "name": "Seats per ticket",
          "description": "Number of attendee seats represented by one purchased ticket unit."
        },
        {
          "name": "Occurrence assignment",
          "description": "Dated sessions that the ticket admits."
        },
        {
          "name": "Capacity pool",
          "description": "Shared enforceable inventory of seats or another constrained resource."
        },
        {
          "name": "Offering-wide pool",
          "description": "One limit shared across an entire offering."
        },
        {
          "name": "Occurrence pool",
          "description": "Limit attached to one dated attendance block."
        },
        {
          "name": "Units per seat",
          "description": "Capacity units consumed for each registered seat."
        },
        {
          "name": "Overbook allowance",
          "description": "Explicit quantity permitted above base capacity."
        },
        {
          "name": "Waitlist enabled",
          "description": "Allows demand to queue when linked capacity cannot cover confirmation."
        },
        {
          "name": "Paused / Closed",
          "description": "Stops normal allocation without deleting historical registration data."
        },
        {
          "name": "Merchandise product",
          "description": "Separate normal product for shirts, robots, meals, or supplies when unit, tax, inventory, or revenue reporting matters."
        },
        {
          "name": "Public checkout status",
          "description": "ready means the published event ticket has a validated branded registration path; every other checkout status is fail-closed and omits a usable registration path."
        },
        {
          "name": "Receipt entitlement adapter",
          "description": "One stable receipt-line/unit identity becomes one linked registration and, after qualifying finalization, one issued ticket."
        },
        {
          "name": "checkout_status: ready",
          "description": "The event ticket, storefront, registration definition, sales window, and capacity passed the public fail-closed checks and a branded purchase path is available."
        },
        {
          "name": "assignment_policy",
          "description": "at_checkout for one attendee per ticket unit; deferred_allowed for a multi-seat pass completed later."
        },
        {
          "name": "Lunch bridge",
          "description": "Separate supervised occurrence included by a full-day camp option; not inferred from overlapping AM and PM times."
        },
        {
          "name": "Participant add-on",
          "description": "Ordinary product or variant assigned to one attendee and retained as its own receipt line."
        },
        {
          "name": "Recurring capacity peak",
          "description": "Highest selected-seat usage on one concrete instance; the series ceiling is not cumulatively consumed across dates."
        },
        {
          "name": "Ticket preset",
          "description": "Reusable defaults copied into a versioned ticket-option snapshot rather than a live inheritance link."
        },
        {
          "name": "Visual purchase rule",
          "description": "Bounded rule-set, group, condition, and action graph; management preview is explanatory and checkout evaluation is authoritative."
        },
        {
          "name": "Physical seat lifecycle",
          "description": "Published venue layout → on-sale occurrence configuration → pricing-zone rule → temporary hold → ticket assignment → append-only inventory evidence."
        },
        {
          "name": "Accessibility seat data",
          "description": "Structured wheelchair, transfer, companion, obstructed-view, and note attributes used for discovery and controlled seat selection."
        }
      ],
      "expectedResult": "Every active ticket option references an active event_ticket product, admits exactly the intended occurrences, consumes every required shared pool, rejects or waitlists excess demand, and reports price, units, seats, and merchandise separately.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "camp-conference-session-patterns",
      "url": "https://platform.getcentri.com/centripos/camp-conference-session-patterns",
      "title": "Build camps, conferences, classes, and one-off schedules",
      "summary": "Use offerings, occurrences, concrete instances, recurrence rules, exceptions, ticket bundles, and shared capacity to support a single workshop, a recurring after-school series, half-day or full-day camps, and multi-session conferences.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Schedule patterns",
      "introduction": "Do not represent every date as a disconnected product. Preserve one reportable offering identity, then use occurrences for the actual dates and ticket options for the purchasable attendance packages. This keeps repeat attendance, revenue, capacity, calendar, and customer history comparable.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "For a one-off event, create one offering and one occurrence with exact start, end, timezone, venue, status, attendee instructions, and calendar visibility. Create one or more event_ticket choices only when pricing or admission differs.",
        "For a repeating after-school program, choose the Afterschool series template or create one recurring offering. Store the normal weekly cadence as an RFC 5545 rule in a valid IANA timezone, then materialize durable concrete dates before date-specific enrollment, check-in, or calendar evidence. Capture school, grade, dismissal method, and authorized pickup only in correctly classified registration questions.",
        "Model holidays, weather closures, rescheduled dates, and one-date overrides with Manage exceptions. The durable instance keeps original_start_at and its stable identity even when its effective time changes; attendee calendars receive the correct EXDATE or RECURRENCE-ID evidence instead of a second unrelated event.",
        "For each camp date, create separate early-arrival, morning, supervised lunch-and-recess, afternoon, and late-pickup occurrences as applicable. The camp template uses stable session kinds early_care, morning, lunch_bridge, afternoon, and late_care with editable local times.",
        "Create morning and afternoon half-day ticket options for their respective occurrences. Create one full-day option that admits morning, lunch_bridge, and afternoon and allocates both half-day pools. Early arrival and late pickup remain independent tickets or add-on entitlements with their own capacity unless intentionally bundled.",
        "Give lunch, early care, late care, rooms, equipment, bus seats, and other scarce resources explicit occurrences or capacity pools. Do not infer entitlement or capacity from overlapping times, ticket wording, or a free-text description.",
        "For a multi-day camp, repeat the daily occurrence pattern under the same offering or use a carefully reviewed recurrence rule. Decide whether the ticket covers one day, selected days, or the whole week, and connect it only to those occurrences.",
        "For a conference, create the conference as the offering and keynotes, workshops, meals, expo blocks, or breakouts as occurrences. Normalize rooms, tracks, speakers, sponsors, and staff. Use selection groups for choose-one or bounded attendee agendas, and give limited sessions their own occurrence-level capacity pools.",
        "Use ticket eligibility and order limits for age bands, membership eligibility, staff or speaker passes, household limits, or other supported rules. Eligibility does not replace legal consent, waiver, or identity verification.",
        "Use calendar views to inspect collisions across events, deliveries, service appointments, work, and custom company entries. The master calendar is an operational schedule; capacity is still enforced by event pools rather than by visual overlap.",
        "Before publication, test each purchasable path and list the resulting occurrences, concrete instances, pools, participant seat count, receipt line, portal schedule, and calendar download. Correct the model instead of adding manual notes to explain inconsistent entitlement.",
        "For a broad recurrence edit, expand the desired local-time series and call the staged reconcile-series operation in batches of at most 500 concrete instances, up to 10,000 for one reconciliation. Reuse the returned reconciliation_id, send a new Idempotency-Key per batch, and set is_final_batch only after the complete replacement window is staged.",
        "Large conferences use the same records as small camps. The builder supports one-at-a-time session authoring and validated CSV import, and the registration definition supports up to 10,000 sessions through paging, search, and bounded batched writes. Never put the whole agenda into one browser request.",
        "A limited conference session receives its own occurrence capacity pool even when no ticket option preallocates it. That unallocated pool lets attendee agenda selection enforce the physical room limit without falsely treating all conference-pass sales as reserved seats in every breakout.",
        "The Event reports screen labels its first 100 session rows as partial. Use the full CSV/export path for a complete large-conference result and preserve occurrence, instance, track, room, participant, ticket, and lifecycle identifiers.",
        "A no_overlap rule compares selections only within the same active selection group. Use separate groups for independent choice sets; do not assume one group’s conflict policy globally blocks every simultaneous session in the offering."
      ],
      "controls": [
        {
          "name": "One-off pattern",
          "description": "One offering with one dated occurrence."
        },
        {
          "name": "Series pattern",
          "description": "One offering with a recurring or multi-date occurrence schedule."
        },
        {
          "name": "Camp pattern",
          "description": "Morning, afternoon, full-day, multi-day, extended-care, and resource capacity modeled explicitly."
        },
        {
          "name": "Conference pattern",
          "description": "One offering with many sessions and optional session-specific ticket or capacity rules."
        },
        {
          "name": "Session kind",
          "description": "Stable classification such as morning, afternoon, keynote, workshop, meal, or general."
        },
        {
          "name": "Recurrence rule",
          "description": "Normal repeating schedule definition on an occurrence."
        },
        {
          "name": "Recurrence exception",
          "description": "Cancellation, reschedule, or field override for one original series date."
        },
        {
          "name": "Occurrence instance",
          "description": "Durable materialized date used by date-specific enrollment, check-in, and calendar evidence."
        },
        {
          "name": "Full-day bundle",
          "description": "One ticket option linked to both morning and afternoon occurrences and pools."
        },
        {
          "name": "General-admission pass",
          "description": "Ticket option admitting multiple conference occurrences."
        },
        {
          "name": "Master company calendar",
          "description": "Unified schedule for event occurrences and other company calendar entries."
        },
        {
          "name": "early_care / late_care",
          "description": "Optional arrival and pickup occurrences with independent entitlement and capacity."
        },
        {
          "name": "lunch_bridge",
          "description": "Supervised full-day bridge between the morning and afternoon occurrences."
        },
        {
          "name": "Selection group",
          "description": "Minimum/maximum attendee session-choice rule, optionally rejecting overlapping selections."
        },
        {
          "name": "reconcile-series",
          "description": "Version-checked staged replacement of a recurring series and its concrete instances without fixed-offset DST drift."
        },
        {
          "name": "Conference session import",
          "description": "Validated CSV path for normalized session rows; definitions may span up to 10,000 sessions through bounded pages and batches."
        },
        {
          "name": "Unallocated occurrence pool",
          "description": "Session-level physical capacity available for attendee selection without being preallocated to every pass product."
        },
        {
          "name": "no_overlap scope",
          "description": "Time-conflict validation among selections that share the same active selection group, not a global offering-wide prohibition."
        }
      ],
      "expectedResult": "The schedule represents the real one-off, series, camp, or conference pattern; recurrence exceptions preserve history; morning, afternoon, and full-day entitlements consume the correct pools; and attendee calendars show only the dates purchased.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "registrations-participants-households",
      "url": "https://platform.getcentri.com/centripos/registrations-participants-households",
      "title": "Manage registrations, guardians, campers, and repeat attendees",
      "summary": "Keep the purchaser or household lead, attendee identities, reusable camper profiles, receipt, ticket, session selections, registration requirements, and attendance connected without duplicating revenue or exposing private child information.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Registration & participants",
      "introduction": "A registration is the paid or reserved entitlement; a participant is the person attending; and the purchaser is the customer who owns the transaction. Adult self-registration, another adult attendee, a youth camper with an authorized guardian, an existing verified customer, and a deferred group pass are distinct identity modes and must never be collapsed by matching only a typed name or email.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Contacts and search for the household lead before creating a duplicate. CentriPOS provisions the protected Parent/Guardian and Camper/Attendee contact types. Household authority, participant identity, and purchaser ownership remain separate even when one person fills several roles.",
        "From a published event feed, choose an option whose checkout_status is ready. The branded storefront revalidates the event_ticket product, sale window, remaining capacity, form and waiver definitions, session choices, add-ons, and ticket quantity before it creates a quote.",
        "For each one-seat ticket unit, choose Another attendee or This ticket is for me. Another attendee creates a distinct adult, guest, or camper profile. This ticket is for me binds the attendee to the verified purchaser customer and never creates a self-guardian link. When the offering has an age policy, birth date is required; when supplied in any case, the purchaser must be at least 216 months old on the first scheduled eligibility date.",
        "For a minor, enter the attendee birth date and purchaser relationship. Checkout records an explicit authorized guardian association so the purchaser can manage that camper registration. It does not infer guardianship from a shared surname, email, address, or payment method.",
        "Anonymous checkout never searches or exposes customer records. Reusing an existing participant_customer_id is restricted to an authenticated, tenant-authorized staff, portal, or API workflow that can prove access to that customer; integrations must not merge adults by email or name alone.",
        "A multi-seat option must use deferred_allowed. Checkout creates a deferred group entitlement and reserves the documented seat count without fabricating participant profiles. The organizer later assigns every attendee and completes required questions, waivers, add-ons, and session selections by the assignment deadline.",
        "Complete every required purchaser-, registration-, and participant-scoped question. Standard answers with an approved report_key can become report dimensions. Medical, accessibility, emergency, pickup, birth-date, signature, and similarly protected values remain sensitive and require dedicated authorization.",
        "Accept each assigned versioned waiver using the displayed content hash and signer name. The immutable acceptance preserves which version was shown; it is not copied into general CRM fields, public feeds, normal reports, or event webhooks.",
        "Choose participant sessions only from the ticket option’s entitled concrete agenda. Selection groups enforce their minimum, maximum, and overlap policy; recurring choices retain occurrence_instance_id so a class date cannot drift to another occurrence.",
        "Choose participant add-ons by product, variant, and quantity. Checkout adds the aggregate products to the sale and retains participant-level assignments so shirts, take-home robots, kits, lunches, parking, or other items reconcile to receipt units and returns.",
        "The quote stores short-lived, tamper-evident registration intents. Final checkout atomically binds the purchaser, receipt line and unit, registration, participant or deferred identity, answers, waiver evidence, session selections, add-on assignments, capacity, and ticket lifecycle. A mismatched or expired intent fails closed.",
        "Pending or partially paid sales hold capacity only until capacity_hold_expires_at and do not expose an active credential. Completed paid/closed sales confirm and issue tickets. Returns, voids, refunds, quantity reductions, cancellations, and expired holds reverse only their matching entitlements.",
        "Use the authorized customer portal and staff roster to review purchaser, guardian, participant, repeat-attendee, requirement-completion, schedule, asset, receipt, and ticket state. Use separate report dimensions for siblings, repeat campers, adult self-attendees, group passes, and purchasers.",
        "Treat receipt-backed purchaser ownership, ticket entitlement, sale and line identity, seat count, amount, and currency as guarded snapshots. Change them only through the source receipt or authoritative registration workflow; the database rejects a generic registration update that could detach financial or entitlement history."
      ],
      "controls": [
        {
          "name": "Parent/Guardian",
          "description": "Protected system contact type for the household lead, payer, or authorized guardian; it is assigned from purchaser and guardian relationships."
        },
        {
          "name": "Camper/Attendee",
          "description": "Protected system contact type assigned when a participant is linked to a customer profile; the participant record remains separate from the purchaser."
        },
        {
          "name": "Purchaser",
          "description": "Customer connected to the transaction and registration order; not automatically the attendee."
        },
        {
          "name": "Receipt-created entitlement",
          "description": "One registration per qualifying integer event-ticket receipt unit, initially participant-unassigned until the follow-up workflow links an attendee."
        },
        {
          "name": "Capacity hold",
          "description": "Expiration on a Pending registration that prevents an unpaid order from consuming capacity forever."
        },
        {
          "name": "Guardian relationship",
          "description": "Explicit participant-to-customer association used for authorized household context."
        },
        {
          "name": "Registration participant",
          "description": "Role and seat relationship between one registration and one reusable attendee."
        },
        {
          "name": "Occurrence entitlement",
          "description": "Dated sessions the ticket option permits the registration to select or attend."
        },
        {
          "name": "Occurrence enrollment",
          "description": "Participant-level Selected, Waitlisted, Cancelled, or admission-derived Attended record for one entitled session."
        },
        {
          "name": "enrollment_policy",
          "description": "entitlement_only, selection_optional, or selection_required behavior on an occurrence."
        },
        {
          "name": "Post-purchase completion",
          "description": "Enabled API or approved workflow that assigns participants, selects sessions, and captures required answers or consents after normal product checkout."
        },
        {
          "name": "Portal completion projection",
          "description": "Overall and per-requirement status only; never answer or signature content."
        },
        {
          "name": "Sensitive answer",
          "description": "Restricted medical, emergency, waiver, pickup, child identity, or comparable private data."
        },
        {
          "name": "Repeat participant",
          "description": "Same reusable participant identity registered for more than one offering or period."
        },
        {
          "name": "Household reporting",
          "description": "Purchaser or guardian-based grouping that preserves each attendee identity."
        },
        {
          "name": "new_participant",
          "description": "Creates a distinct adult, guest, or camper identity; it is never silently merged by name or email."
        },
        {
          "name": "purchaser_self",
          "description": "Uses the verified adult purchaser as attendee without a household or guardian self-link."
        },
        {
          "name": "existing_customer",
          "description": "Authenticated identity mode that binds a participant to an already authorized customer profile."
        },
        {
          "name": "deferred_group",
          "description": "Reserves a multi-seat pass while attendee assignment and per-person requirements remain explicitly outstanding."
        },
        {
          "name": "guardian_required",
          "description": "Youth-attendee rule that requires an explicit purchaser-to-participant guardian relationship."
        },
        {
          "name": "Adult eligibility",
          "description": "purchaser_self must be at least 216 months old at the first scheduled eligibility date when a birth date is supplied; an offering age policy makes birth date required."
        },
        {
          "name": "Receipt-backed guard",
          "description": "Database protection against generic rewrites of purchaser, entitlement, receipt identity, seats, amount, or currency."
        }
      ],
      "expectedResult": "Each receipt-backed registration is attached to the correct purchaser, reusable participant, guardian relationship, ticket option, seat count, answers, and lifecycle state, so repeat-attendee and household reporting works without exposing protected data.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "tickets-waitlist-checkin",
      "url": "https://platform.getcentri.com/centripos/tickets-waitlist-checkin",
      "title": "Issue tickets, manage the waitlist, and record attendance",
      "summary": "Move confirmed registrations through credential delivery, concurrency-safe waitlist offers, high-volume check-in, check-out, and auditable correction without overwriting history.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Attendance operations",
      "introduction": "Ticket credentials and check-in records are operational evidence. Check-ins are append-only: a mistake is corrected with a Void input that produces new audit evidence, not by editing or deleting the original scan. Capacity and registration state are validated again during admission.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Events → Registrations and confirm the offering, registration number, purchaser, assigned participant, ticket option, occurrence itinerary, seat count, receipt state, requirement completion, and registration status. A receipt-created entitlement can remain unassigned until the post-purchase participant workflow is complete.",
        "A confirmed group registration can hold pending_assignment tickets while seats remain unassigned. pending_assignment is non-admissible and exposes no code or QR. Assign a participant through the authoritative seat/transfer flow; only a participant-bound, unexpired Valid or Used ticket projects an active credential to an authorized viewer. Voided, Transferred, Expired, and pending history remains visible without a credential.",
        "Use Events → Waitlist to review Waiting and Offered demand. Offer next spot calls the server's atomic queue command; use the documented row lifecycle actions for manual cancellation, priority, and acceptance changes.",
        "Offer next is atomic. The service requeues expired offers, evaluates currently available linked capacity, locks eligible rows, and claims one entry by priority and queue position. Concurrent callers cannot offer the same row. Never imitate this behavior with a client-side sort followed by a normal update.",
        "An Offered entry has an expiration and capacity reservation. Accepted points to the resulting registration; Expired, Cancelled, and superseded records remain reportable history. Use the documented waitlist operations for lifecycle changes rather than bypassing another attendee with an unrelated confirmed registration.",
        "Open Events → Check-in and choose the exact offering or occurrence context. Confirm local time, venue, active station, and whether the action is In, Out, or Void. Roster/manual admission sends exact ticket_id plus participant_id and fails closed when a duplicate name, group, or registration search is ambiguous; scanners may alternatively submit one authorized credential.",
        "Submit only the documented check-in input. The atomic admission service locks the registration and ticket, validates participant and occurrence entitlement plus lifecycle state, derives Accepted, Denied, Duplicate, or Voided, and updates accepted ticket and registration state in the same transaction. The caller cannot supply its own result, actor, denial reason, or audit metadata.",
        "Use events:attendance:write for check-in creation and events:attendance:read for attendance records. Keep events:credentials:read/write for scan credentials and events:registrations:read/write for registration lifecycle. A manual override is not an unrestricted success flag; it requires events:attendance:override, an explicit reason, and server-recorded evidence.",
        "For check-out, submit an Out direction. To correct an erroneous attendance action, submit Void with its required operational reason. Never PATCH or DELETE the original evidence; the current API intentionally exposes check-in list, create, and get operations only.",
        "For an offline scanner, persist each attempt locally with the exact offering, registration, ticket and participant context, occurrence_instance_id when applicable, device_id, capture time, and a stable client_scan_id. POST 1–500 attempts to /events/{event_id}/checkins/batch. HTTP 200 is intentionally partial: each item returns an explicit accepted or denied safe checkin result, or an error, and a denied row never rolls back accepted peers. Batch output strips credentials and denial detail.",
        "Reuse the same Idempotency-Key for a retry of the same single-scan or batch request. Within an offline batch, keep the same device_id and client_scan_id for a retry of one physical scan; changing that scan body under the same stable identity conflicts. This protects arrivals after a timeout without suppressing a genuinely separate later action.",
        "After the occurrence, reconcile confirmed seats, issued tickets, accepted entries, unique participants, no-shows, check-outs, denials, duplicates, void corrections, and waitlist conversion. Do not place ticket codes or protected registration answers in routine reports, webhook consumers, or CRM fields.",
        "A single denied or duplicate admission is still committed as append-only evidence and then returns 409 event_admission_not_accepted. The error includes only safe evidence identifiers, direction, result, admitted quantity, and time—never a credential, denial reason, actor, device, or arbitrary metadata.",
        "For a credential-based offline scan, request identity binds a one-way credential digest rather than the raw credential. Retries remain idempotent without putting a reusable ticket secret into request-hash evidence or logs.",
        "Use the camera-first scanner on a registered device. Download its bounded device manifest while online, then scan into the encrypted local queue when connectivity is unavailable. Reconnect and synchronize in batches of at most 500; server admission remains authoritative and the device retires or refreshes its manifest on the documented lifecycle.",
        "PDF tickets are branded on demand. Enable Apple Wallet or Google Wallet only after a manager chooses Check readiness in the tenant’s own isolated data plane. Apple readiness builds and signs a real pass; Google readiness signs with the project-local service account, exchanges an OAuth token, and reads the exact configured event-ticket class from the Google Wallet API. The browser cannot mark a provider Ready and a master-project secret is never accepted as a substitute for tenant-project credentials.",
        "Provision Apple Wallet only through the tenant project secret manager with APPLE_WALLET_PASS_TYPE_IDENTIFIER, APPLE_WALLET_TEAM_IDENTIFIER, APPLE_WALLET_WWDR_PEM, APPLE_WALLET_SIGNER_CERT_PEM, APPLE_WALLET_SIGNER_KEY_PEM, and optional APPLE_WALLET_SIGNER_KEY_PASSPHRASE. Provision Google Wallet with GOOGLE_WALLET_ISSUER_ID, GOOGLE_WALLET_CLIENT_EMAIL, and GOOGLE_WALLET_PRIVATE_KEY_PEM. Never paste any value into the settings screen, documentation, logs, browser storage, or a support ticket.",
        "Enter the full existing Google EventTicketClass ID as issuer ID plus class suffix, such as 3388.event_admission. The class must belong to the configured issuer, be readable by the tenant service account, and have UNDER_REVIEW or APPROVED status. Save-to-Wallet tokens reference that exact verified class and never create a substitute class from an offering ID.",
        "The manager-authenticated readiness broker resolves the exact active tenant data plane and invokes its service-only readiness probe. Recheck after provider identifiers or tenant-plane credentials change; a failed probe stores only safe provider state and diagnostics, never private key or certificate material."
      ],
      "controls": [
        {
          "name": "Ticket code / QR",
          "description": "Active admission credential returned only with events:credentials:read for a participant-bound, unexpired Valid or Used ticket."
        },
        {
          "name": "Credential omission",
          "description": "Routine registration-read ticket projections omit ticket_code and mark credential_fields_omitted."
        },
        {
          "name": "Pending assignment / Valid / Used / Voided / Transferred / Expired",
          "description": "Exact ticket lifecycle. Pending assignment is unassigned and non-admissible; only eligible Valid or Used tickets have an active credential."
        },
        {
          "name": "Waitlist position",
          "description": "Stable queue order evaluated after priority."
        },
        {
          "name": "Offer next",
          "description": "Atomic expiry cleanup, capacity reservation, and one-row claim; safe under concurrent callers."
        },
        {
          "name": "Offer expiration",
          "description": "Deadline for converting an Offered entry into an accepted registration."
        },
        {
          "name": "Check-in direction",
          "description": "In, Out, or Void attendance input."
        },
        {
          "name": "Accepted / Denied / Duplicate / Voided",
          "description": "Server-derived result recorded for an attendance attempt."
        },
        {
          "name": "events:attendance:read",
          "description": "Attendance evidence only; it never grants ticket-code or QR credential access."
        },
        {
          "name": "events:attendance:write",
          "description": "Atomic check-in creation permission."
        },
        {
          "name": "Append-only",
          "description": "Original check-in cannot be edited or deleted; correction creates Void evidence."
        },
        {
          "name": "Offline check-in batch",
          "description": "One to 500 attempts under a device ID; HTTP 200 may contain accepted, denied, and error outcomes independently without credential or denial detail."
        },
        {
          "name": "client_scan_id",
          "description": "Stable 8–160 character scanner identity reused with the same device for retries of one physical attempt."
        },
        {
          "name": "Idempotency-Key",
          "description": "Top-level retry identity that prevents one single-scan or batch request from becoming duplicate writes."
        },
        {
          "name": "events:credentials:read",
          "description": "Lists or retrieves an operational event ticket credential."
        },
        {
          "name": "events:credentials:write",
          "description": "Issues, updates, or revokes a ticket credential; it is not an attendance permission."
        },
        {
          "name": "event_admission_not_accepted",
          "description": "Safe 409 returned after denied or duplicate evidence is committed; inspect authorized staff evidence separately for operational detail."
        },
        {
          "name": "Credential digest",
          "description": "One-way value included in offline scanner request identity so retries bind the credential without retaining the raw scan secret."
        },
        {
          "name": "Camera-first scanner",
          "description": "Registered-device QR capture with an encrypted offline queue and bounded server synchronization."
        },
        {
          "name": "Check readiness",
          "description": "Manager-only action that validates wallet signing inside the exact tenant data plane before a provider can be enabled."
        },
        {
          "name": "Google EventTicketClass ID",
          "description": "Full issuer-qualified class ID verified through the Google Wallet API and reused by generated save tokens."
        },
        {
          "name": "Wallet provider secrets",
          "description": "Tenant-project-only Apple certificate/key and Google issuer/service-account values; never client-readable or stored in delivery settings."
        },
        {
          "name": "PDF ticket",
          "description": "Branded on-demand document available without an external wallet provider."
        }
      ],
      "expectedResult": "Valid tickets reach only the authorized participant or household, waitlist offers follow the approved queue and capacity, and every entry, exit, denial, duplicate, or correction is represented by immutable attendance evidence.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "publish-event-feeds-calendar",
      "url": "https://platform.getcentri.com/centripos/publish-event-feeds-calendar",
      "title": "Publish a themed event feed and calendar links",
      "summary": "Place automatically updated event offerings on a website, provide branded detail and embed views, attach public media safely, and give attendees downloadable calendar entries without exposing the tenant database.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Publishing & calendar",
      "introduction": "Public event pages are bounded projections served through branded CentriPOS routes. Publishing a feed does not expose private event tables, purchaser records, participant records, registration answers, ticket credentials, capacity administration, or internal calendar entries.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Events → Publishing and create a feed with a durable slug and name. Choose Draft, Published, Paused, or Archived and Public, Unlisted, or Private visibility.",
        "Select which offerings appear, their order, and featured state. A feed can use explicit offering membership and supported filters; only offerings that are themselves publication-eligible should render publicly.",
        "Configure the feed theme, SEO fields, and supported embed settings. Review contrast, focus states, mobile layout, image alt text, long descriptions, sold-out states, registration windows, venue wording, and online/hybrid details.",
        "Use only the tenant-qualified branded route generated by CentriPOS: https://pos.getcentri.com/events/feed/{tenantId}/{feedSlug}, with /{eventSlug} for one offering. The published tenantId is a required routing boundary, not a credential; never substitute a Supabase hostname, project reference, storage path, or database URL.",
        "Use the generated event detail route for a single offering. The public slug is a publishing identifier, not an authorization token. Private offerings and nonpublic assets must fail closed even if someone guesses a slug.",
        "For an external website, use https://pos.getcentri.com/events/embed/{tenantId}/{feedSlug}, with optional /{eventSlug}. The twelve formal public GET operations are feed and offering JSON, feed- and offering-scoped occurrence pages, registration bootstrap, paged registration definition, paged physical-seat availability, agenda, feed and offering calendar downloads, and feed and offering rolling calendar subscriptions. Every route is tenant- and feed-qualified; there is no slug-only route. Configure supported layout and theme options, then test desktop and mobile widths.",
        "Use Public only for an external HTTPS asset safe for anonymous delivery. Retail API asset writes reject Supabase project and Storage origins. Managers may upload an Attendees or Staff native file up to 25 MiB; it remains private and is delivered to an authorized attendee through a branded five-minute capability URL with no bucket, object path, project URL, or Supabase hostname in JSON, HTML, logs, or webhooks.",
        "Confirm every occurrence has correct local time, IANA timezone, venue, status, and recurrence exception. Use Manage exceptions for one-date cancellations, reschedules, and modifications; public JSON includes only the sanitized event-facing exception fields.",
        "Offer Add to calendar or Download calendar from the public event or authorized portal page. The public feed ICS uses stable tenant-and-occurrence UIDs, timezone-aware dates, safe location and description fields, RRULE for a recurring series, EXDATE for cancelled instances, and RECURRENCE-ID override events for cancelled, rescheduled, or modified exceptions.",
        "Use the Google Calendar link when presented. Calendar downloads are snapshots; after a reschedule or cancellation, publish the updated schedule and notify attendees through the configured operational channel. Never use public ICS as a participant, registration, or meeting-credential export.",
        "Use the company Calendar to view canonical event occurrence entries beside projected deliveries, service visits, work, projects, external events, and custom entries. Public feed visibility and internal calendar visibility are separate settings.",
        "Before launch, test anonymous feed and detail requests, direct unlisted access, private-offering rejection, branded ready checkout, every non-ready checkout status, adult self and youth guardian registration, deferred group pass, sold-out capacity, cancelled/rescheduled recurrence exceptions, embed, public and attendee-only assets, mobile keyboard/screen-reader flow, and ICS import.",
        "The exact machine routes are GET /api/events/{tenant_id}/{feed_slug}/calendar.ics for a feed and GET /api/events/{tenant_id}/{feed_slug}/offerings/{event_slug}/calendar.ics for one offering.",
        "The feed and offering ICS routes share one bounded contract. A normal response is the complete file. If either export exceeds the occurrence, exception, or 8 MiB limit, 413 calendar_export_requires_pagination supplies first_page and page_size_maximum. Request page_size 1–500 and follow the opaque cursor, RFC 8288 Link rel=\"next\", X-CentriPOS-Next-Cursor, and X-CentriPOS-Calendar-Partial until complete.",
        "Choose Validate before Publish. Resolve every blocking IANA-timezone, missing or contradictory price, incomplete prose, inventory/capacity, unsafe or noncanonical URL, redirect, venue, registration window, recurrence, and lifecycle finding. Publish reruns the authoritative validation and fails closed if the record changed or any blocker remains.",
        "After publication, a transaction that changes the offering or a dependent venue, schedule, product or price, ticket, capacity, asset, purchase rule, access code, ticket preset, or seating record reruns the canonical validation at transaction completion. If the change would leave the live offering invalid, the entire transaction is rejected.",
        "Use /calendar-subscription.ics at feed or offering scope for Apple Calendar and webcal subscriptions. It always returns a bounded rolling attendee-safe window and refreshes at the same stable branded URL; use /calendar.ics for a complete snapshot or its documented paged export.",
        "The public list and detail pages expose List, Month, Week, Day, Map, Photo, and Summary views from one safe projection. Search and filter by event kind, reusable venue, date window, and admission state. Load more follows the opaque occurrence cursor when a large conference exceeds the initial discovery page.",
        "Feed-scoped occurrence pages are globally ordered by (starts_at, id) across every linked published offering, not concatenated one offering at a time. Follow the opaque cursor to continue that same deterministic order without skipping or repeating interleaved conference sessions.",
        "Public HTML includes canonical, Open Graph, Twitter, and schema.org Event, Offer, and Place metadata. Reusable venues provide structured address, coordinates or an approved map URL, public contact details, accessibility summary, and an enforced IANA timezone; an occurrence venue override wins for that dated session.",
        "Reserved-seat checkout starts with a compact safe seat summary and pages available seats through /registration-seats with ticket_option_id plus optional seating_config_id, section_id, search, cursor, and limit 1–250. Never fetch or render an unbounded venue layout in one browser response.",
        "Public and portal projection code recursively strips Supabase origins from URLs, HTML, nested objects, and arrays. Treat any leaked project hostname or Storage path as a privacy defect; never work around the branded boundary by rewriting it in website code."
      ],
      "controls": [
        {
          "name": "Publication feed",
          "description": "Themeable collection of eligible event offerings."
        },
        {
          "name": "Tenant-qualified feed route",
          "description": "Published tenantId and feedSlug together identify the public projection; neither value is a private credential."
        },
        {
          "name": "Public / Unlisted / Private",
          "description": "Discovery and access boundary for a feed or offering."
        },
        {
          "name": "Featured",
          "description": "Feed-specific merchandising flag for an offering."
        },
        {
          "name": "Theme",
          "description": "Supported colors, typography, spacing, and presentation tokens."
        },
        {
          "name": "SEO",
          "description": "Feed title, description, and supported indexing metadata."
        },
        {
          "name": "Embed settings",
          "description": "Bounded layout and website-placement options."
        },
        {
          "name": "Public asset",
          "description": "Explicitly approved offering or occurrence image, attachment, document, map, video, or download."
        },
        {
          "name": "checkout_status",
          "description": "Public ticket state: ready only after storefront, event_ticket, registration, sales-window, and capacity validation; every non-ready state fails closed."
        },
        {
          "name": "RRULE",
          "description": "Published normal cadence for a recurring series."
        },
        {
          "name": "EXDATE",
          "description": "Cancelled series instance omitted from normal expansion."
        },
        {
          "name": "RECURRENCE-ID",
          "description": "Exception component that identifies the original instance being cancelled, rescheduled, or modified."
        },
        {
          "name": "Master company calendar",
          "description": "Private operational calendar spanning events and other scheduled work."
        },
        {
          "name": "Branded route",
          "description": "Customer-facing URL beneath https://pos.getcentri.com; never an internal data origin."
        },
        {
          "name": "checkout_status",
          "description": "ready, storefront_unavailable, ticket_product_unavailable, registration_unavailable, or sold_out."
        },
        {
          "name": "Attendees asset",
          "description": "Attachment available only through registration-authorized portal access; never placed in an anonymous feed."
        },
        {
          "name": "Paged ICS",
          "description": "Bounded page_size/cursor export used when either a feed or offering calendar would exceed the public safety limits."
        },
        {
          "name": "Offering calendar ICS",
          "description": "GET /api/events/{tenantId}/{feedSlug}/offerings/{eventSlug}/calendar.ics; the attendee-safe schedule for one published offering."
        },
        {
          "name": "Validate before Publish",
          "description": "Server-authored blocking and advisory findings; publishing repeats the check and cannot be bypassed by browser state."
        },
        {
          "name": "Rolling calendar subscription",
          "description": "Stable /calendar-subscription.ics URL for Apple Calendar or webcal clients; bounded to a rolling safe window instead of returning a pagination error."
        },
        {
          "name": "Occurrence page",
          "description": "Feed- or offering-scoped public continuation page used by giant conference discovery views."
        },
        {
          "name": "registration-seats",
          "description": "Anonymous-safe, ticket-scoped available-seat page with opaque continuation and bounded filters."
        },
        {
          "name": "Structured venue",
          "description": "Reusable Place identity with structured postal address, map data, accessibility summary, public contacts, and an IANA timezone."
        },
        {
          "name": "Discovery views",
          "description": "List, Month, Week, Day, Map, Photo, and Summary presentations of the same filtered public data."
        },
        {
          "name": "Recursive origin scrub",
          "description": "Fail-closed removal of Supabase project and Storage origins from every public or portal projection depth."
        }
      ],
      "expectedResult": "The published branded feed, event detail, embed, approved public assets, registration state, recurrence exceptions, and calendar download agree while private participant, ticket, registration-answer, and internal calendar data remain inaccessible anonymously.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "event-portal-privacy",
      "url": "https://platform.getcentri.com/centripos/event-portal-privacy",
      "title": "Protect guardian, camper, and attendee information in the portal",
      "summary": "Show the right household or attendee their registered event, approved schedule, tickets, instructions, and public files while keeping participant, medical, emergency, waiver, and pickup information out of unrelated contact links.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Portal & privacy",
      "introduction": "A registration may appear in the client portal only through an authorized customer or registration relationship and configured portal settings. A normal contact portal link is not automatic permission to reveal every participant record connected through a household.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Decide which customer owns portal access for the registration: normally the purchaser or an explicitly authorized guardian customer. Confirm the contact identity and household association before enabling event registration content.",
        "Keep the attendee or camper as a separate reusable participant. Link the participant to the guardian customer where appropriate; do not merge a child into the purchaser profile to make a portal query easier.",
        "Configure offering and ticket portal settings for the minimum useful view: offering name, occurrence schedule, venue or meeting instructions, registration number and status, participant display name, approved tickets, calendar action, and public attachments.",
        "Do not expose birth date, medical details, diagnosis, allergies, medication, emergency contact, authorized pickup, waiver/signature evidence, school or student identifiers, accessibility notes, raw form answers, ticket credential hashes, internal notes, or staff fields in a general portal response.",
        "Show registration-form and waiver status only through the safe completion projection: an overall completion summary and per-requirement Complete, Incomplete, or Not required state. Never include an answer value, signature, waiver document, credential, or protected form payload in the portal completion response.",
        "When more than one guardian is associated, use explicit authorization rather than household inference alone. A purchaser, guardian, attendee, pickup contact, and emergency contact are different roles and must not be treated as interchangeable.",
        "Give each sibling or attendee their own participant identity and registration links. The portal may group registrations for presentation while reporting and access checks continue to preserve the individual record.",
        "For online or hybrid events, reveal meeting URLs only to the authorized attendee or household at the intended lifecycle point. Keep them out of public feeds and search indexing unless the business deliberately publishes an open meeting.",
        "Show Public assets plus Attendees assets only for a registration this portal identity is authorized to view. Staff assets never enter the customer portal. Private forms and signed documents use a separately authorized flow with appropriate retention and download auditing.",
        "On cancellation, transfer, ticket revocation, or guardian change, re-evaluate portal access immediately. A previously delivered calendar file or downloaded attachment cannot be remotely recalled, so avoid putting unnecessary private data in either.",
        "Test with the purchaser, an authorized guardian, an unrelated customer, a sibling household, a staff user, and an expired or revoked portal session. Each identity should receive only its permitted registration projection.",
        "For an adult self-attendee, the verified purchaser and participant can share one customer identity. Portal access follows that customer relationship without inventing a household or guardian link.",
        "Return Attendees assets only after the portal resolves a view-authorized registration. Do not send event tabs or registration files through a generic contact portal when the customer has no purchaser, participant, or explicitly authorized guardian relationship to that registration.",
        "Page registrations beyond the first result set with before_registered_at and before_registration_id together; the default is 25 and maximum is 100. Never send a timestamp cursor without its ID tie-breaker.",
        "Page each registration child resource independently with limit and after_id, at most 100 per page. The exact resources are participants, tickets, agenda, schedule, assets, requirements, assignment_forms, assignment_questions, assignment_waivers, assignment_groups, assignment_group_occurrences, and assignment_sessions. The assignment-definition limits are 4 forms, 10 questions, 1 waiver, 100 groups, 100 group occurrences, and 50 sessions per page.",
        "Use the token-scoped assign_event_registration_seat POST only for purchaser_self or new_participant. The body is limited to 256 KiB and carries registration_id, optional ticket_id, expected_version, idempotency_key, identity, and bounded answers, waivers, and concrete occurrence selections. A successful assignment promotes exactly one pending seat to an active participant-bound ticket while remaining seats stay pending.",
        "Portal ticket history exposes ticket_code and a QR only when the ticket is participant-bound, unexpired, and Valid or Used. Pending assignment, Voided, Transferred, and Expired rows return ticket_code null, credential_active false, and viewer_authorized false.",
        "A manager-native Attendees asset is limited to 25 MiB and delivered only through /account-portal-event-asset/<capability>/<assetId>. The branded capability expires after five minutes and the portal response never contains the event-assets bucket, object path, Supabase hostname, or project URL.",
        "Privacy-filtered child pages advance their keyset cursor even when every row on that page is hidden and visible data is empty. Continue until has_more is false; do not retry the same cursor or infer that an empty visible page is the end.",
        "Unexpected portal and public-quote failures return a generic safe error. Use the request correlation ID for support; never expose internal table, Storage, project, stack, or validation detail to the customer."
      ],
      "controls": [
        {
          "name": "Portal owner",
          "description": "Customer identity authorized to view the registration in the client portal."
        },
        {
          "name": "Participant",
          "description": "Reusable attendee or camper identity separate from the portal customer."
        },
        {
          "name": "Guardian association",
          "description": "Relationship between participant and responsible customer; not alone proof of every portal permission."
        },
        {
          "name": "Registration projection",
          "description": "Minimum portal-safe offering, schedule, status, ticket, and instruction fields."
        },
        {
          "name": "Sensitive answer",
          "description": "Medical, emergency, waiver, pickup, birth, school, or comparable private form content."
        },
        {
          "name": "Form and waiver completion",
          "description": "Aggregate and per-requirement status only; it is not an answer, signature, or document payload."
        },
        {
          "name": "Meeting URL",
          "description": "Attendee-only join information unless intentionally public."
        },
        {
          "name": "Public attachment",
          "description": "Asset explicitly approved for customer access."
        },
        {
          "name": "Ticket credential",
          "description": "Admission secret that must be delivered only to the authorized attendee or household."
        },
        {
          "name": "Transfer / revocation",
          "description": "Lifecycle change requiring access and ticket re-evaluation."
        },
        {
          "name": "Unrelated contact portal",
          "description": "Must not receive event registration details merely because the contact exists in the same tenant."
        },
        {
          "name": "Adult self-attendee",
          "description": "Purchaser and attendee share one verified customer identity, with no self-guardian relationship."
        },
        {
          "name": "Attendees asset",
          "description": "Registration-authorized portal file excluded from the anonymous feed and unrelated customer portals."
        },
        {
          "name": "Registration cursor",
          "description": "Atomic before_registered_at plus before_registration_id pair; default 25, maximum 100."
        },
        {
          "name": "Child resource page",
          "description": "Independent limit/after_id keyset page, maximum 100, with resource-specific assignment-definition limits."
        },
        {
          "name": "Portal seat assignment",
          "description": "Token POST supporting purchaser_self or new_participant only, expected version, idempotency, answers, waivers, and concrete selections within 256 KiB."
        },
        {
          "name": "credential_active",
          "description": "True only for a participant-bound, unexpired Valid or Used ticket; every other lifecycle row is QR-inactive."
        },
        {
          "name": "Five-minute asset URL",
          "description": "Branded capability route for authorized native attendee files; never a reusable Storage URL."
        },
        {
          "name": "Generic customer error",
          "description": "Fail-closed portal or quote response with a safe message and correlation ID, not internal diagnostics."
        }
      ],
      "expectedResult": "Only an explicitly authorized purchaser, guardian, or attendee sees the minimum approved registration projection, while unrelated contacts and public routes cannot retrieve child, medical, emergency, waiver, pickup, credential, or private-answer data.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "event-reports",
      "url": "https://platform.getcentri.com/centripos/event-reports",
      "title": "Report on event sales, participants, merchandise, and attendance",
      "summary": "Analyze offerings from revenue and units down to ticket choices, half-day or full-day demand, repeat campers, household purchasers, T-shirts, take-home robots, capacity, waitlists, and attendance.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Event reporting",
      "introduction": "Choose the counting unit before interpreting a number. Receipts, ticket-product units, registration records, seats, unique participants, purchaser households, issued tickets, check-ins, and merchandise units are related but not interchangeable.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Events → Reports and set the business timezone, date basis, offering, occurrence, event kind, delivery format, status, ticket option, location, and other required filters.",
        "Use receipt or sale date for recognized sales activity, registration date for enrollment conversion, occurrence date for scheduled attendance, and check-in time for operational attendance. Label exports with the chosen date basis.",
        "Read ticket revenue from the linked event_ticket receipt lines and reconcile registration amount totals, discounts, taxes, refunds, cancellations, and transferred registrations to their source sales. A registration status change alone does not move cash.",
        "Read ticket units and seats separately. One full-day product unit may grant one attendee access to two occurrences; a family or group option may create several seats from one ticket unit.",
        "Compare morning, afternoon, and full-day ticket options, then inspect each shared capacity pool. Full-day seats should consume both half-day pools, so adding option counts without understanding allocations can double-count attendees or available seats.",
        "Track capacity, confirmed seats, remaining units, overbook use, waitlist size, offers, acceptances, expirations, and sold-out or reopened periods by offering and occurrence.",
        "Measure unique participants and repeat participants from reusable participant identities. Measure purchaser households from purchaser customers. A returning guardian with a new camper and a returning camper purchased by another guardian are different retention stories.",
        "Analyze attendance as accepted check-ins, unique attendees, check-outs, denied scans, duplicates, void corrections, no-shows, and completion. Check-in rows are append-only evidence, so use the effective result rather than deleting exceptions from the denominator.",
        "Report optional merchandise from its own receipt product lines. Use normal product category, SKU, variant, quantity, price, discount, tax, cost, and inventory fields to answer how many T-shirts, sizes, kits, lunches, or take-home robots were sold.",
        "When merchandise was intentionally included at no extra charge, use an explicit zero-dollar receipt line only if that is the documented fulfillment and unit-tracking design. Keep its quantity out of admission revenue while retaining unit reporting; do not add unrequested merchandise to historical receipts.",
        "Break down by offering, occurrence, session kind, ticket option, product, category, participant type, purchaser or household, new versus repeat, registration source, location, age band where authorized, and attendance outcome.",
        "Export only the minimum columns needed. Exclude medical, emergency, waiver, pickup, exact birth date, ticket credentials, and private answers from routine reporting. Use aggregated age bands or operational flags when they answer the question.",
        "Reconcile a sample from report row to registration, participant, ticket option, receipt line, payment, capacity allocation, ticket, and check-in before distributing the result.",
        "Use the Event reports view or the documented event-report API resource for the privacy-safe reporting slices: financial summary, add-on product and variant units, participant and repeat segments, occurrence selections and attendance, tracks, stakeholders, and allowlisted standard answer dimensions. Protected answers and ticket codes are excluded.",
        "For giant conferences, page or export the full result rather than treating the screen’s first 100 session rows as the complete dataset. Preserve report_key, product_id and variant_id, occurrence_id and occurrence_instance_id, participant identity, receipt line, and lifecycle status as separate join dimensions."
      ],
      "controls": [
        {
          "name": "Date basis",
          "description": "Sale, registration, occurrence, or attendance timestamp used for the report period."
        },
        {
          "name": "Ticket revenue",
          "description": "Net sales from linked event_ticket receipt lines after applicable discounts, returns, and refunds."
        },
        {
          "name": "Ticket units",
          "description": "Catalog product quantity sold."
        },
        {
          "name": "Registered seats",
          "description": "Seat count represented by registrations; may differ from ticket units."
        },
        {
          "name": "Unique participants",
          "description": "Distinct attendee identities in the selected scope."
        },
        {
          "name": "Purchaser households",
          "description": "Distinct customers who managed the transaction."
        },
        {
          "name": "Repeat participant",
          "description": "Participant with qualifying prior registration history."
        },
        {
          "name": "Capacity consumed",
          "description": "Units applied to every linked pool, not simply ticket quantity."
        },
        {
          "name": "Attendance",
          "description": "Effective accepted entry and related exit/correction evidence."
        },
        {
          "name": "No-show",
          "description": "Confirmed expected participant without qualifying attendance under the business rule."
        },
        {
          "name": "Merchandise units",
          "description": "Separate receipt-line quantities for shirts, robots, kits, meals, or other products."
        },
        {
          "name": "Zero-dollar line",
          "description": "Unit-tracking line with no admission revenue; use only when the merchandise is truly included and intended."
        },
        {
          "name": "Privacy-safe export",
          "description": "Report that omits sensitive participant and credential fields not needed for analysis."
        },
        {
          "name": "Reporting slices",
          "description": "Server-shaped financial, merchandise, participant, lifecycle, session, track, stakeholder, and allowlisted-answer datasets."
        },
        {
          "name": "report_key",
          "description": "Stable dimension key for an approved standard registration question; not permission to expose sensitive answers."
        }
      ],
      "expectedResult": "The selected filters reconcile from aggregate to offering, occurrence, ticket product, registration, participant, purchaser, receipt line, capacity allocation, merchandise line, and append-only attendance evidence without mixing counting units or exporting sensitive fields.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "highlevel-event-workflows",
      "url": "https://platform.getcentri.com/centripos/highlevel-event-workflows",
      "title": "Connect event activity to HighLevel workflows",
      "summary": "Use CentriPOS event triggers and actions to coordinate appropriate CRM automation while keeping ticketing, capacity, attendance, child records, and sensitive registration data authoritative in CentriPOS.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "HighLevel automation",
      "introduction": "HighLevel is valuable for messaging and workflow orchestration, but it is not the system of record for event capacity, registration answers, ticket credentials, attendance evidence, or protected camper information. Connections resolve through the authorized CentriCRM location and tenant integration.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open the CentriCRM or HighLevel integration for the selected business and confirm the exact HighLevel location. Do not reuse a fixed-location token or workflow subscription across unrelated CentriPOS tenants.",
        "Before configuring a trigger or action, verify that HighLevel Marketplace registration, review, OAuth/location mapping, CentriPOS tenant entitlement, and per-location activation have actually completed. These are external controlled gates; code, documentation, or an internal schema does not prove activation, so keep the workflow disabled while any gate is pending.",
        "Only after every external activation gate is verified, create an event trigger subscription through the approved CentriPOS HighLevel workflow integration. Choose only supported event types and use an exact LeadConnector workflow trigger target generated by HighLevel.",
        "Select a privacy projection appropriate to the workflow. Normal projections remove sensitive participant fields; Sensitive projections still allow only the operational allowlist; Restricted projections fully redact business payload fields.",
        "Use offering triggers for created, updated, published, and cancelled changes; occurrence triggers for created, updated, rescheduled, cancelled, or capacity changes; registration triggers for created, updated, confirmed, cancelled, transferred, or waitlisted changes; and participant triggers for created, updated, guardian linked, or guardian updated changes.",
        "Use ticket, attendance, form, waiver, waitlist, capacity, and calendar triggers only for the workflow that genuinely needs them. Supported operational triggers include ticket issued or revoked, attendee checked in or out, registration form completed, waiver signed, waitlist offer created or accepted, threshold reached, sold out, reopened, and calendar entry lifecycle changes.",
        "Design the HighLevel workflow to deduplicate the CentriPOS event ID. Delivery can retry, and the same immutable event can legitimately arrive more than once. Preserve the event time and safe record URL for support correlation.",
        "Use only the 29 registered HighLevel actions. Registration upsert creates or updates Pending only; confirmation is a separate authoritative action. Waitlist upsert writes Waiting or Cancelled only; Offer next and Accept are separate atomic actions. Venue, ticket-preset, publication, purchase-rule, scanner, seating-layout, seating-configuration, physical-seat-hold, and event receipt payment-plan actions call bounded authoritative commands. Each action resolves tenant context from the connected HighLevel location and uses its own idempotency key.",
        "Treat action success as a CentriPOS result, not as a payment authorization or legal consent. A registration action cannot fabricate a paid receipt, bypass capacity, silently accept a waiver, or expose a meeting credential outside its authorized lifecycle.",
        "Never map medical, diagnosis, allergy, medication, emergency contact, authorized pickup, guardian authorization, waiver signature, birth date, school or student ID, social-security, password, secret, token, raw form-answer, or credential fields into general HighLevel contact custom fields.",
        "Use CentriPOS contact and participant references to prevent duplicate HighLevel contacts. A guardian may be an appropriate CRM contact; a camper may remain only a protected CentriPOS participant unless the business has a lawful, explicit reason and approved workflow for a separate CRM record.",
        "Monitor subscription status, delivery attempts, retries, and dead letters. CentriPOS uses bounded exponential retries and stops after the supported attempt limit; correct the receiver before replaying.",
        "Test each trigger and action in an isolated preview context with synthetic records. Verify wrong-location rejection, missing-scope rejection, sensitive-field stripping, idempotent retry, capacity enforcement, status transitions, and audit correlation before enabling customer communications.",
        "The exact 96-trigger vocabulary is event.created, event.updated, event.published, event.cancelled; event_occurrence.created, event_occurrence.updated, event_occurrence.rescheduled, event_occurrence.cancelled, event_occurrence.capacity_changed; registration.created, registration.updated, registration.confirmed, registration.cancelled, registration.transferred, registration.waitlisted; participant.created, participant.updated, participant.guardian_linked, participant.guardian_updated; waitlist.offer_created, waitlist.offer_accepted; ticket.issued, ticket.updated, ticket.revoked; attendee.checked_in, attendee.checked_out; registration_form.completed; waiver.signed; capacity.threshold_reached, capacity.sold_out, capacity.reopened; calendar.entry.created, calendar.entry.updated, calendar.entry.cancelled; venue.created, venue.updated, venue.archived; ticket_preset.created, ticket_preset.updated, ticket_preset.archived; purchase_rule.created, purchase_rule.updated, purchase_rule.archived; scanner.device_registered, scanner.device_updated, scanner.device_retired, scanner.batch_synchronized; ticket.delivery_configuration.updated; ticket.artifact_ready, ticket.artifact_failed, ticket.artifact_revoked, ticket.artifact_updated; seating.layout.created, seating.layout.updated, seating.layout.published, seating.layout.archived; seating.configuration.created, seating.configuration.updated, seating.configuration.on_sale, seating.configuration.archived; seating.hold.created, seating.hold.updated, seating.hold.released, seating.hold.expired, seating.hold.converted; seating.assignment.created, seating.assignment.updated, seating.assignment.released, seating.assignment.transferred; seating.seat.blocked, seating.seat.unblocked; access_code_set.created, access_code_set.updated, access_code_set.archived; access_code.created, access_code.updated, access_code.revoked; access_code.reservation_created, access_code.reservation_updated, access_code.reservation_confirmed, access_code.reservation_expired, access_code.reservation_released; seating.intent_seat_held, seating.intent_seat_updated, seating.intent_seat_assigned, seating.intent_seat_released; event_payment_plan_policy.created, event_payment_plan_policy.updated, event_payment_plan_policy.archived; event_registration_payment_plan.activated, event_registration_payment_plan.paused, event_registration_payment_plan.resumed, event_registration_payment_plan.delinquent, event_registration_payment_plan.completed, event_registration_payment_plan.canceled, and event_registration_payment_plan.admission_reinstated.",
        "The exact 29 action keys are centripos_event_upsert, centripos_occurrence_upsert, centripos_registration_upsert, centripos_registration_confirm, centripos_participant_upsert, centripos_guardian_link_upsert, centripos_registration_cancel_or_transfer, centripos_waitlist_upsert, centripos_waitlist_offer_next, centripos_waitlist_accept, centripos_ticket_issue_or_revoke, centripos_attendance_record, centripos_calendar_entry_upsert, centripos_venue_upsert, centripos_ticket_preset_upsert, centripos_event_validate_or_publish, centripos_purchase_rules_save, centripos_scanner_device_register, centripos_seating_layout_publish, centripos_seating_configuration_upsert, centripos_seat_hold, centripos_seat_hold_release, centripos_seat_hold_confirm, centripos_receipt_payment_plan_create, centripos_receipt_payment_plan_pause, centripos_receipt_payment_plan_resume, centripos_receipt_payment_plan_cancel, centripos_receipt_payment_plan_send_customer_link, and centripos_receipt_payment_plan_reinstate_admission. Payment-plan lifecycle actions call the receipt/invoice plan authority; there is no mark-paid action. Do not substitute a generic table update for an authoritative lifecycle command.",
        "Venue, ticket-preset, purchase-rule, scanner, ticket-delivery, artifact, seating, access-code, reservation, and registration-intent seat triggers use the same tenant resolution, immutable event identity, delivery retry, privacy projection, and branded record-link rules as the original event vocabulary. HighLevel access-code triggers include lifecycle metadata only; raw codes, code_hash, and even the masked hint remain outside the CRM payload boundary.",
        "The new HighLevel actions remain deliberately narrower than the Retail API. centripos_event_validate_or_publish validates or publishes through the database lifecycle; centripos_purchase_rules_save replaces one bounded rule graph; centripos_seating_layout_publish and centripos_seating_configuration_upsert preserve layout/configuration state; and centripos_seat_hold, centripos_seat_hold_release, and centripos_seat_hold_confirm use authoritative seat-inventory commands. There is intentionally no HighLevel action that transports or creates a raw access code.",
        "Event payment-plan workflow triggers carry the same safe lifecycle projection as signed delivery and never carry card, vault, payment-link, medical, waiver, or answer data. centripos_receipt_payment_plan_create creates the event receipt plan through the existing invoice-plan authority; pause, resume, and cancel call the existing receipt-plan lifecycle. send_customer_link returns the actual canonical expires_at: its requested lifetime applies only when a new receipt token is created, and a reused live token keeps its existing expiry. Its scheduled amount is only a prefill on the ordinary receipt page, where the customer may pay that amount, the full balance, or another valid partial amount. centripos_receipt_payment_plan_reinstate_admission requires payment_plan_id and a 1–1000 character reason, requires the authoritative completed receipt balance to be zero, atomically rechecks live registration, daypart/session, and physical-seat capacity, and returns safe registrations_reinstated, occurrence_enrollments_reinstated, seats_reinstated, and tickets_issued counts. No HighLevel action marks an installment or receipt paid.",
        "An outbound trigger target is accepted only at https://services.leadconnectorhq.com/workflows-marketplace/triggers/execute/{trigger}/{location} with no user info, port, query, or fragment. A subscription may define at most 32 normalized filters against the already-projected payload; each filter list has at most 100 scalar values, so filtering cannot recover a redacted field.",
        "Each encoded HighLevel workflow payload is capped at 256 KiB. Delivery makes at most eight total attempts, starts with a 30-second exponential delay capped at six hours, and retries only network failures, 408, 409, 425, 429, or 5xx responses. Delivered, dead-lettered, and suppressed are terminal; reuse the immutable event ID and subscription identity for deduplication.",
        "HighLevel Marketplace registration, action/trigger definition publication, OAuth/location mapping, reviewer approval, and customer-workflow activation remain external controlled gates. Keep production workflows disabled until that app is approved and the target CentriPOS tenant is entitled; never interpret deployed code or documentation as Marketplace activation."
      ],
      "controls": [
        {
          "name": "HighLevel location",
          "description": "External account context mapped to exactly one authorized CentriPOS tenant integration."
        },
        {
          "name": "Manual marketplace activation",
          "description": "Platform-controlled publication of CentriPOS trigger and action definitions in HighLevel; not implied by application code."
        },
        {
          "name": "Tenant entitlement",
          "description": "Explicit CentriPOS authorization for this business to use the event workflow contract; documentation alone is not entitlement."
        },
        {
          "name": "Trigger subscription",
          "description": "Approved event-type and LeadConnector workflow target relationship."
        },
        {
          "name": "Privacy projection",
          "description": "Normal, sensitive allowlist, or fully restricted outbound field boundary."
        },
        {
          "name": "Immutable event ID",
          "description": "Deduplication key that remains the same across delivery retries."
        },
        {
          "name": "Record URL",
          "description": "Branded safe link or API resource reference used for correlation."
        },
        {
          "name": "Offering/occurrence trigger",
          "description": "Workflow event about program content or schedule state."
        },
        {
          "name": "Registration trigger",
          "description": "Workflow event about enrollment lifecycle."
        },
        {
          "name": "Capacity trigger",
          "description": "Threshold, sold-out, reopened, or capacity-change signal."
        },
        {
          "name": "CentriPOS action",
          "description": "HighLevel-initiated upsert or lifecycle command validated by the tenant system of record."
        },
        {
          "name": "Idempotency key",
          "description": "Caller-supplied retry identity preventing duplicate action writes."
        },
        {
          "name": "Sensitive-field stripping",
          "description": "Removal of child, medical, emergency, waiver, credential, and secret data before delivery."
        },
        {
          "name": "event.created · event.updated · event.published · event.cancelled",
          "description": "Offering lifecycle triggers available to HighLevel workflows."
        },
        {
          "name": "event_occurrence.created · event_occurrence.updated · event_occurrence.rescheduled · event_occurrence.cancelled",
          "description": "Occurrence lifecycle triggers available to HighLevel workflows."
        },
        {
          "name": "event_occurrence.capacity_changed",
          "description": "Occurrence capacity-change trigger."
        },
        {
          "name": "registration.created · registration.updated · registration.confirmed",
          "description": "Registration creation, general update, and confirmation triggers."
        },
        {
          "name": "registration.cancelled · registration.transferred · registration.waitlisted",
          "description": "Registration cancellation, transfer, and waitlist triggers."
        },
        {
          "name": "participant.created · participant.updated",
          "description": "Participant lifecycle triggers with protected-field projection."
        },
        {
          "name": "participant.guardian_linked · participant.guardian_updated",
          "description": "Explicit guardian relationship and portal-authorization lifecycle triggers."
        },
        {
          "name": "waitlist.offer_created · waitlist.offer_accepted",
          "description": "Waitlist offer lifecycle triggers."
        },
        {
          "name": "ticket.issued · ticket.updated · ticket.revoked",
          "description": "Ticket credential lifecycle triggers without delivering credential secrets."
        },
        {
          "name": "attendee.checked_in · attendee.checked_out",
          "description": "Attendance triggers from accepted operational evidence."
        },
        {
          "name": "registration_form.completed · waiver.signed",
          "description": "Completion signals; payload privacy still strips protected answers and signatures."
        },
        {
          "name": "capacity.threshold_reached · capacity.sold_out · capacity.reopened",
          "description": "Capacity automation triggers."
        },
        {
          "name": "calendar.entry.created · calendar.entry.updated · calendar.entry.cancelled",
          "description": "Master calendar lifecycle triggers."
        },
        {
          "name": "centripos_event_upsert",
          "description": "HighLevel action that creates or updates a CentriPOS offering."
        },
        {
          "name": "centripos_occurrence_upsert",
          "description": "HighLevel action that creates or updates an occurrence."
        },
        {
          "name": "centripos_participant_upsert",
          "description": "HighLevel action that creates or updates an event participant under the native privacy boundary."
        },
        {
          "name": "centripos_guardian_link_upsert",
          "description": "HighLevel action that explicitly links or updates a Parent/Guardian relationship and portal authorization."
        },
        {
          "name": "centripos_registration_upsert",
          "description": "Creates or updates only a Pending registration; it cannot confirm, cancel, transfer, or fabricate payment."
        },
        {
          "name": "centripos_registration_cancel_or_transfer",
          "description": "HighLevel action for an authorized cancellation or transfer."
        },
        {
          "name": "centripos_waitlist_upsert",
          "description": "Creates or updates only Waiting or Cancelled queue state; offer and acceptance are separate commands."
        },
        {
          "name": "centripos_ticket_issue_or_revoke",
          "description": "HighLevel action that issues or revokes a ticket under CentriPOS rules."
        },
        {
          "name": "centripos_attendance_record",
          "description": "HighLevel action that appends check-in, check-out, or correction evidence."
        },
        {
          "name": "centripos_calendar_entry_upsert",
          "description": "HighLevel action that creates or updates a canonical calendar entry."
        },
        {
          "name": "Dead letter",
          "description": "Delivery stopped after the supported retry limit and requiring review."
        },
        {
          "name": "Marketplace gate",
          "description": "External registration, review, approval, and per-location activation required before customer workflows may use these contracts."
        },
        {
          "name": "Authoritative action",
          "description": "Tenant-resolved idempotent lifecycle command; never an unrestricted direct-table mutation."
        },
        {
          "name": "HighLevel delivery boundary",
          "description": "256 KiB projected payload, eight total attempts, and a fixed LeadConnector marketplace-trigger target shape."
        },
        {
          "name": "Workflow filter",
          "description": "One of at most 32 conditions applied only after privacy projection; it cannot address fields that CentriPOS removed."
        },
        {
          "name": "centripos_registration_confirm",
          "description": "Confirms a Pending registration through confirm_event_registration; it is separate from pending-only upsert."
        },
        {
          "name": "centripos_waitlist_offer_next",
          "description": "Atomically offers the next capacity-eligible Waiting entry through offer_next_event_waitlist_entry_from_workflow."
        },
        {
          "name": "centripos_waitlist_accept",
          "description": "Accepts one active offer through accept_event_waitlist_offer_from_workflow and returns its registration lifecycle result."
        },
        {
          "name": "centripos_venue_upsert / centripos_ticket_preset_upsert",
          "description": "Bounded idempotent configuration upserts through the event-platform workflow command."
        },
        {
          "name": "centripos_event_validate_or_publish",
          "description": "Runs publish validation or the authoritative publication transition; it cannot bypass blocking issues."
        },
        {
          "name": "centripos_purchase_rules_save",
          "description": "Replaces one bounded visual purchase-rule graph and leaves checkout authorization to server evaluation."
        },
        {
          "name": "centripos_scanner_device_register",
          "description": "Registers one tenant scanner device through the authoritative device command."
        },
        {
          "name": "centripos_seating_layout_publish / centripos_seating_configuration_upsert",
          "description": "Publishes a valid reusable layout or upserts one occurrence seating configuration."
        },
        {
          "name": "centripos_seat_hold / release / confirm",
          "description": "Creates, releases, or converts physical-seat holds through the server inventory lifecycle; the hold key input is a digest, never a raw session secret."
        },
        {
          "name": "Access-code workflow boundary",
          "description": "HighLevel triggers expose safe lifecycle metadata without raw code, code_hash, or code_hint. No HighLevel action creates an access code."
        },
        {
          "name": "Event receipt payment-plan actions",
          "description": "Create, pause, resume, cancel, generate a customer link, or reinstate paid-in-full admission through the existing receipt/invoice-plan authority; no mark-paid shortcut exists."
        },
        {
          "name": "centripos_receipt_payment_plan_reinstate_admission",
          "description": "Requires payment_plan_id plus a nonblank 1–1000 character reason; current receipt balance must be zero, live capacity is rechecked, and safe restored-registration and ticket counts are returned."
        }
      ],
      "expectedResult": "Each enabled HighLevel trigger arrives once logically despite retries with the correct tenant and privacy projection, and every supported action is tenant-resolved, scope-checked, idempotent, capacity-safe, lifecycle-valid, and auditable in CentriPOS.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "slug": "master-company-calendar",
      "url": "https://platform.getcentri.com/centripos/master-company-calendar",
      "title": "Use the master company calendar",
      "summary": "Review event occurrences beside deliveries, service appointments, and other dated work in one month or agenda view, then export only the currently visible commitments as an iCalendar file.",
      "collection": {
        "id": "events",
        "title": "Events & scheduled offerings"
      },
      "section": "Master calendar",
      "introduction": "Events → Master calendar is a unified operating view. It does not merge unrelated resource records or replace their authoritative workflows: event capacity stays with offerings, delivery status stays with fulfillment, and service status stays with Service Center.",
      "beforeYouBegin": "Confirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.",
      "steps": [
        "Open Events → Master calendar and confirm the selected business. The calendar is tenant-bound; switching businesses changes every visible commitment.",
        "Use the previous-month and next-month arrows to move one month at a time. Choose Today to return the calendar to the current month. Read the displayed month and the business timezone before interpreting dates near midnight or daylight-saving changes.",
        "Choose Month for the grid or Agenda for a chronological list. On smaller screens, the month view presents the visible commitments as a list rather than compressing an unreadable seven-column grid.",
        "Under Show, toggle Events, Deliveries, Service, and Other. The commitments-this-month count follows the visible source kinds. A hidden kind is filtered from the view; it is not deleted or cancelled.",
        "Read each entry's title, start and end, source badge, supporting subtitle, and status. Choose or open the source record through the supported product workflow when a schedule, address, assignee, capacity, or lifecycle value needs to change.",
        "For an event occurrence, edit the normal schedule through its offering. Use Manage exceptions for one-date cancellation, reschedule, or modification. Use staged reconcile-series for a broad recurrence rewrite so concrete instances, attendee calendars, capacity, publication, and webhooks preserve stable identity.",
        "For a delivery, change the promised schedule and status through Sales → Fulfillment Center. For service work, use the Service Center visit or appointment. Do not create a custom calendar entry to mask an incorrect source record.",
        "Use custom or external calendar entries only for dated commitments that do not already have an authoritative CentriPOS source. Choose the correct source type, visibility, timezone, status, organizer, attendee notification, and sync state.",
        "Treat visibility separately from source access. Public, Attendees, Staff, Internal, and Private describe calendar exposure, but a viewer still needs authorization to reach the underlying customer, participant, delivery, service, or event record.",
        "Choose Export .ics to download the entries currently included by the source-kind filters. The file includes safe calendar fields and stable identifiers; verify it before sharing because an internal company export can contain operational titles and timing.",
        "After a reschedule or cancellation, confirm the source version and calendar entry version advance and the new status is visible. External calendar sync can report Local, Pending, Synced, Failed, or Conflict; an exported file is not proof a connected calendar accepted an update.",
        "For a reporting or audit question, use the resource-specific report and source record. The calendar proves scheduled placement and current displayed state, not payment, delivery completion, service completion, participant consent, or attendance by itself.",
        "Calendar projections are maintained from authoritative event occurrences and instances, receipt-level deliveries, service visits and tickets, work and projects, plus deliberate custom/external entries. Large historical projection backfills run as bounded resumable batches rather than one unbounded request.",
        "Each delivery receipt contributes one customer-facing delivery calendar row. Internal route execution may add distinct delivery_operational_stop rows, which must not be counted as additional customer deliveries or emitted through the ordinary delivery webhook vocabulary."
      ],
      "controls": [
        {
          "name": "Previous / next",
          "description": "Moves the displayed calendar one month backward or forward."
        },
        {
          "name": "Today",
          "description": "Returns the displayed month to the current date."
        },
        {
          "name": "Month",
          "description": "Seven-day grid on larger screens and a readable list adaptation on smaller screens."
        },
        {
          "name": "Agenda",
          "description": "Chronological list of visible commitments."
        },
        {
          "name": "Show: Events",
          "description": "Includes event occurrence calendar entries."
        },
        {
          "name": "Show: Deliveries",
          "description": "Includes delivery commitments projected from fulfillment."
        },
        {
          "name": "Show: Service",
          "description": "Includes service visit or service-appointment commitments."
        },
        {
          "name": "Show: Other",
          "description": "Includes supported work, project, staff, external, or custom entries."
        },
        {
          "name": "Commitments this month",
          "description": "Count of entries in the displayed month after source-kind filtering."
        },
        {
          "name": "Source record",
          "description": "Authoritative event, delivery, service, work, project, staff, external, or custom record behind the entry."
        },
        {
          "name": "Visibility",
          "description": "Public, attendees, staff, internal, or private calendar exposure classification."
        },
        {
          "name": "Sync status",
          "description": "Local, pending, synced, failed, or conflict state for external calendar coordination."
        },
        {
          "name": "Export .ics",
          "description": "Downloads the currently visible calendar set; it does not create a live subscription or prove external import."
        },
        {
          "name": "delivery",
          "description": "One receipt-level customer delivery commitment on the master calendar."
        },
        {
          "name": "delivery_operational_stop",
          "description": "Separate internal route-stop projection; never a second sale or customer delivery."
        }
      ],
      "expectedResult": "The intended event, delivery, service, and other commitments appear once at the correct date, time, timezone, source, visibility, and status; filters affect only the view; the .ics export matches those visible entries; and authoritative changes remain in each source workflow.",
      "troubleshooting": [
        "Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.",
        "Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.",
        "Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields."
      ],
      "updated": "2026-08-25",
      "product": "centripos",
      "audience": "customer"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "create-verify-contact",
      "title": "Create and verify a contact",
      "summary": "Keep a single useful customer record, check the business context, and confirm your changes saved.",
      "introduction": "A contact record gives your team a shared place for a person's details and follow-up. Search for the person before creating another record, then save only the information your team needs. Available fields and permissions depend on your CentriCRM account.",
      "beforeYouBegin": "Open your organization's CentriCRM sign-in link and confirm the business or sub-account. Have accurate contact details and permission to maintain that person's record. Use a designated test contact when learning the workflow.",
      "steps": [
        "Open Contacts in the intended business. Search by email or phone as well as name; spelling differences can hide a record that already exists.",
        "If you find the person, open that record and compare the identifying details before editing. If several records appear to match, follow your team's duplicate-record process before adding more information.",
        "If the person is missing, choose Add Contact. Enter the available name, email and phone details carefully. Keep separate people in separate records even when they share a company or household.",
        "Review the fields your business uses for ownership, source and follow-up. A label or tag is an organizational choice; do not treat it as evidence that someone consented to receive marketing.",
        "Save the record, reopen it and confirm the details appear as intended. Search once more using the email or phone number to make sure teammates can find it.",
        "If a required business detail has no suitable field, ask an administrator to check Settings → Custom Fields. Agree on the field's meaning and type before creating a new field that could duplicate an existing one."
      ],
      "expectedResult": "Your team can find the intended person's saved record in the correct business, with accurate details and no unnecessary duplicate.",
      "troubleshooting": [
        "If a contact seems missing, check the selected business, search criteria and any active filters before creating a replacement.",
        "If a value does not save, check the field's format and your permissions. Reopen the record to distinguish a saved value from an unsaved edit.",
        "For support, collect the business name, field name, time and exact error. Redact personal information from screenshots."
      ],
      "sources": [
        {
          "title": "LeadConnector: create and edit contacts and custom fields",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006360-create-new-contact"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/create-verify-contact"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "manage-conversation",
      "title": "Review and respond to a conversation",
      "summary": "Find the right thread, review its history, and check the channel and recipient before responding.",
      "introduction": "Conversations brings customer messages and related CRM activity together. A reliable reply starts with the correct contact and communication channel. Channel availability, sending permissions and scheduling options depend on your account's setup.",
      "beforeYouBegin": "Confirm the business and your permission to contact the recipient. Use a connected, approved communication channel and follow the person's communication preferences. Use a designated test recipient when checking configuration.",
      "steps": [
        "Open Conversations and find the contact. Check Unread, Recent or All as appropriate; clear filters if you cannot see the expected thread.",
        "Open the thread and confirm the contact details. Read recent messages and timestamps before writing so you do not duplicate another teammate's response.",
        "Separate internal activity from customer messages. An appointment update or workflow entry in the history does not by itself mean a message was sent to the customer.",
        "Choose the intended available channel, such as email or SMS. Check the actual recipient address or number and the sender identity, especially when a contact has several ways to reach them.",
        "Prepare the reply. If you insert a snippet, template or custom value, inspect the completed text for missing names, dates, links and other details before sending.",
        "Send only when the content and recipient are approved. If using an available scheduling option, confirm the date, time and displayed timezone. Then inspect the thread's resulting status rather than assuming a button click proves delivery.",
        "Record the next action or owner using your team's normal process. If sending failed, investigate the visible error before retrying so the recipient does not receive duplicates."
      ],
      "expectedResult": "The intended conversation contains the reviewed response or scheduled action, with a clear status and a known next step for your team.",
      "troubleshooting": [
        "If a channel is unavailable, ask the account administrator to confirm connection and permissions; switching channels can change the recipient and consent requirements.",
        "If a conversation is missing, clear filters and verify the selected business and contact details.",
        "For an unexpected send status, record the time, channel and safe error text. Avoid sending again until you understand whether the first attempt was accepted."
      ],
      "sources": [
        {
          "title": "LeadConnector: managing conversations",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000001731-managing-conversations-quick-start-guide"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/manage-conversation"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "verify-lead-form",
      "title": "Check a website lead form before launch",
      "summary": "Follow a controlled submission from the public form to the correct contact and follow-up process.",
      "introduction": "A form is ready when visitors can submit it and your team can find and act on the resulting record. Testing the form in its actual page catches problems that a builder preview can miss. Forms and automation options vary by account and permissions.",
      "beforeYouBegin": "Identify the business, form and destination page. Use a test email or phone number your team controls. Check whether submission triggers messages or other automation, and arrange a controlled test with the account administrator before submitting.",
      "steps": [
        "Agree on the form's purpose and the minimum information needed for the next step. Distinguish required details from optional information, and review any consent wording appropriate to the intended follow-up.",
        "Inspect the form's fields and their contact-field mappings. Confirm that a custom field means the same thing to the form and to the team using the resulting record.",
        "Review the confirmation visitors will see and the intended internal notification or follow-up. Identify the owner responsible for new inquiries; a submission alone does not guarantee someone will respond.",
        "Open the actual page on a desktop and phone-sized screen. Check readable labels, required-field messages, keyboard access and whether submission provides a clear result.",
        "Submit one clearly identifiable test record after confirming the test's effects. Do not repeatedly press Submit when the result is uncertain; first check whether the record arrived.",
        "Find the submission and contact in the intended CentriCRM business. Compare the captured values with the test input, then check the expected assignment, notification and any approved follow-up separately.",
        "Correct mismatches and repeat a controlled test. Record the page URL, form name, test time and results, and remove or label the test record according to your team's process."
      ],
      "expectedResult": "A controlled submission creates or updates the expected record in the correct business, displays a clear confirmation and reaches the responsible team through the approved follow-up process.",
      "troubleshooting": [
        "If the page accepts the form but no record appears, confirm the business, form identity and field mappings before rebuilding the form.",
        "If a contact exists but no follow-up occurs, inspect the notification or workflow configuration separately from the form submission.",
        "If duplicate records or messages appear, pause further testing and compare submission times and automation activity. Share redacted evidence with support."
      ],
      "sources": [
        {
          "title": "LeadConnector: create and manage a contact form",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000008687-how-to-create-and-manage-a-contact-form"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/verify-lead-form"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "prepare-private-integration",
      "title": "Prepare an authorized private integration",
      "summary": "Define the business, owner and permissions before an administrator grants a developer access.",
      "introduction": "A private integration connects an authorized application to a specific CentriCRM account. Treat access as a business decision: name the owner, define the work it may perform and grant only the permissions needed. Seeing API documentation does not establish that your account has every API feature.",
      "beforeYouBegin": "Have an administrator confirm the intended business, available integration controls and the developer responsible for the connection. This checklist prepares the request; creating credentials or enabling a live connection requires the account owner's authorization.",
      "steps": [
        "Write down the outcome in plain language, such as reading contact details for an approved internal report. List the records the integration needs to read or change and the business it belongs to.",
        "Choose a responsible business owner and technical contact. Agree on how the integration will be disabled when its purpose ends or ownership changes.",
        "Ask the developer to identify the required API areas, account context and exact scopes using the official reference. Separate read access from permission to create, update, delete or send communications.",
        "Have an administrator confirm that Private Integrations is available and permitted for the account. If the control is absent, resolve access and entitlement before assuming a different account's instructions apply.",
        "Agree on a server-side secret store and an authorized handoff method before any token is generated. Tokens belong outside public code, browser fields, source control, screenshots and support messages.",
        "Plan a narrow test using controlled records, including the expected result and what should happen when access is missing or a different business is selected. Approve live writes and messages separately from a read test.",
        "Record the integration's purpose, business, owner and granted scopes without recording the token. Keep a rotation and revocation plan with the deployment owner, and verify the connection after any credential change."
      ],
      "expectedResult": "The administrator and developer have an agreed access request, secure credential-handling plan and controlled verification procedure for one identified business.",
      "troubleshooting": [
        "If the integration menu is missing, confirm account permissions and availability with the administrator rather than borrowing another business's credential.",
        "If the developer requests broad access, ask which required operation needs each scope before approval.",
        "If a credential is exposed, notify the authorized administrator promptly and follow the account's revocation or rotation process. Do not paste the credential into a support ticket."
      ],
      "sources": [
        {
          "title": "LeadConnector: private integrations",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000002774-private-integrations-everything-you-need-to-know"
        },
        {
          "title": "LeadConnector API reference",
          "url": "https://marketplace.leadconnectorhq.com/docs/"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/prepare-private-integration"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "confirm-business-profile",
      "title": "Start with the right RevPro business profile",
      "summary": "Confirm your business, location and public review destination before preparing requests.",
      "introduction": "Open RevPro at https://revpro.getcentri.com. Before working with reviews, confirm which business and location your account represents. A matching business name alone may not distinguish several locations or public profiles. Available features and controls depend on your account's plan and setup.",
      "beforeYouBegin": "Use your authorized RevPro account and have the intended business name, location address and public review profile available for comparison. The account's branded help address has not yet been added here; ask your administrator for the in-app or account-specific guide when you need exact screen instructions.",
      "steps": [
        "Sign in at https://revpro.getcentri.com and read the business and location context shown by your account. If you have several locations, select the one whose reviews you intend to manage.",
        "Compare the displayed business name, address and website with the location's current public information. Resolve a mismatch with the administrator before preparing a customer-facing request.",
        "Where your account provides a connected review profile or destination link, open it and verify that it leads to the correct public business and location. Do not infer the destination from a similar business name.",
        "Check which review-management tools your account actually provides. If a guide mentions a feature you cannot see, ask about permissions and plan availability rather than assuming it is enabled.",
        "Identify who owns profile changes and customer follow-up. Keep a record of the selected location and verified public destination without recording passwords or connection secrets.",
        "Continue to request preparation only after the identity and destination are confirmed. If the profile needs reconnecting or replacing, arrange that change with the authorized administrator first."
      ],
      "expectedResult": "You can identify the intended RevPro business and location, verify its public review destination and name the administrator responsible for configuration.",
      "troubleshooting": [
        "If the expected location is absent, check your account access with the administrator. Do not use a similar location as a substitute.",
        "If a public review link opens the wrong profile, stop preparing requests and capture the destination URL for the administrator.",
        "For exact controls, use the branded guide supplied by your account. The vendor's agency setup documentation is not a substitute for your account's customer guide."
      ],
      "sources": [
        {
          "title": "RevPro application",
          "url": "https://revpro.getcentri.com"
        },
        {
          "title": "Climbo: how branded customer guides are provided",
          "url": "https://guides.climbo.com/your-guides"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/confirm-business-profile"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "prepare-review-request",
      "title": "Prepare a review request for approval",
      "summary": "Check the recipient, business identity, message and review destination before any request is sent.",
      "introduction": "A review request should identify the business clearly and give the intended customer a working route to provide feedback. This preparation checklist does not send a request. Your account administrator must confirm which request channels, templates and scheduling features are available in your RevPro setup.",
      "beforeYouBegin": "Open https://revpro.getcentri.com and confirm the business and location. Have an approved recipient and permission to contact them through the intended channel. Use a controlled test recipient when checking a request, and obtain your account's branded guide for exact controls.",
      "steps": [
        "Confirm that the request belongs to the correct business and location. Check the public review destination using the business-profile checklist before selecting recipients.",
        "Choose the intended recipient according to your organization's review-request policy. Verify the email address or phone number and check whether the person has already received the same request.",
        "Review the wording for a clear business identity, a recognizable purpose and a working feedback link. Ask for honest feedback without implying that the customer must leave a positive rating.",
        "If your account provides a template or preview, inspect the completed message with its real substitutions. Check the name, location, link and sender details; an unresolved placeholder needs correction before approval.",
        "Open the destination link on a desktop and phone-sized screen. Confirm it resolves to the intended location and that the customer can understand the next step. Do not submit a fabricated public review during testing.",
        "Record the proposed recipient, channel and timing for the responsible person's approval. If an approved test send is needed, use a recipient your team controls and inspect the recorded result before any broader send.",
        "After a separately authorized send, check the available request status. A recorded send, a delivered message and a published review are different outcomes; report only what your account actually shows."
      ],
      "expectedResult": "The proposed request has a verified recipient, clear message, correct review destination and an explicit approval or controlled-test result before broader use.",
      "troubleshooting": [
        "If preview data is missing, check the source recipient and business fields rather than sending a request with unresolved placeholders.",
        "If a request's outcome is uncertain, inspect its existing status before sending again to avoid duplicate customer contact.",
        "If a documented channel or scheduling option is absent, confirm permissions and entitlement with the administrator. Do not assume another account's features apply."
      ],
      "sources": [
        {
          "title": "RevPro application",
          "url": "https://revpro.getcentri.com"
        },
        {
          "title": "Climbo: account-branded customer guides",
          "url": "https://guides.climbo.com/your-guides"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/prepare-review-request"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "troubleshoot-review-workflow",
      "title": "Troubleshoot a RevPro review workflow",
      "summary": "Separate account access, request delivery and review visibility, then collect useful evidence for support.",
      "introduction": "A missing request or review can involve several different stages. Start with the last stage you can verify and investigate the next one. This avoids changing a working business profile or contacting a customer repeatedly while the original outcome is uncertain.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com with an authorized account. Identify the affected business, location and approximate time. Available status information depends on your plan and permissions; this guide does not assume a particular logging or retry control exists.",
      "steps": [
        "Describe the expected result precisely: access to a location, a prepared request, a sent message, a working destination link or a visible published review. These require different checks.",
        "Confirm the selected business and location. If another authorized teammate can see the expected item, compare access and filters before concluding the item is missing.",
        "For a request problem, check the recipient details, intended channel, time and any status visible in your account. Keep a send attempt separate from evidence of delivery or recipient action.",
        "For a link problem, open the exact destination and compare its public business name and address. If it points to the wrong location, stop additional requests and involve the configuration owner.",
        "For a review-visibility problem, check the intended public review profile directly. Do not infer that RevPro can control the external platform's publication decisions or guarantee a review will appear.",
        "Before retrying, changing a connection or preparing another send, ask the responsible administrator to assess the existing result and the possible effect of the change.",
        "Collect a concise support report with the business and location, expected and observed behavior, timestamp with timezone, affected page URL and redacted screenshot or safe error text. Use the account's approved support channel and branded guide; omit credentials and unnecessary customer details."
      ],
      "expectedResult": "You have isolated the affected stage and gathered enough safe evidence for the administrator or support team to investigate without duplicate requests or speculative configuration changes.",
      "troubleshooting": [
        "If you cannot access the account, use its authorized sign-in recovery or administrator process before investigating review data.",
        "If no status is visible, report that limitation rather than guessing whether a request failed or was delivered.",
        "If a guide's controls do not match your screen, confirm that the guide belongs to your customer account and current plan. Agency API instructions serve a different audience."
      ],
      "sources": [
        {
          "title": "RevPro application",
          "url": "https://revpro.getcentri.com"
        },
        {
          "title": "Climbo: branded guide access and publication",
          "url": "https://guides.climbo.com/your-guides"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/troubleshoot-review-workflow"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "import-contacts",
      "title": "Import contacts with field checks",
      "summary": "Validate a small sample before importing a complete contact list.",
      "introduction": "A successful upload must put the right values on the right records. Decide whether you are creating, updating or doing both before importing.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Prepare a CSV with a clear header row. Remove irrelevant columns and create required custom fields before mapping.",
        "Check email and phone formats, duplicate identifiers and which business owns the records. Keep a recoverable copy of the original data.",
        "Open Contacts and the available import tool. Choose the intended create or update behavior; do not assume every row creates a new contact.",
        "Map each included column deliberately. Review how blank values and duplicate matches will be handled.",
        "Import a small approved sample first. Reopen the resulting contacts and compare identities, custom fields and ownership.",
        "Review errors before the full import. Correct rejected rows rather than resubmitting the entire file blindly."
      ],
      "expectedResult": "Sample records match the source, import behavior is understood and rejected rows have an identified cause.",
      "troubleshooting": [
        "A duplicate error can reflect account matching rules; inspect the existing contact before changing those rules.",
        "A contact ID from another business cannot identify a record in this account.",
        "Check field formats and mappings before repeating a failed import."
      ],
      "sources": [
        {
          "title": "LeadConnector: importing contacts",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000004433-importing-contacts"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/import-contacts"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "merge-duplicate-contacts",
      "title": "Review duplicate contacts before merging",
      "summary": "Choose the correct surviving record and inspect field choices.",
      "introduction": "Merging consolidates records. Establish that they represent the same person and decide which information should survive before confirming.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Search for the suspected duplicates using email, phone and name. Compare identities rather than relying on a shared surname.",
        "Open each record and note conflicting details and related work that your team needs to preserve.",
        "Use the available merge action only for confirmed duplicates. Choose the intended master record.",
        "Review the proposed field mapping. Resolve conflicting values with the record owner rather than accepting every default.",
        "Have an authorized user confirm the merge after reviewing its effects. Do not use merging to associate different household members.",
        "Reopen the surviving contact and verify details, findability and the business context. Check the associated work important to your team."
      ],
      "expectedResult": "One verified contact remains with reviewed identifying details.",
      "troubleshooting": [
        "If records represent different people, keep them separate and use an appropriate relationship instead.",
        "If the merge control is absent, check permissions; do not delete records as a substitute.",
        "Escalate unexpected missing history with the surviving record ID and redacted evidence."
      ],
      "sources": [
        {
          "title": "LeadConnector: merging multiple records",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000004413-merging-multiple-records"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/merge-duplicate-contacts"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "build-smart-list",
      "title": "Build and check a Smart List",
      "summary": "Test filter logic before using a segment for outreach.",
      "introduction": "A Smart List is defined by its filters. A plausible contact count does not prove that the intended people are included.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Write the segment rule in plain language, including who must be excluded.",
        "Open Contacts and create or edit the intended Smart List. Select fields and operators that match the rule.",
        "Review nested conditions and alternatives separately. Check whether the builder is combining each group with AND or OR.",
        "For date conditions, distinguish a fixed date from a rolling relative window. Confirm the timezone used by your account.",
        "Apply the filters and inspect several matching contacts plus known non-matching examples.",
        "Save a descriptive list name. Recheck membership immediately before a separately authorized bulk action or campaign."
      ],
      "expectedResult": "The saved segment includes and excludes the intended test examples.",
      "troubleshooting": [
        "Unexpectedly large lists often need a review of OR conditions and empty fields.",
        "For changing membership, check relative dates and recent contact updates.",
        "List membership alone is not permission to send marketing."
      ],
      "sources": [
        {
          "title": "LeadConnector: advanced filters in Smart Lists",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000007568-advanced-filters-in-smart-lists"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/build-smart-list"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "manage-contact-tags",
      "title": "Apply contact tags deliberately",
      "summary": "Check selected records and automation effects before a bulk tag change.",
      "introduction": "Tags organize contacts and may also trigger workflows. Treat bulk tag changes as operational changes when automation depends on them.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Agree on the exact tag spelling and purpose. Check whether an existing tag already serves that purpose.",
        "Ask the automation owner whether adding or removing it triggers messages or other changes.",
        "Filter and inspect the intended contacts. Confirm the selected count and scope of the selection.",
        "Choose the available add or remove tag action. Review the exact tags; removing all tags is a broader choice.",
        "Run an authorized small sample first and inspect its bulk-action status and resulting records.",
        "Proceed with the approved selection only after the sample behaves correctly. Record the action name and outcome."
      ],
      "expectedResult": "Only the intended contacts carry the reviewed tags, with understood automation effects.",
      "troubleshooting": [
        "If a message fires unexpectedly, involve the workflow owner before repeating the action.",
        "A bulk-action progress value is not a substitute for checking sample records.",
        "Do not remove unrelated tags to fix one incorrect label."
      ],
      "sources": [
        {
          "title": "LeadConnector: bulk add and remove tags",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000003233-bulk-add-and-remove-tags-from-contacts"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/manage-contact-tags"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "verify-calendar-connection",
      "title": "Verify a calendar connection",
      "summary": "Check linked-calendar writes, conflict blocking and timezone behavior.",
      "introduction": "A linked calendar and a conflict calendar serve different purposes. Confirm both before publishing booking availability.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the staff member, Google account and calendar that should receive new appointments.",
        "Review Settings → Calendars → Connections with the authorized calendar owner. Confirm access to the intended account.",
        "Check the linked calendar used for CRM events and the calendars used to detect conflicts. Writer access is needed to push events.",
        "Arrange a controlled appointment and confirm its date, timezone, participant and appearance on the linked calendar.",
        "Add an approved external Busy event and inspect whether the corresponding time becomes unavailable. Free events do not necessarily block bookings.",
        "Check the booking page on desktop and phone. Confirm the displayed timezone and clean up controlled test appointments."
      ],
      "expectedResult": "The intended calendar receives appointments and known Busy conflicts block the expected times.",
      "troubleshooting": [
        "If events do not appear externally, check linked-calendar selection and write access.",
        "For double bookings, inspect conflict calendars and whether the external event is Busy.",
        "Do not reconnect a different Google account merely because its calendar is easier to find."
      ],
      "sources": [
        {
          "title": "LeadConnector: connect Google Calendar",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000005594-how-to-connect-your-google-calendar"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/verify-calendar-connection"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "manage-opportunity-progress",
      "title": "Keep an opportunity in the correct pipeline",
      "summary": "Review the contact, stage, owner and status as a deal progresses.",
      "introduction": "A pipeline stage describes your sales process; the opportunity status describes its outcome. Agree on their meanings before moving records.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the contact and existing opportunity before creating another deal for the same work.",
        "Confirm the intended pipeline, stage and owner. Use your team’s definitions for qualified, won and lost.",
        "Review the amount and expected next action. Keep estimates distinct from confirmed revenue.",
        "Before changing a stage or field, check whether an Opportunity Changed workflow reacts to that transition.",
        "Apply an authorized change and inspect the saved opportunity. Confirm that any expected follow-up occurred once.",
        "Use controlled positive and negative examples when testing a trigger: one should match the exact transition, and one should not."
      ],
      "expectedResult": "The deal has the intended pipeline, stage, status and owner, with verified follow-up.",
      "troubleshooting": [
        "“Has Changed” and “Has Changed To” are different trigger conditions; compare the configured rule.",
        "If a deal is missing, check pipeline filters, ownership and permissions.",
        "Avoid repeatedly moving stages to force an automation to run."
      ],
      "sources": [
        {
          "title": "LeadConnector: Opportunity Changed trigger",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000007414-workflow-trigger-opportunity-changed"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/manage-opportunity-progress"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-workflow-goal",
      "title": "Test a workflow goal and exit path",
      "summary": "Define what happens when a goal is met and when it is not.",
      "introduction": "A goal can change where an enrolled contact continues in a workflow. Test the unmet path as carefully as the successful path.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Describe the intended outcome and the event that proves it, using a controlled contact.",
        "Open the workflow draft and review entry conditions, repeat enrollment and actions that could send messages.",
        "Configure the available goal condition. Check which enrolled contacts can advance to that goal.",
        "Review the behavior when a contact reaches the goal without meeting it: end, continue or wait where supported.",
        "Test one qualifying example and one that never meets the condition. Inspect their paths and downstream actions.",
        "Obtain approval for the exact trigger and actions before publication. Record how the owner will monitor and stop the workflow."
      ],
      "expectedResult": "Both qualifying and non-qualifying contacts follow an understood path.",
      "troubleshooting": [
        "A goal is not a universal stop switch; inspect actions after the goal.",
        "If the builder differs from older documentation, verify current account controls before assuming a numeric limit.",
        "Do not test with real customers when downstream messages are active."
      ],
      "sources": [
        {
          "title": "LeadConnector: workflow goal events",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000000090-how-to-set-up-workflow-goal-events"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-workflow-goal"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "disable-workflow-action",
      "title": "Understand a disabled workflow action",
      "summary": "A skipped action does not pause the rest of the workflow.",
      "introduction": "Disabling an action can skip that node while later active actions still execute. Review the complete path before using it during maintenance.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Locate the workflow and identify the precise action you intend to suspend.",
        "Read the actions before and after it, including branches and customer messages.",
        "Decide whether skipping only this action is appropriate. If all activity must stop, ask the workflow owner for the supported broader stop procedure.",
        "Make an authorized draft change and review how the node is shown as disabled.",
        "Use a controlled contact to inspect the execution log. Confirm the action is skipped and observe what runs next.",
        "Document the change, its reason and re-enable conditions. Review the path again before resuming the action."
      ],
      "expectedResult": "The team understands which node is skipped and which downstream work can still run.",
      "troubleshooting": [
        "If later messages continue, that can be expected behavior rather than a failed disable.",
        "Check logs for skipped versus failed actions; they mean different things.",
        "Avoid changing several nodes at once when diagnosing a single action."
      ],
      "sources": [
        {
          "title": "LeadConnector: temporarily disable workflow actions",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000007415-temporarily-disable-actions-in-a-workflow"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/disable-workflow-action"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "prepare-email-campaign",
      "title": "Prepare and test an email campaign",
      "summary": "Review the received email, audience and sender before approving a send.",
      "introduction": "An editor preview cannot reproduce every email client. Check the actual received message before using a campaign broadly.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Define the campaign purpose and approved recipient segment. Check exclusions and communication preferences.",
        "Choose an appropriate template and replace sample text, images, links and footer information.",
        "Inspect personalization values with realistic contact data. Provide a sensible result when optional data is missing.",
        "Check every button and link, including the preference or unsubscribe route, and confirm From and Reply-To identities.",
        "Send an authorized test to controlled inboxes. Review desktop and phone rendering, images, text fallback and link destinations.",
        "Review the final audience and schedule with the responsible sender. Publish or send only after approval, then inspect available delivery results."
      ],
      "expectedResult": "The approved campaign renders usefully and targets the intended audience.",
      "troubleshooting": [
        "If layouts differ, simplify unsupported email HTML rather than relying on browser rendering.",
        "A successful test to one inbox does not guarantee inbox placement everywhere.",
        "Stop approval if personalization or the preference route is broken."
      ],
      "sources": [
        {
          "title": "LeadConnector: email builder and inline editor",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006855-how-to-use-the-email-builder-and-its-in-line-editor"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/prepare-email-campaign"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "check-email-delivery",
      "title": "Investigate a failed email",
      "summary": "Compare sender identity and provider errors before retrying.",
      "introduction": "Email failure can come from sender configuration or the receiving provider. Start with the recorded error and one affected message.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Locate the failed conversation email and note its time, recipient domain and safe error text.",
        "Inspect the warning or provider detail available beside that message.",
        "Compare its From address with the identity verified for the configured SMTP provider.",
        "Ask the account administrator to confirm provider connection and sender verification; keep passwords out of support evidence.",
        "If configuration matches, request the relevant provider logs through the authorized owner.",
        "After correction, use one approved controlled test and check its outcome before resending customer messages."
      ],
      "expectedResult": "The failure is tied to a specific error or configuration issue, with a verified controlled retest.",
      "troubleshooting": [
        "A sender mismatch can fail even when the recipient address is valid.",
        "If an earlier attempt has an uncertain outcome, check status before resending.",
        "Do not replace the provider or edit DNS without understanding existing mail dependencies."
      ],
      "sources": [
        {
          "title": "LeadConnector: SMTP delivery troubleshooting",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000004976-troubleshooting-smtp-email-delivery-issues"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/check-email-delivery"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-sending-domain",
      "title": "Review email sending identity",
      "summary": "Distinguish the authenticated domain, displayed sender and reply destination.",
      "introduction": "Domain authentication supports sender identity but does not guarantee inbox delivery. Plan changes with the person responsible for existing email services.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Record the current From address, Reply-To destination and authenticated sending domain.",
        "Confirm ownership of the proposed domain or subdomain and inventory existing DNS and mail dependencies.",
        "Review the account-generated authentication requirements in Email Services. Use its exact values rather than a generic example.",
        "Have the authorized domain administrator assess conflicts and approve the change before any DNS edit.",
        "After a separately authorized setup, verify domain status and the assignments for the intended email categories.",
        "Inspect a controlled received message, reply routing and authentication results. Monitor failures before increasing sending volume."
      ],
      "expectedResult": "The team can explain the sender identity and verify the intended category uses the approved domain.",
      "troubleshooting": [
        "Do not delete existing MX or SPF records to resolve a conflict without checking their owner.",
        "A verified domain and a completed SSL certificate are separate setup results.",
        "Check reputation, list quality and content when authenticated email still misses the inbox."
      ],
      "sources": [
        {
          "title": "LeadConnector: dedicated sending domains",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/48001226590-dedicated-email-sending-domains-overview-setup"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-sending-domain"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-customer-invoice",
      "title": "Review a CentriCRM invoice",
      "summary": "Check customer, products, totals and recurrence before sharing an invoice.",
      "introduction": "These instructions concern CentriCRM invoices. They do not establish the behavior of CentriPOS invoicing, receipts or accounting integrations.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Confirm the customer record and the intended one-time or recurring billing arrangement.",
        "Open the available invoice editor and review business details, recipient and due date.",
        "Inspect each product, quantity, price and applicable adjustment. Check recurrence when using a recurring product.",
        "Compare subtotal, fees, tax and total with the agreed transaction. Do not enable optional charges by default.",
        "Inspect the customer preview and approved payment method. Save for review before sending.",
        "After authorized sharing, inspect the invoice’s recorded status. Treat payment recording and actual payment confirmation as separate checks."
      ],
      "expectedResult": "The reviewed invoice matches the agreed customer, amount and billing frequency.",
      "troubleshooting": [
        "If the total is unexpected, compare line items and optional fees before changing the whole invoice.",
        "For payment issues, verify the configured processor and invoice status.",
        "Do not infer a CentriPOS or accounting sync result from a CentriCRM invoice preview."
      ],
      "sources": [
        {
          "title": "LeadConnector: invoice editor",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006182-create-and-send-invoices-faster-with-the-new-invoice-editor"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-customer-invoice"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "prepare-payment-link",
      "title": "Prepare a payment link",
      "summary": "Check the customer checkout and billing frequency before sharing.",
      "introduction": "A payment link can represent a one-time or recurring purchase. Verify the resulting checkout, not only its internal name.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the product or service and the agreed amount, currency and billing frequency.",
        "Confirm that the authorized business has the intended supported payment provider configured.",
        "Open Payments → Payment Links where available and prepare the link with the approved product and payment type.",
        "Review the description and any recurring terms so the customer can understand the charge.",
        "Open the generated link on desktop and phone. Compare product, amount, business identity and frequency before sharing.",
        "Share only after authorization. Verify payment status separately; a link opening successfully is not evidence of a completed payment."
      ],
      "expectedResult": "The approved link opens the expected checkout with clear billing terms.",
      "troubleshooting": [
        "If the provider or payment type is absent, confirm setup and entitlement.",
        "For a changed price, recheck the generated checkout rather than assuming an old link updated.",
        "Never use a real charge solely to test whether a link loads."
      ],
      "sources": [
        {
          "title": "LeadConnector: shareable payment links",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006397-streamlined-payment-collection-with-shareable-payment-links"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/prepare-payment-link"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "read-subscription-status",
      "title": "Read a subscription status accurately",
      "summary": "Separate subscriptions, invoice recurrence and provider synchronization.",
      "introduction": "The Subscriptions view does not cover every recurring billing model. Find the correct billing record before interpreting a missing entry.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the customer, original purchase source and payment provider.",
        "Open Payments → Subscriptions where available and search for the intended subscription.",
        "Compare provider or subscription ID, amount and status with the expected purchase.",
        "Check whether the arrangement is an invoice recurring template or membership subscription; those are excluded from this documented view.",
        "For an initial payment failure, inspect the source transaction as well; a contact can exist without a subscription entry.",
        "Before changing or retrying billing, have the authorized billing owner compare provider status and synchronization behavior."
      ],
      "expectedResult": "The team identifies the correct billing source and reports the observed status without assuming universal synchronization.",
      "troubleshooting": [
        "A missing row does not by itself prove that no recurring arrangement exists.",
        "Different payment providers can synchronize differently.",
        "Do not create a replacement subscription until the original billing outcome is understood."
      ],
      "sources": [
        {
          "title": "LeadConnector: subscription statuses and tracking",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/48001225940-understanding-subscription-statuses-and-tracking"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/read-subscription-status"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-site-domain",
      "title": "Plan a website or funnel domain connection",
      "summary": "Identify the target product and protect existing domain services.",
      "introduction": "Website, email and client-portal domain connections serve different products. Review the exact target before granting DNS access.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the page or product and the precise hostname intended for it.",
        "Record current DNS, website and email services using that hostname or domain.",
        "Review Sites → Settings → Domains where available and select the intended product.",
        "Inspect the generated records or automatic connection request. Confirm their scope with the domain administrator.",
        "Obtain authorization before applying DNS changes. Do not copy another account’s targets or replace a working application domain.",
        "After authorized setup, verify the target page, HTTPS and redirects while checking existing mail and site services."
      ],
      "expectedResult": "The connection plan identifies the correct product, exact hostname and validation steps.",
      "troubleshooting": [
        "A domain connected elsewhere needs an ownership and dependency review before reassignment.",
        "Conflicting records require investigation rather than deletion by default.",
        "Do not treat a pending certificate as proof that DNS already points to the intended product."
      ],
      "sources": [
        {
          "title": "LeadConnector: connecting a domain",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000005273-connecting-your-domain-a-guide"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-site-domain"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-social-post",
      "title": "Prepare channel-specific social content",
      "summary": "Inspect each destination and format before a social post is approved.",
      "introduction": "The same text and media can behave differently across social channels. Review each connected destination on its own.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the approved campaign and the exact business pages that may receive the post.",
        "Open the available Social Planner and confirm connected page names.",
        "Prepare the shared message, then inspect channel-specific edits rather than assuming one version fits every platform.",
        "Check media crop, links, captions, mentions and any format restrictions for each selected channel.",
        "Review the preview and schedule, including timezone, with the responsible publisher.",
        "Publish only after approval and inspect each channel’s resulting status. Confirm the external post when access permits."
      ],
      "expectedResult": "Every selected channel has reviewed content, destination and timing.",
      "troubleshooting": [
        "If one channel rejects a post, inspect its error before reposting to all destinations.",
        "A connected personal profile and a business page are different destinations.",
        "Preview success does not prove external publication."
      ],
      "sources": [
        {
          "title": "LeadConnector: customize posts for each social channel",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000009553-customize-social-media-posts-for-each-channel-in-social-planner"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-social-post"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "check-crm-review-request",
      "title": "Check a CentriCRM reputation request",
      "summary": "Verify the connected profile and request result within CentriCRM.",
      "introduction": "CentriCRM reputation tools and RevPro are separate products. Confirm which system owns the request before troubleshooting it.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Confirm the business and connected review profile in the available CentriCRM reputation tools.",
        "Open the customer-facing review destination and verify the correct business and location.",
        "Review the approved recipient, channel and message. Check for a previous request to avoid duplicates.",
        "Use a controlled recipient for an authorized test and inspect the received message and destination.",
        "Check request status separately from delivery, clicks and the external review itself.",
        "If displaying reviews in a widget, inspect the intended page and filter settings after an authorized update."
      ],
      "expectedResult": "The request reaches the intended profile and its observed status is recorded accurately.",
      "troubleshooting": [
        "Do not use RevPro screen instructions to diagnose a CentriCRM request.",
        "If reviews are missing, verify the connection and external profile before repeating requests.",
        "A sent request does not guarantee a published review."
      ],
      "sources": [
        {
          "title": "LeadConnector: reputation management quick start",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000001734-reputation-management-quick-start-guide"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/check-crm-review-request"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "interpret-lead-attribution",
      "title": "Interpret lead source and attribution",
      "summary": "Compare the source record with the reporting context.",
      "introduction": "Attribution answers a defined question about a contact’s origin or activity. Establish the report’s meaning before comparing totals.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Choose the business, reporting period and question you need answered.",
        "Inspect the source and attribution details available on representative contacts.",
        "Compare recorded campaign or referral information with the actual lead journey your team intended to track.",
        "Check date ranges, filters and attribution definitions before comparing two reports.",
        "Use a controlled test lead when validating capture from an approved campaign or form.",
        "Record missing-source cases for investigation. Keep assumptions about unknown traffic separate from observed data."
      ],
      "expectedResult": "Your report states its scope and uses source data your team can trace to example contacts.",
      "troubleshooting": [
        "A contact’s source label and a campaign’s performance metric may answer different questions.",
        "Changes in filters or reporting periods can explain differing totals.",
        "Do not relabel historical records simply to make a report match an expectation."
      ],
      "sources": [
        {
          "title": "LeadConnector: lead sources and attribution",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006180-understand-lead-sources-improve-marketing-performance"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/interpret-lead-attribution"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "check-call-routing",
      "title": "Check inbound phone routing",
      "summary": "Trace ringing, answering and voicemail using a controlled call.",
      "introduction": "Forwarding, caller identity and voicemail settings interact. Document the current route before changing it.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the intended business number and the people or destination that should answer it.",
        "Review the available phone-number settings with the authorized phone administrator.",
        "Record forwarding, timeout, call-connect, whisper and recording choices that affect the route.",
        "Arrange an approved controlled call and observe which devices ring and what the caller hears.",
        "Test an unanswered case and verify where voicemail goes. Check caller identity on both sides.",
        "Make only approved changes and repeat the same checks before a broader rollout."
      ],
      "expectedResult": "The observed answered and unanswered call paths match the business’s intended routing.",
      "troubleshooting": [
        "Do not apply a universal timeout recommendation without considering the destination’s voicemail.",
        "For one failing number, compare its settings rather than changing every number.",
        "Ask the administrator about applicable recording requirements before enabling recording."
      ],
      "sources": [
        {
          "title": "LeadConnector: phone-number settings",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/48001239448-phone-number-settings-explained"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/check-call-routing"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "prepare-course-access",
      "title": "Prepare a course and its offer",
      "summary": "Check the learner’s access separately from the course content.",
      "introduction": "A course product holds content; an offer determines how learners receive access and any price. Review both before sharing.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Confirm the intended audience, course content and authorized instructor or owner.",
        "Use Memberships → Courses → Products where available to organize the course and lessons.",
        "Preview the learning sequence and check links, media and any unpublished content.",
        "Review the related offer, included course, pricing and access terms.",
        "Use a controlled learner account to inspect the approved access or checkout path.",
        "Publish and share only after approval. Recheck the learner’s actual access; draft offers are not available to learners."
      ],
      "expectedResult": "The intended learner can reach the approved content through the correct offer.",
      "troubleshooting": [
        "If the course exists but cannot be accessed, inspect the offer and learner entitlement.",
        "A course preview does not prove the paid checkout works.",
        "Do not grant a broad offer to fix a single learner’s access problem."
      ],
      "sources": [
        {
          "title": "LeadConnector: launch a course",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000006217-getting-started-launch-a-course"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/prepare-course-access"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "prepare-community-group",
      "title": "Prepare a community group",
      "summary": "Check membership, visibility and moderation before inviting members.",
      "introduction": "A community needs an access plan and responsible moderators as well as branding. A group link does not bypass permissions.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Define who should join and which content should remain restricted.",
        "Confirm the available client portal and community setup for the account.",
        "Review group identity, branding and the intended member access path.",
        "Assign ownership, administration and moderation according to team responsibilities.",
        "Check the group with a controlled member account as well as an administrator.",
        "Approve invitations only after verifying visible content, joining behavior and the process for reporting concerns."
      ],
      "expectedResult": "The intended member sees the appropriate group and content, with clear moderation ownership.",
      "troubleshooting": [
        "Administrator visibility can hide a member-access problem; test the member role.",
        "If a link fails, check membership and portal context before making content public.",
        "Use the account’s available controls; community features vary by setup."
      ],
      "sources": [
        {
          "title": "LeadConnector: setup and manage communities",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000000282-how-to-setup-customize-and-manage-your-communities"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/prepare-community-group"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "review-team-access",
      "title": "Review a team member’s access",
      "summary": "Match roles, module permissions and assigned records to the person’s work.",
      "introduction": "A missing record can involve assignment restrictions as well as module access. Diagnose the actual boundary before broadening permissions.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the person and the work they need to perform in this business.",
        "Open Settings → Users with authorized administrative access and find the existing user.",
        "Review the role, module permissions and any assigned-data restriction together.",
        "Apply only approved access changes and save them.",
        "Have the user verify the intended task and representative records with their own login.",
        "Record the access owner and review permissions when responsibilities change or the person leaves."
      ],
      "expectedResult": "The user can perform the approved work with appropriate record visibility.",
      "troubleshooting": [
        "Do not create a duplicate user when an email already belongs to an existing account.",
        "Check record assignment before granting broad administrative access.",
        "Keep passwords, OTPs and recovery links out of support reports."
      ],
      "sources": [
        {
          "title": "LeadConnector: user access and permissions",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000009052-user-access-manage-users-and-permissions"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/review-team-access"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "organize-project-tasks",
      "title": "Organize project work and ownership",
      "summary": "Give each task a clear outcome, owner and place in the project.",
      "introduction": "Projects keep work near CRM records. Structure and visibility should help the team find the next action.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Identify the project outcome and the contacts or opportunities it relates to.",
        "Open the available project workspace under Contacts → Tasks and choose the appropriate Space and List.",
        "Create tasks with clear outcomes, assignees, dates and priorities.",
        "Use subtasks for separately trackable work and associate CRM records where appropriate.",
        "Inspect the same work in list or Kanban view and agree on status meanings.",
        "Verify private-space membership and task ownership before adding sensitive internal information."
      ],
      "expectedResult": "Teammates can find the work, see who owns it and understand its current status.",
      "troubleshooting": [
        "A different view does not necessarily represent a different set of tasks; check filters.",
        "If work is invisible, inspect Space membership and permissions.",
        "Use specific due dates rather than placing every task at the same artificial deadline."
      ],
      "sources": [
        {
          "title": "LeadConnector: project management",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000008496-introduction-to-project-management"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/organize-project-tasks"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "triage-support-ticket",
      "title": "Triage a support ticket",
      "summary": "Assign ownership and distinguish the due date from service targets.",
      "introduction": "Ticketing availability depends on the account’s plan and permissions. Use one traceable ticket to coordinate the response.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Confirm Ticketing is available and identify whether the request arrived manually or through a connected channel.",
        "Review the requester, problem and existing related tickets before creating another.",
        "Set the appropriate category, priority and responsible owner.",
        "Review the due date separately from any service-level target; they are not the same measure.",
        "Prepare a response after checking the ticket history and recipient. Send only when authorized.",
        "Update status and next action so another teammate can understand what remains."
      ],
      "expectedResult": "The request has a clear owner, status and next action with appropriate response targets.",
      "troubleshooting": [
        "If tickets do not arrive, investigate the intake connection separately from assignment.",
        "If an expected control is absent, confirm plan and role availability.",
        "Avoid duplicate replies by reading recent activity before responding."
      ],
      "sources": [
        {
          "title": "LeadConnector: introduction to ticketing",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000009662-introduction-to-ticketing"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/triage-support-ticket"
    },
    {
      "product": "centricrm",
      "audience": "customer",
      "slug": "evaluate-ai-task",
      "title": "Evaluate an AI feature before automating",
      "summary": "Define a bounded task and check outputs before customer-facing use.",
      "introduction": "Internal assistance, generated content and customer-facing agents have different effects. Availability and usage charges depend on the account.",
      "beforeYouBegin": "Confirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.",
      "steps": [
        "Choose one specific task and define what a correct result would look like.",
        "Confirm the tool is available for the plan, permissions and connected channels.",
        "Provide approved source material and define when a person must take over.",
        "Test with controlled examples, including missing information and questions the tool should escalate.",
        "Review accuracy, tone and any proposed external action before enabling customer-facing automation.",
        "Identify an owner to monitor output, usage and handoff behavior after authorized activation."
      ],
      "expectedResult": "The team understands the task, limits, costs and escalation path before automation is enabled.",
      "troubleshooting": [
        "If a feature is missing, check plan, permissions, Labs and integration prerequisites.",
        "A fluent answer is not verification of customer data or policy.",
        "Pause expansion when tests reveal unsupported claims or unreliable handoff."
      ],
      "sources": [
        {
          "title": "LeadConnector: AI tools available in an account",
          "url": "https://help.leadconnectorhq.com/support/solutions/articles/155000008751-ai-tools-available-in-your-account"
        }
      ],
      "url": "https://platform.getcentri.com/centricrm/evaluate-ai-task"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "read-request-analytics",
      "title": "Read request analytics without confusing outcomes",
      "summary": "Separate sent, delivered, clicked and published-review results.",
      "introduction": "Request Analytics describes the request journey for a selected month. A click is engagement, not proof of a published review.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the location and reporting month before comparing figures.",
        "Read Sent, Delivered and Clicked as separate stages.",
        "Investigate a large sent-to-delivered gap using recipient quality and channel evidence.",
        "Compare first-message and reminder engagement before changing reminder policy.",
        "Review unique link visits by source, such as messages, QR/direct traffic or employee links.",
        "Record the period and definitions beside your findings. Check external review results separately."
      ],
      "expectedResult": "Your report identifies the request stage and period behind each figure.",
      "troubleshooting": [
        "An empty month may simply have no requests.",
        "Do not divide metrics with different scopes or periods.",
        "Investigate weak delivery before increasing sending volume."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: request analytics",
          "url": "https://guides.climbo.com/request-analytics"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/read-request-analytics"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "reply-to-review",
      "title": "Prepare a reply to the correct review",
      "summary": "Identify public versus private feedback and review the response before publishing.",
      "introduction": "The reviews feed can contain public reviews, private feedback and video testimonials. Their response destinations are different.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Open Reputation → Reviews where available and locate the intended feedback.",
        "Read the source, date and business context. Confirm whether the response will be public or private.",
        "Prepare a specific, courteous reply without exposing private transaction or customer details.",
        "If generating a draft with AI, check every factual claim and proposed commitment.",
        "Obtain the required approval before sending or publishing, then inspect the recorded result.",
        "For public replies, verify the external review page when authorized access permits."
      ],
      "expectedResult": "The reviewed reply reaches the intended feedback destination.",
      "troubleshooting": [
        "Deleting a review inside the platform does not remove it from the external review site.",
        "Hiding a review from a website widget does not hide it from the source platform.",
        "A private-feedback response should not expose that feedback publicly."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: replying to reviews",
          "url": "https://guides.climbo.com/replying-to-reviews"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/reply-to-review"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "interpret-rating-goals",
      "title": "Interpret the reputation dashboard",
      "summary": "Read aggregate figures and rating goals in their proper context.",
      "introduction": "A rating goal is a planning estimate. It does not promise that customers will leave particular ratings.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the location and connected review sites represented on the dashboard.",
        "Read review count and average rating together; neither alone describes the complete picture.",
        "Inspect the platform breakdown before comparing an aggregate with a single review site.",
        "Treat the next-goal estimate as a model of what would move the average.",
        "Choose an appropriate service-improvement or request-follow-up action rather than asking only for positive ratings.",
        "Record the period and sources when discussing progress with the team."
      ],
      "expectedResult": "The team can explain the dashboard’s scope and distinguish a goal from an observed result.",
      "troubleshooting": [
        "Different connected-platform sets can explain different totals.",
        "A large existing review base can require more new reviews to move its average.",
        "Do not turn a rating estimate into a customer guarantee."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: dashboard and rating goals",
          "url": "https://guides.climbo.com/dashboard-rating-goals"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/interpret-rating-goals"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "check-video-testimonials",
      "title": "Check video testimonial collection",
      "summary": "Confirm entitlement, customer consent and the resulting video record.",
      "introduction": "Video testimonials are plan-dependent and use the customer review-link flow. Test the experience before promoting it.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the location’s entitlement and the approved purpose for collecting testimonials.",
        "Review the Video Testimonial option under the available review-link settings.",
        "Use a controlled phone to inspect recording or upload, consent and the displayed file requirements.",
        "Submit only an authorized test clip without real customer information.",
        "Find the result in Reviews and allow time for processing before checking playback or transcript.",
        "Review separate approval and permissions before sharing the clip socially or displaying it in a widget."
      ],
      "expectedResult": "An approved test reaches the intended location and can be reviewed before reuse.",
      "troubleshooting": [
        "An absent option can reflect plan availability.",
        "For rejected files, follow the current on-screen duration, size and format requirements.",
        "Do not assume collecting a clip authorizes every later publication."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: video testimonials",
          "url": "https://guides.climbo.com/video-testimonials"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/check-video-testimonials"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "review-employee-tracking",
      "title": "Review employee tracking labels",
      "summary": "Use meaningful internal attribution and inspect the matched reviews.",
      "introduction": "Employee tracking is plan-dependent. Matches indicate how the configured labels were detected, not a complete measure of performance.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Agree on the purpose of tracking and who may maintain the profiles.",
        "Review each employee profile, active status and configured aliases.",
        "Use permitted service or role labels; the documented alias rules prohibit the employee’s own name.",
        "Inspect representative matched reviews and check for accidental or ambiguous matches.",
        "Compare the leaderboard’s metric and period before discussing results.",
        "Explain limitations to the team and review labels when roles change."
      ],
      "expectedResult": "The team understands what attribution measures and can inspect its supporting reviews.",
      "troubleshooting": [
        "Inactive profiles are not matched against new reviews.",
        "A frequent general word can create misleading attribution.",
        "Do not ask customers to mention a named individual to influence tracking."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: employee tracking",
          "url": "https://guides.climbo.com/employee-tracking"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/review-employee-tracking"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "review-google-profile",
      "title": "Review Google Business Profile changes",
      "summary": "Check connection authority and public business information before saving.",
      "introduction": "Profile management requires the appropriate Google Login connection and a verified business. Public Access alone does not authorize changes.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the exact business and location, then check connection and verification status.",
        "Compare proposed information with approved business records before editing.",
        "Review the available Profile sections separately, including business details, photos and hours.",
        "Use the supported place for each change. The documented address field is read-only here and requires Google’s own profile process.",
        "Obtain approval before saving changes that will be sent to Google.",
        "Inspect the recorded result and later compare the public listing; external updates need not appear instantly."
      ],
      "expectedResult": "Approved information is submitted for the correct business and its public result is checked.",
      "troubleshooting": [
        "Refresh an expired connection through the authorized owner; do not select a different location.",
        "A pending Google verification must be resolved before profile management.",
        "Avoid deleting photos while diagnosing an unrelated connection issue."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: Google Business Profile management",
          "url": "https://guides.climbo.com/google-business-profile-management"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/review-google-profile"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "check-review-widget",
      "title": "Check a website review widget",
      "summary": "Verify the layout, filters and page before approving an embed.",
      "introduction": "Widget layout and filters determine what visitors see. A source review remaining public does not require it to appear in a website widget.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm widget entitlement and the location whose reviews should appear.",
        "Choose a layout that fits the intended page rather than covering important controls.",
        "Review type, rating and source filters before diagnosing an empty widget.",
        "Inspect the preview with realistic short and long review text.",
        "Have the website owner approve and install the provided embed in a test or review environment.",
        "Check desktop and phone layout, loading and any review destination before publication."
      ],
      "expectedResult": "The approved page displays the intended review set without obstructing its main task.",
      "troubleshooting": [
        "Check source connection and filters when the widget is empty.",
        "The badge layout relies on Google totals rather than written review cards.",
        "Hiding a card from a widget does not remove the review from its external source."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: website widgets",
          "url": "https://guides.climbo.com/website-widgets"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/check-review-widget"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "interpret-visibility-reports",
      "title": "Interpret Maps and AI visibility reports",
      "summary": "Compare reports using the same keyword, location, area and update time.",
      "introduction": "Maps and AI ranking reports are periodic snapshots, not live search results. Report scope matters as much as position.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the location and relevant connected Google profile.",
        "Read the report’s last-updated time before discussing recent changes.",
        "Record the search keyword and map radius used for the comparison.",
        "Inspect competitor and location context instead of treating one rank as universal.",
        "Keep Maps ranking, AI ranking and profile interaction metrics separate.",
        "Compare like-for-like reports over time and record proposed actions as hypotheses rather than guaranteed ranking fixes."
      ],
      "expectedResult": "The reported visibility result includes its scope, period and limitations.",
      "troubleshooting": [
        "The official guide describes monthly Maps and AI reports; they should not be labeled live.",
        "AI Ranking and Performance may be unavailable on some plans.",
        "Performance requires Google Login even where ranking supports Public Access."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: ranking and performance analytics",
          "url": "https://guides.climbo.com/ranking-performance-analytics"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/interpret-visibility-reports"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "prepare-social-share",
      "title": "Prepare a review for social sharing",
      "summary": "Check eligible content, destination and format before publication.",
      "introduction": "Social sharing uses connected pages and plan-dependent controls. Public review content still needs a thoughtful publication review.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Select the intended written review or video testimonial and confirm its source.",
        "Check the actual connected destination names before preparing the post.",
        "Choose a supported content format for the selected channels.",
        "Review the image or clip, caption, attribution and any generated text.",
        "Confirm approval, timing and timezone before publishing or scheduling.",
        "Inspect each destination’s resulting status and avoid reposting when an earlier outcome is uncertain."
      ],
      "expectedResult": "The approved share uses the correct review, format and connected pages.",
      "troubleshooting": [
        "The Share control can be absent because of plan, rating or missing written text.",
        "Google publishing needs Google Login, not Public Access.",
        "Supported formats differ by channel; a preview is not evidence of external publication."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: sharing reviews on social media",
          "url": "https://guides.climbo.com/sharing-reviews-on-social-media"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/prepare-social-share"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "review-social-automation",
      "title": "Review automatic social sharing",
      "summary": "Define destination, selection rules and oversight before enabling an agent.",
      "introduction": "The Social Agent can publish without a person reviewing each run. Treat its configuration as a public publishing decision.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm entitlement, connected pages and the owner responsible for published content.",
        "Review the social template and the allowed post type.",
        "Choose the intended frequency, rating threshold, language and caption guidance.",
        "Inspect which selected channels support that format.",
        "Obtain explicit approval before enabling and saving automatic publication.",
        "Monitor the Feed and failed-reason details after activation; check public results and token usage."
      ],
      "expectedResult": "Automatic sharing has approved selection rules, destinations and a monitoring owner.",
      "troubleshooting": [
        "A run can produce no post when no eligible unshared review is available.",
        "Check connection permissions and token availability for failures.",
        "Do not enable automation merely to inspect its settings."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: Social Agent",
          "url": "https://guides.climbo.com/social-agent"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/review-social-automation"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "review-auto-replies",
      "title": "Review automatic Google review replies",
      "summary": "Set boundaries and monitoring before enabling automatic responses.",
      "introduction": "The SEO Agent automatically publishes eligible Google review replies. Other review platforms are outside this documented automatic-reply scope.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm plan availability, Google Login authority and the business’s reply policy.",
        "Review tone, length, language, rating threshold and additional instructions.",
        "Decide which cases need human handling and avoid instructions that invent transaction details.",
        "Check whether configuration also overrides manual AI draft settings.",
        "Obtain approval before enabling the agent or starting a separate backlog-reply run.",
        "Monitor its Feed, public replies and failure reasons. Keep an owner responsible for stopping unsuitable automation."
      ],
      "expectedResult": "Automatic replies operate within an approved policy and are monitored after activation.",
      "troubleshooting": [
        "Public Access is insufficient for automatic Google replies.",
        "Replies are asynchronous; an immediate absence does not prove failure.",
        "Check tokens, review eligibility and connection validity before restarting a backlog run."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: SEO Agent",
          "url": "https://guides.climbo.com/seo-agent"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/review-auto-replies"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "configure-review-notifications",
      "title": "Check review notification delivery",
      "summary": "Verify both event switches and a working delivery channel.",
      "introduction": "Notification preferences belong to the selected location. A switched-on preference still needs a permitted delivery channel.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the location and the people responsible for reacting to review activity.",
        "Open the available Notifications settings and review recipient email details.",
        "If using device notifications, check site and operating-system permission on that device.",
        "Select the relevant review, feedback, automation or usage events rather than enabling everything without an owner.",
        "Use an available test or controlled event to verify the intended channel.",
        "Repeat the review separately for other locations; do not assume preferences were copied."
      ],
      "expectedResult": "The chosen location’s important events reach a verified, responsible recipient.",
      "troubleshooting": [
        "A browser that previously blocked permission may require a site-settings change.",
        "Unavailable device notifications can reflect browser, device or account support.",
        "Check the current account controls when older guides disagree about recipient limits."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: notifications",
          "url": "https://guides.climbo.com/notifications"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/configure-review-notifications"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "inspect-location-history",
      "title": "Use history to investigate requests and AI actions",
      "summary": "Filter the right location and stage before retrying an action.",
      "introduction": "History provides evidence for the selected location. Request activity and AI activity answer different questions.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the affected location, approximate time and expected action.",
        "Choose the appropriate history tab for a request or AI action.",
        "Filter by supported category, channel, contact and date range as appropriate.",
        "Inspect the matching entry and its observed outcome before making another attempt.",
        "For AI activity, compare the action and token usage with the task performed.",
        "Share a concise, redacted support report. Do not assume an export feature exists; the documented history is read in the interface."
      ],
      "expectedResult": "The investigation identifies a traceable action and its location-specific evidence.",
      "troubleshooting": [
        "No entry in one location does not prove no action occurred in another.",
        "Clear filters when expected activity seems missing.",
        "Keep customer details and credentials out of screenshots sent to support."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: history",
          "url": "https://guides.climbo.com/history"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/inspect-location-history"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "manage-location-context",
      "title": "Work safely across several locations",
      "summary": "Distinguish account-wide settings from location-specific settings.",
      "introduction": "A business account can contain several independent locations. The app displays one location at a time.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Confirm the business account selected at login.",
        "Use the available location switcher and verify the name and address before working.",
        "Treat reviews, contacts, templates, campaigns and integrations as belonging to that location.",
        "Review location settings individually when standardizing notifications or connections.",
        "Ask the authorized owner to assess account-wide Team, Billing or location changes.",
        "Verify the context again before a send, public edit or automation change."
      ],
      "expectedResult": "Changes and reports are attributed to the intended business and location.",
      "troubleshooting": [
        "A single-location account may have no active location-switching control.",
        "A new location starts without the first location’s connections.",
        "Deleting a location is permanent and does not itself lower the subscription quantity."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: multi-location management",
          "url": "https://guides.climbo.com/multi-location-management"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/manage-location-context"
    },
    {
      "product": "revpro",
      "audience": "customer",
      "slug": "review-revpro-team",
      "title": "Review RevPro team roles",
      "summary": "Match account-wide ownership and location access to responsibilities.",
      "introduction": "Owner and Staff access serve different purposes. Review assigned locations before promoting a team member.",
      "beforeYouBegin": "Sign in at https://revpro.getcentri.com and confirm the location. Ask your administrator about plan availability and approve public changes before saving.",
      "steps": [
        "Identify the person’s day-to-day work and locations they need to access.",
        "Have an authorized Owner inspect the account’s Team controls.",
        "Choose the appropriate role; Owner access includes account-wide administration.",
        "For Staff, review the intended location assignments.",
        "After an approved update, have the person verify access with their own login.",
        "Review access when responsibilities change and keep account ownership deliberate."
      ],
      "expectedResult": "The person can reach the intended locations with the appropriate administrative boundary.",
      "troubleshooting": [
        "Staff not seeing billing or the team list can be expected behavior.",
        "New locations may be visible to Owners automatically; review that broader role carefully.",
        "Do not share a single login to work around missing location access."
      ],
      "sources": [
        {
          "title": "Climbo Client Mode: add team members",
          "url": "https://guides.climbo.com/add-team-members"
        }
      ],
      "url": "https://platform.getcentri.com/revpro/review-revpro-team"
    }
  ]
}
