Review Order Payments, Returns, Tickets, and Timeline

Investigate linked post-purchase activity without confusing operational records with external settlement.

Before you begin

Open the exact order and verify its organization, identifier, customer, currency, and line items. Access to Returns or Communications may be required to open linked records. Decide whether the investigation concerns payment state, a return, a support ticket, or event timing.

How it works

The order detail page separates linked information into focused panels. Payments describes supported transaction or refund evidence. Returns lists records linked to the order. Tickets connects customer-support work. The timeline orders supported activity so users can reconstruct what CapitalOS recorded and when.

Step-by-step

Open the order and confirm its header information.
Review the payment panel for supported amounts, currencies, states, and timestamps.
Compare refund evidence with related return records; they represent different concepts.
Open Returns and verify SKU, reason, status, stage, and refund context.
Open Tickets and follow the case to Communications when authorized.
Review the timeline from oldest to newest and note each event source.
Compare timing with source synchronization and customer communication.
Document unexplained differences using identifiers and timestamps, not sensitive customer data.
Return to the relevant source module for corrections or follow-up.

Check your result

You can distinguish the order’s commercial state from its return workflow and support activity. Linked records open the correct organization context, and the timeline provides a coherent sequence without being treated as a payment-provider ledger.

Common problems

A refund and return do not match: they may have different amounts, dates, partial states, or processing timing.

A return is missing: search Returns by order and SKU, then check whether it was linked correctly.

A ticket link fails: verify Communications access, ticket synchronization, and organization ownership.

The timeline lacks an expected event: not every external event is represented; inspect the source and supported synchronization.

Permissions and data notes

Panels inherit Orders access, while linked modules can apply additional permissions. Payment and customer context is sensitive. Use external commerce or payment records for authoritative settlement and CapitalOS for operational coordination.