Skip to content
Changelog

Week of July 20, 2026

2 changes to the Flint API, SDKs, and docs, newest first, from July 22, 2026 to July 22, 2026. The newest changes are on the changelog.
  • Breaking change
  • API
  • Inventory

Multi-location inventory, allocation, and reservations#

Inventory has its own API. Stock is tracked per location, demand is routed across locations, and checkout holds real claims instead of decrementing a counter.

  • Inventory API: inventory items and per-location levels, adjustments, safety stock, policies, transfers, counts, and merchant-owned reservations. Read levels to inspect stock; create a reservation when your integration needs to hold it.
  • Locations API: create and manage locations, publish their geography, and enable them for inventory. Identity, geography, and the inventory block are versioned independently so concurrent writes cannot silently overwrite each other.
  • Allocation policies: rank locations into priority groups to decide which one serves demand. Single-location merchants can skip policies entirely and route to a fixed location.
  • New webhook events use the inventory. prefix, alongside order.inventory_exception.created and order.inventory_exception.resolved. See the event catalog.

Breaking: product variants no longer carry their own stock count. quantity_available and enforce_inventory_limit have been removed from ProductVariant. A variant now declares inventory_tracking (not_tracked or tracked) and points inventory_item_id at an inventory item whose quantities live on per-location levels. Tracking is never inferred from a product being physical, so a variant you do not explicitly mark tracked sells without a stock check.

Idempotency keys are required on quantity-changing commands. Adjustments and reservation transitions reject a request with no Idempotency-Key. Flint will not generate one, because a generated key cannot protect the case that matters: the request succeeded and you never received the response. Reusing a key with identical input returns the original result and its original level projections.

  • Breaking change
  • Payments
  • API

One all-in processing fee on every payment#

Superseded by Dispute fees follow the money deducted from your balance.

Payments now report a single Flint processing fee, and the fields around it are provider-neutral.

  • processing_fee_money on payment intents replaces platform_fee_money. It is Flint's complete all-in price to process the payment, not a provider cost with a markup on top, so your net is captured_money minus this one field. The fee is final at card capture or ACH success; canceled payments and failures before success have none, and refunds do not return or revise it.
  • Balance transaction fee_money is documented as Flint's own fee on the movement. Refund, dispute, and return entries carry no Flint fee; an instant payout carries its own.
  • processor_fee and flint_fee balance transaction types are no longer part of the public ledger. What Flint pays its providers is Flint's cost and never appears as a deduction on your payments.

New Processing fees and Reconciliation guides cover the fee lifecycle and matching deposits back to the ledger.