API Release News November 13, 2026

Here’s what’s new in API that’s been in production since November 13, 2026!

Breaking Changes:

Cash register orders will expose their real sales channel

• Today, an order created on a cash register cash desk returns the GUID of the parent store in salesChannelGuid, and filtering orders by the store GUID also returns orders from all of its cash desks. From November 16, 2026, GET /api/orders, GET /api/orders/{code} and order snapshots will return the cash desk’s own GUID, and the salesChannelGuid filter will match only the channel you pass.
• Action required: If you filter orders by a store GUID to get its cash register orders, include the cash desk GUIDs in your filter as well. If you match salesChannelGuid against known stores, expect new, previously unseen GUIDs.

Zero price will no longer clear a price in the Pricelists API

• Affected endpoint: PATCH /api/pricelists/{id}
• Effective date: 16.11.2026
• Today, sending a literal 0 in data.price.price, data.price.commonPrice, data.price.buyPrice, or data.prices.purchasePrice.price clears the price — the same as sending null. After the change, 0 will be stored as a genuine price of zero:
  • for data.price.price, data.price.commonPrice this means an orderable, free item
  • for data.price.buyPrice, data.prices.purchasePrice.price it is a purchase cost of 0 and does not affect orderability.
  • The only way to remove a price will be an explicit null. Fields you don’t send remain untouched, as before.
• What you need to do:
  • If your addon sends 0 to clear a price, switch it to null before 16.11.2026. Sending null already works today, so you can migrate immediately — no need to wait for the rollout.
  • Also note that a 0.00 value may already appear in GET responses today when a merchant sets a genuine zero price in administration or via CSV/XML import — make sure your integration treats 0.00 and null as distinct values.
• Related change for CSV/XML import and export:
  • The same distinction now applies to product import and export: an empty cell means “no price” and a literal 0 means a genuine zero price. If your integration generates import files, verify it doesn’t write 0 for products that should have no price — especially files derived from older exports, where a missing price was rendered as 0 .
• The updated behavior is described in the Pricelists endpoint documentation — see the PATCH /api/pricelists/{id} description.

New Features:

EET support in API

• A new EET section exposes receipts sent to the tax administration (EET 2.0).
• GET /api/eet/records returns a paginated list of EET records, newest first, with delivery state, last error code and message, warnings and missed-deadline information.
• GET /api/eet/evidence-units returns the e-shop’s EET evidence units (registration places), ordered by identifier.
• See the documentation.

Create suppliers and fetch supplier detail

• Suppliers now have write and detail endpoints, see the documentation.

Webhooks for blog articles

• Three new webhook events article:create, article:update and article:delete, see the documentation.

---

Improvements:

Payload delivery for price list webhooks

• pricelist:create and pricelist:update can now be registered with sendPayload. The payload body is the GET /api/price-lists/{id} response.

Cash desks in the sales channels list

• GET /api/sales-channels now returns cash register cash desks (child in_store channels) in addition to root sales channels. Marketplace child channels remain hidden.
• A new parentSalesChannelGuid attribute was added to the list and both detail endpoints (GET /api/sales-channels/{guid}, GET /api/sales-channels/id/{id}); it is null for root channels and holds the parent store GUID for a cash desk. If your integration treats every in_store channel as a physical store, filter on parentSalesChannelGuid to distinguish stores from cash desks.

---

What we plan in the upcoming days:

New features and improvements in progress, e.g.:

• stock:massMovement webhook — one notification per flush with a payload listing every stock movement, for bulk operations such as imports and multi-item orders
• Asynchronous customer batch update (PATCH /api/customers/batch)

Please note: The plan above is subject to change due to unexpected events or changes in priorities — we do not commit to deliver these outputs and outcomes. Thank you for your understanding.

---

If you have any API-related questions, feedback or requests, please do not hesitate to contact us on api@shoptet.cz. We would love to hear from you!

Post navigation