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.
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 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 API for real-time status updates.
Invoice Generation
If Aggregator generates the invoice and updates Fynd OMS using 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 and POST Shipping Label APIs after polling 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 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 API.
Credit Note Generation
If Aggregator generates the credit note using POST Credit Note API. Alternatively, Fynd auto-generates the credit note upon return acceptance.
Fetch Customer Credit Note
Poll the 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 API.
Refer to our Touchpoints Supported documentation for additional API usage and best practices.