1.11.6

Otto sync / product fetch — SKUs containing % (and DE decimals like 0,5%) no longer break Otto Market product lookups.
Analysis — Period selector gains All time (no date window on sales/returns/ads queries).
Otto monitor — OAuth token refresh works again after SQLModel’s timezone-aware datetime default.

Area	Behavior
Problem	Path `GET /v5/products/{sku}` returns HTTP 400 when the SKU contains `%` (percent-encoding clash).
Fix	Use `GET /v5/products?sku=…` with the SKU percent-encoded (`%` → `%25`, `,` → `%2C`).
Comma trap	Do not append an empty `&sku=` for comma SKUs — that produced a trailing comma in Otto’s self-link and empty `productVariations`.
Fallback	If still not found and the SKU contains `,`, retry once with `,` → `.` (e.g. `0,5%` → `0.5%`).
Quantity	Path quantity calls encode `%` the same way; other SKUs (e.g. `SonyPlaystation5Pro(2)`) keep the original path endpoints.

Area	Behavior
UI	Period → All time on Analysis articles and the sales-stats dialog.
API	`days=0` means no `from`/`to` filter on order/retour/ad queries.
Custom	Custom from/to still capped at 365 days.
Otto ads	SPA ad rollups remain ~90 days; warning shown for All time / long windows.

Area	Behavior
Failure	`UPDATE otto_credentials … Datetime values must have timezone information`
Cause	Naive Berlin `get_berlin_time()` vs SQLModel 0.0.45+ `UTCDateTime` default
Fix	`sa_type=DateTime(timezone=False)` / shared naive type on Otto credentials, related detail timestamps, Plenty credentials

No Postgres migration — columns were already timestamp without time zone.

Redeploy service-multi-repricer and refresh the frontend.
If a % SKU still reports “Product not found on Otto”, confirm the exact seller SKU in Otto Seller Hub.