> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/use-cases/own-your-customer.md). # Own your customer: local commerce Small sellers reaching buyers directly — keeping the margin, the relationship, and a verifiable identity — instead of renting an aggregator. A boutique hotel pays 18% of every international booking to an OTA — and never owns the guest relationship. A smallholder farmer is captive to local middlemen and sells at distress prices. A pet-services owner wants to be found by nearby customers and keep a care history for the animals they look after. In each case the seller creates the value, but an aggregator owns the discovery, the customer, and the margin. NFH fabric lets small sellers **be discovered directly, transact on their own terms, and keep the customer relationship** — while carrying verifiable claims (provenance, ratings, certifications) that used to require a platform's brand to be believed. ## What changes * The hotel takes **direct bookings** and keeps the \~18% it paid to OTAs — and owns the guest relationship for repeat stays. * The farmer reaches buyers beyond local middlemen, gets a **fair, transparent price**, and avoids distress sales. * The pet-services owner is **discovered by nearby customers** and maintains a portable care/vaccination identity per pet that follows the animal. * A handloom cooperative sells with **verifiable provenance and origin-certification claims**, protecting margins against knock-offs. * Trust that used to require a platform brand now travels as **credentials the seller controls**. ## Where to start Register one seller, publish a small catalogue (rooms, produce, or services), and attach one verifiable claim (a certification or rating). Run a direct discover → book → settle loop from a sandbox buyer app, confirming the seller keeps the full margin and the relationship. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nfh.global/use-cases/own-your-customer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.