Order Management Plugin API
Order Management Plugin API
An order management plugin API for teams building installable extensions that need order lookup, refund context, and post-purchase actions on one workflow record.
Teams searching order management plugin APIs usually need an installable extension model plus a real order system of record they can use for lookup, follow-up, and post-purchase workflows.
Flint gives plugins a public partner-app install model and a semantic order object they can read instead of reconstructing order meaning from a payment event stream.
Order lookup, hosted collection surfaces, refunds, and invoice follow-up all sit on one platform, which makes post-purchase extension logic less brittle.
Because the order is durable, plugins can work on the same record support and operations teams already trust later.
Use This Platform Shape When
The extension needs one workflow record for order lookup, hosted follow-up, refund context, and later support-side actions.
Your team is building post-purchase logic that becomes brittle if it has to reconstruct the sale from payment events and separate app tables.
Merchant-installed extensions should act on the same order record support and operations already trust later.
Order lookup inside an extension
Read the semantic order record directly after merchant install instead of correlating processor objects, app events, and frontend context manually.
Hosted follow-up after purchase
Launch invoice or other hosted recovery flows from the same order lifecycle when the buyer still has a balance or needs later collection.
Post-purchase support workflows
Let the plugin inspect refunds, payment state, and order history before deciding what operator or customer action makes sense next.
Extension logic on a durable record
Keep plugin automation grounded in the order rather than making every post-purchase action depend on payment metadata and internal joins.
Choose Something Narrower When
Implementation References
Reference the platform-level surfaces
Related Pages
Explore refunds, plugin installs, and broader ecommerce extension workflows
These pages connect post-purchase plugin logic to the order, refund, and install surfaces it depends on.
Returns and Refunds Plugin API
Use this when the order-management extension is primarily about post-purchase refund and return behavior.
Ecommerce Plugin Payments API
Go broader when the plugin needs payment, checkout, and install behavior beyond post-purchase order operations.
Refunds API for Order-Based Payments
Useful when the immediate technical question is refund semantics rather than the plugin architecture around them.