> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/guides/verticals/barber/manifest-and-services.md).

# Declare the shop

Declare a barbershop manifest: the core nine plus client creation and loyalty, and a service catalog built for fast turnover.

## The manifest

A barbershop platform declares the core nine, `CreateClients`, and the loyalty pair. Nothing else. Capabilities you do not declare are capabilities Nerova never calls, and a lean manifest certifies faster because only the declared surface is conformance-tested.

```json
{
  "contractVersion": "2026-08-01",
  "providerName": "Fade District",
  "capabilities": [
    "ReadServices",
    "ReadStaff",
    "ReadSchedules",
    "ReadClients",
    "ReadAvailability",
    "ReadAppointments",
    "CreateAppointments",
    "RescheduleAppointments",
    "CancelAppointments",
    "CreateClients",
    "ReadLoyalty",
    "RedeemLoyalty"
  ]
}
```

No `IntakeForms` means services never carry intake schemas and the concierge never asks pre-appointment questions. No subject capabilities means no `subjectVocabulary` and no `subjectFields`: the person on the phone is the person in the chair. If your platform also issues gift cards, add `ReadGiftCards` and `IssueGiftCards` and follow the [salon retail flow](/guides/verticals/beauty-and-nails/booking.md) unchanged.

## The service catalog

Barbershop catalogs win on clarity: short names, honest durations, walk-in prices. Staff matter here; regulars book a barber, not a slot.

```json
[
  {
    "externalServiceId": "svc_fade",
    "name": "Skin fade",
    "durationMinutes": 45,
    "price": { "amountCents": 22000, "currency": "ZAR" },
    "category": "Cuts",
    "description": "Clipper fade, styled to finish.",
    "intakeFields": []
  },
  {
    "externalServiceId": "svc_beard_trim",
    "name": "Beard trim",
    "durationMinutes": 20,
    "price": { "amountCents": 12000, "currency": "ZAR" },
    "category": "Grooming",
    "description": "Shape and line-up with hot towel.",
    "intakeFields": []
  },
  {
    "externalServiceId": "svc_cut_and_beard",
    "name": "Cut and beard combo",
    "durationMinutes": 60,
    "price": { "amountCents": 30000, "currency": "ZAR" },
    "category": "Cuts",
    "description": "Skin fade plus full beard service.",
    "intakeFields": []
  }
]
```

With `IntakeForms` undeclared, every `intakeFields` array stays empty; declaring the capability later is additive and needs no migration. The catalog rules live on the [services reference](https://docs.nerovasystems.com/documentation/provider-api/operations/services).

Next: [Booking and regulars](/guides/verticals/barber/booking.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerovasystems.com/guides/verticals/barber/manifest-and-services.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
