> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/customer-account-portal/order-history.md). # Order history View your past orders within the Smartrr customer portal. Customers can view all their order history orders for *both* subscription and one-time purchases from their Customer Account Portal. Once logged in, they'll land on our portal homepage. Customers can view their order by year under the **Order History** section.
Screenshot of the customer portal, highlighting the "Order history" section. Below this section, you will see the "Past orders" subheading. Below the subheading are the orders grouped by dates. Click on an order's card to view additional details.
The following badges can appear on each order mini-card to indicate the status of the order: * Processing * Shipped * Gifted * Refunded By clicking on the order mini-card, the customer can view all details associated with the order – including tracking and carrier information if the order has been shipped.
Screenshot of an expanded past order. Showing the items in the order, the address, prices and card used.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.smartrr.com/docs/support/customer-account-portal/order-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.