What we have seen is this: a Shopify order can look commercially complete while funds remain only authorised. When manual review, made-to-order production or split fulfilment takes longer than expected, the capture window can close before anyone owns the decision.
Contact StoreBuilt to design a payment-capture workflow that protects revenue and customer trust.
Table of contents
- Keyword decision
- Treat authorisation as a timed state
- Build the capture queue
- Control fulfilment and exceptions
- Reconcile every outcome
- StoreBuilt point of view
Keyword decision
Primary keyword: Shopify payment capture expiry. Secondary intents include Shopify manual payment capture, card authorisation expiry ecommerce and payment capture workflow UK. Intent is urgent technical-commercial diagnosis. Competitor libraries discuss gateways and checkout conversion; the gap is the operational clock between authorisation and fulfilment.
Treat authorisation as a timed state
Authorised does not mean settled cash. Record the gateway, payment method, authorised amount, timestamp, applicable expiry or capture deadline, currency and risk-review state. Gateway and payment-method rules vary, so do not publish one internal deadline as if it applies universally.
| State | Meaning | Next control |
|---|---|---|
| authorised | funds reserved or approved | review/capture clock |
| partially captured | some value collected | resolve remaining amount |
| captured | payment submitted for settlement | reconcile payout |
| voided | authorisation released | stop fulfilment |
| expired | capture opportunity may be lost | recovery decision |
| failed | collection unsuccessful | hold and investigate |
Use a conservative internal SLA ahead of the displayed deadline. Leave time for staff absence, gateway errors and customer contact rather than scheduling action at the final minute.
Build the capture queue
Group authorised orders by time remaining, value, reason for manual capture and fulfilment status. Every record needs an owner and next action. Alert at staged thresholds and escalate high-value or production-ready orders.
An anonymous made-to-order merchant reviewed every order manually but tracked deadlines in personal inboxes. A team absence allowed several authorisations to expire after production began. A shared queue using transaction timestamps, production milestones and escalation ownership exposed the risk while there was still time to act.
| Queue field | Purpose |
|---|---|
| capture deadline | urgency |
| order value | commercial priority |
| review reason | decision context |
| stock/production state | exposure already incurred |
| customer contact | recovery evidence |
| owner | accountability |
Explore Shopify payment automation for monitored capture and exception workflows.
Control fulfilment and exceptions
Create a hard rule that unpaid or failed-capture orders cannot enter irreversible fulfilment unless an authorised exception exists. Warehouse status, ERP release and Shopify payment status must agree. A tag alone is weak if staff can remove it or an integration ignores it.
Test partial fulfilment, edited orders, increased totals, substitutions, split locations, fraud review, preorders, delayed production and cancellations. Decide whether the authorised amount still matches the order after each change. Do not collect more than the approved and customer-understood amount.
For an expired or failed capture, stop release, preserve the transaction evidence and use an approved repayment journey. Customer messages should clearly explain that payment was not completed without implying blame. Never request card details through email or support notes.
Reconcile every outcome
Reconcile authorised amount, captured amount, refund, gateway fee and payout as separate events. A successful capture is not yet proof of bank settlement. Link exceptions to a stable order and transaction reference so finance can distinguish timing from loss.
Report approaching-expiry value, captures attempted, success rate, failure reason, recovery time, expired amount and any orders fulfilled before payment confirmation. Review by gateway, payment method, store and workflow version. Sudden changes may indicate a gateway configuration or integration release rather than shopper behaviour.
Document who can capture, partially capture, void and override holds. Remove access when roles change and review automation logs. Request a Shopify audit if authorised orders rely on manual memory.
+## Test the full authorisation clock
Build fixtures for each gateway and payment method. Cover full and partial capture, edited value, cancellation, split fulfilment, fraud review, preorder delay and failed capture. Record the transaction’s actual deadline and verify alerts use a safety margin.
Run failure drills: make the gateway unavailable, delay a webhook, retry automation and remove the usual owner. Confirm failed capture cannot appear paid to the warehouse and repeated events cannot collect twice. Support needs an approved recovery message and secure repayment route.
Reconcile test captures through payout and refund, not only the order screen. Grant capture and void permissions narrowly, document the emergency owner and set value thresholds. Review every exception during the first complete authorisation cycle. Reliability means delay, retry and human absence still lead to one explainable financial outcome.
+## A 30-day capture-control rollout
In week one, inventory gateways, payment methods and every reason an order remains authorised. Measure real time between authorisation, review, production and capture. In week two, define internal deadlines with safety margins, build the shared queue and assign primary and backup owners. Document which states block ERP or warehouse release.
In week three, shadow alerts and run controlled failure drills. Compare displayed deadlines with gateway records, test delayed webhooks and confirm retries cannot duplicate capture. Ask support to practise the repayment journey without handling card details. In week four, enable escalation, review approaching-expiry value daily and reconcile every capture through payout.
At month end, separate avoidable expiry from legitimate cancellation, gateway failure and customer decision. Report value as well as order count, since one high-value missed capture can outweigh many routine successes. Review production lead times and risk rules if authorisations routinely approach expiry. The payment workflow should fit the operating model; alerts cannot compensate forever for a review or fulfilment process that is structurally too slow.
+## Questions for the weekly payments review
Ask which authorisations are closest to expiry, why they remain open and whether the same cause repeats. Compare capture status with production and fulfilment release, then sample payout settlement for recently recovered orders. Review gateway errors, delayed events, manual overrides and staff access changes. Check upcoming preorders or long-lead products against expected authorisation windows before selling. Finally, confirm customer recovery links and support guidance still work. A short weekly review prevents a queue from becoming a passive report of revenue already lost.
StoreBuilt point of view
StoreBuilt believes an authorisation is a countdown, not a comfort signal. Make the deadline visible, join it to fulfilment state and give every exception an owner. Revenue is protected when payment operations are designed as deliberately as checkout.