Approve product changes before they go live
Edits to a product must be reviewed and approved before they're published to your product reference APIs.
When you edit a product in the Product Portal — for example, adding applicability conditions to a discount or updating rate details — the change doesn't take effect publicly straight away. Product changes go through a review and approval workflow, and the published version of the product stays as it was until the update is approved.
Why the API and the Console can differ
The Product Portal shows your working version of a product, including draft edits. Your product reference APIs serve the last approved and published version. Between making an edit and approving it, the two can legitimately show different data:
- Fields you've just added or changed appear in the Console but not yet in the public API response.
- Conversely, if a draft is in progress, the API continues serving the previously approved values.
Once the update is approved and published to Production, the Console and the API are back in sync.
How to publish a change
- Open Product Portal in the Fiskil Console and edit the product.
- Save your changes — they're held as a draft and deployed to Staging, where you can validate them.
- Select Request approval to submit the draft for review by an authorised approver on your team.
- Once approved, the change is published to Production and served by your product reference APIs. Team owners can use Approve and Apply to approve and publish in one step.
Check the pending state
Products with unpublished edits show as drafts awaiting approval in the Product Portal. To confirm what's actually being served, use the Test API button in Product Portal to call Get Products or Get Product Detail against Staging (your draft) or Production (the live, approved version). See Testing your Products API.
Edited a product but the public data hasn't changed?
Check whether the update is still awaiting approval. If a change has been approved and published but still isn't reflected in the API, contact support with the product ID.
For the full workflow, see Creating products in the developer documentation.