# Pick-At-Store (PAS) Model The Pick-At-Store (PAS) Model allows customers to place orders directly in-store and receive their items on the spot, creating a seamless shopping experience. This model includes structured order flows and API interactions for efficient order processing and return handling. Pick-at-Store Journey Diagram center em Figure 1: Pick-at-Store Order Flows ### Forward Flow Order Placement Customer places an order in-store through the POS or Store OS. Fynd OMS creates the order with `order_type` set to `PickAtStore`. Order Confirmation Use the [POST Order Confirmation](/konnect/channels/erp-wms/api-documentation/orders/post-order-confirmation) API to change order status from `created` to `confirmed`. Items are reserved for fulfillment, preventing further modifications. Order Status Tracking Poll the [GET Order by ID](/konnect/channels/erp-wms/api-documentation/orders/get-order-by-id) API for real-time status updates. Invoice Generation If Aggregator generates the invoice and updates Fynd OMS using [POST Update Invoice](/konnect/channels/erp-wms/api-documentation/orders/post-update-invoice). Alternatively, Fynd auto-generates the invoice upon order confirmation. Fetch Customer Invoice and Shipping Label Aggregator retrieves invoice and shipping label via [Fetch Customer Invoice](/konnect/channels/erp-wms/api-documentation/orders/post-customer-invoice) and [POST Shipping Label](/konnect/channels/erp-wms/api-documentation/orders/post-shipping-label) APIs after polling [GET Order by ID](/konnect/channels/erp-wms/api-documentation/orders/get-order-by-id). Order Completion Order status changes to `handed_over_to_customer` once the customer receives their items. Confirm completion by polling the [GET Orders](/konnect/channels/erp-wms/api-documentation/orders/get-orders) API using `DELIVERED` as an orderStatus filter. ### Return Flow Return Initiation Customer initiates a return at the store. Store begins the return process in their third-party ERP/Store OS/Fynd OMS. Quality Control (QC) Check Store staff performs a QC check to ensure the product meets return eligibility criteria. Return is accepted upon passing QC. Return Status Update Update return status in Fynd OMS to `return_accepted` using [POST Return and QC](/konnect/channels/erp-wms/api-documentation/returns/post-update-return-qc) API. Credit Note Generation If Aggregator generates the credit note using [POST Credit Note](/konnect/channels/erp-wms/api-documentation/returns/post-credit-note) API. Alternatively, Fynd auto-generates the credit note upon return acceptance. Fetch Customer Credit Note Poll the [GET Returns](/konnect/channels/erp-wms/api-documentation/returns/get-returns) API to verify credit note generation. Return Completion Return status changes to `return_completed` once the credit note is processed. Confirm return completion by polling the [GET Returns](/konnect/channels/erp-wms/api-documentation/returns/get-returns) API. Refer to our [Touchpoints Supported](/konnect/channels/erp-wms/touchpoints-supported) documentation for additional API usage and best practices.