# PUT /v1/shops/{id}/exceptions/{ean}

> Fix a product's reorder point by hand, or keep it off the stop-stocking list, or both.

Markdown twin of https://panlytics.net/developers/api/exceptions-save (last updated 2026-10-25). Every page of the Panlytics developer docs is listed at https://panlytics.net/developers/llms.txt, and all of them are in one file at https://panlytics.net/developers/llms-full.txt. The site guide is https://panlytics.net/llms.txt.

## What it does

Writes or replaces the shop's one rule for the product, exactly as the Exceptions page does: the same checks, the same audit row. A rule must say something: a level, `neverStop`, or both. The level overrides the worked-out reorder point in every figure from the next read on.

## Who may call it

A key whose maker's role holds `exceptions` (manage exceptions), after the fence, for the shop or category it names.

## Request

```http
PUT https://panlytics.net/api/v1/shops/{id}/exceptions/{ean}
```

### Parameters

| Name | In | Type | Required | What it is |
| --- | --- | --- | --- | --- |
| `id` | path | integer | Yes | The shop's id. |
| `ean` | path | string | Yes | The product's id in the shop's own system, usually its barcode (EAN). A product's full name is accepted too. |
| `Authorization` | header | string | Yes | Bearer, a space, then the key. |

### Body

Sent as `application/json`.

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `keepAt` | integer or null | No | The reorder point to keep the product at, in pieces; null to fix no level. |
| `neverStop` | boolean | No | True to keep the product off the stop-stocking list for good. |
| `reason` | string | No | Why, in a sentence. People read it on the Exceptions page. |

### Example request

```bash title="curl"
curl -X PUT https://panlytics.net/api/v1/shops/12/exceptions/6410000000017 \
  -H "Authorization: Bearer $PANLYTICS_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keepAt": 12,
  "neverStop": true,
  "reason": "Sold out every Saturday morning."
}'
```
```python title="Python"
import os

import requests

response = requests.put(
    "https://panlytics.net/api/v1/shops/12/exceptions/6410000000017",
    headers={"Authorization": f"Bearer {os.environ['PANLYTICS_KEY']}"},
    json={
      "keepAt": 12,
      "neverStop": True,
      "reason": "Sold out every Saturday morning."
    },
    timeout=60,
)
response.raise_for_status()
print(response.json())
```
```typescript title="TypeScript"
const response = await fetch("https://panlytics.net/api/v1/shops/12/exceptions/6410000000017", {
  method: "PUT",
  headers: {
    Authorization: `Bearer ${process.env.PANLYTICS_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "keepAt": 12,
    "neverStop": true,
    "reason": "Sold out every Saturday morning."
  }),
});
if (!response.ok) throw new Error(`Panlytics answered ${response.status}`);
console.log(await response.json());
```

## Response

`200`: The answer, as JSON.

| Field | Type | Always there | What it is |
| --- | --- | --- | --- |
| `productId` | string | Yes | The product the rule is for, as its id: a name sent in the path is turned into its barcode. |
| `saved` | boolean (always true) | Yes | Always true. |

### Example response

```json title="200"
{
  "productId": "6410000000017",
  "saved": true
}
```

## Errors

A refusal is JSON with a `code`, a sentence in `error`, and a `requestId` when the fault is ours. Read the code, not the sentence. Every code is listed on [Errors](https://panlytics.net/developers/security/errors).

| Status | Code | When | What to do |
| --- | --- | --- | --- |
| 400 | `api.invalid` | A path id, a query parameter, a header or a body field is missing or not valid. `detail` names the field. | Read that endpoint in the API reference, correct the field and call again. |
| 400 | `bad_request.said` |  | Change it and try again. |
| 401 | `api.key_missing` | The call had no Authorization header. | Send the key in the Authorization header as Bearer, then call again. |
| 401 | `api.key_refused` | The key is wrong, revoked, past its end, or its maker or company no longer allows it (developer mode off, the maker removed or switched off, or the maker's role lost the developer ability). | Ask the person who gave you the key to make a new one. |
| 401 | `api.wrong_key_kind` | This key does not open these endpoints. | Use the key these endpoints were made for, or ask the person who gave you the key. |
| 403 | `refused` | The key's maker may not do this here: their role lacks the ability, or the shop or category is outside their reach. | Ask the CEO for a role that allows it, or call it for a shop or category the role reaches. |
| 403 | `auth.not_fresh` | This step needs you to prove it is you. | Confirm your password or passkey, then try again. |
| 403 | `refused.demo` | The key belongs to a shared demo account, which may not change anything. | Use a key made in a real company account. |
| 404 | `not_found.said` | Nothing with that id in the key's company. An id of another company answers the same. | Check the id. List the shop or category it belongs to and take the id from there. |
| 429 | `api.rate_limited` | The key made more than 120 calls in this minute. Wait the seconds in Retry-After. | Wait the seconds in Retry-After, then call again. |
| 500 | `server` | Something failed on our side. The answer carries a requestId to quote. | Try again in a minute; if it keeps happening, report it. |
| 503 | `developer.unavailable` | API keys are not set up on this deployment yet. | Report it, and we will switch them on. |