> ## Documentation Index > Fetch the complete documentation index at: https://docs-pos.solya.app/llms.txt > Use this file to discover all available pages before exploring further. # Attach a store to a company and set its establishment number > Sets which société a store trades under and its per-establishment number (FR: the NIC, the 5-digit half the SIRET is composed from). A store ALWAYS has a société — the column is NOT NULL and defaults to the « Société à compléter » placeholder — so this operation MOVES an attachment, it never creates one from nothing. `establishmentNumber` may be `null`, which is the explicit not-yet-known state; it is never invented. A non-null number is validated against the société's registration number through the composed identifier's check digit (FR: the SIRET's Luhn), so a NIC that does not belong to that SIREN is a 400 with a field error. The body's `storeId` is IGNORED — the path wins. 404s for an unknown société or an unprovisioned store. ## OpenAPI ````yaml /openapi.json put /v1/companies/stores/{storeId} openapi: 3.0.3 info: title: Solya POS API version: 1.0.0 description: >- The Solya POS backend HTTP surface. Every documented operation is agent-ready: it carries an `operationId`, an agent-facing `description`, the `pos.*` scopes it enforces (`x-required-permissions`) and an `x-agent-tier`. Success responses return the payload as raw JSON; failures return the `ErrorResponse` envelope (`{ error: { code, message, statusCode } }`). servers: - url: / description: The backend, relative to its deployed origin. security: [] paths: /v1/companies/stores/{storeId}: put: tags: - Network summary: Attach a store to a company and set its establishment number description: >- Sets which société a store trades under and its per-establishment number (FR: the NIC, the 5-digit half the SIRET is composed from). A store ALWAYS has a société — the column is NOT NULL and defaults to the « Société à compléter » placeholder — so this operation MOVES an attachment, it never creates one from nothing. `establishmentNumber` may be `null`, which is the explicit not-yet-known state; it is never invented. A non-null number is validated against the société's registration number through the composed identifier's check digit (FR: the SIRET's Luhn), so a NIC that does not belong to that SIREN is a 400 with a field error. The body's `storeId` is IGNORED — the path wins. 404s for an unknown société or an unprovisioned store. operationId: attachStoreToCompany parameters: - schema: type: string minLength: 1 in: path name: storeId required: true requestBody: required: true content: application/json: schema: type: object properties: storeId: type: string minLength: 1 legalEntityId: type: string minLength: 1 establishmentNumber: nullable: true type: string minLength: 1 required: - storeId - legalEntityId - establishmentNumber example: storeId: store-rivoli legalEntityId: le-solya establishmentNumber: '00074' responses: '200': description: The stored attachment. content: application/json: schema: type: object properties: storeId: type: string minLength: 1 legalEntityId: type: string minLength: 1 establishmentNumber: nullable: true type: string minLength: 1 required: - storeId - legalEntityId - establishmentNumber additionalProperties: false description: The stored attachment. example: storeId: store-rivoli legalEntityId: le-solya establishmentNumber: '00074' '400': description: >- The request failed schema validation; `error.fieldErrors` lists the fields. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' '401': description: No valid credential was presented — send a bearer token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: The actor is authenticated but lacks the required `pos.*` scope. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: No resource matches the addressed identifier. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: An unexpected server error — safe to retry idempotent requests. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearerAuth: [] components: schemas: ValidationErrorResponse: type: object required: - error additionalProperties: false description: >- A `VALIDATION_FAILED` envelope carrying the offending fields in `fieldErrors`. properties: error: type: object required: - code - message - statusCode additionalProperties: false properties: code: type: string enum: - VALIDATION_FAILED message: type: string statusCode: type: integer fieldErrors: type: array description: >- One entry per rejected field: the field path and why it was rejected. items: type: object required: - field - message additionalProperties: false properties: field: type: string description: Dot-path of the offending field. message: type: string description: Why the field was rejected. ErrorResponse: type: object required: - error additionalProperties: false description: The uniform failure envelope every non-2xx response returns. properties: error: type: object required: - code - message - statusCode additionalProperties: false properties: code: type: string enum: - VALIDATION_FAILED - UNAUTHORIZED - FORBIDDEN - NOT_FOUND - CONFLICT - BUSINESS_RULE_VIOLATION - INTERNAL_ERROR description: >- Machine-readable kernel `ResultCode` — branch on this, not on `message`. message: type: string description: >- Human-readable explanation. Safe to surface; never leaks server internals. statusCode: type: integer description: >- The HTTP status, mirrored into the body so a client need not read headers. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- `Authorization: Bearer `. Accepts EITHER a Keycloak access token (scopes-in-token) OR an opaque POS session token; both resolve to the same `pos.*` scope vocabulary the route guards enforce. ````