> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/logistics-integration/delivery-partner-integrations/faqs.md). # FAQs ### Overview These FAQs cover common questions about third-party logistics app setup and behavior. ### Which delivery providers can I connect? You can connect supported logistics providers from the **Apps** section. The available list depends on the integrations enabled in your workspace. The structure is designed to support multiple providers over time. ### Does this setup replace the Logistics Core Module? No. The app connection handles provider integration. Store-level delivery behavior still depends on [Logistics Core Module](/whatsapp-commerce/logistics-integration/logistics-core-module.md). ### Can I use the module without a third-party logistics partner? Yes. You can use your own in-shop delivery setup and configure delivery areas, pricing, and charges from the core delivery settings. Use third-party integration only when you want to connect a provider account. ### What happens after I save the API credentials? If the credentials are valid, the provider becomes available for logistics actions. The system can then send shipment or pickup data to that provider. ### What happens if the API credentials are wrong? Provider actions may fail, stay pending, or stop syncing correctly. Check the API key, account details, and provider-side configuration. ### Do pickup days create pickup requests automatically? No. Pickup days only control when pickup requests are allowed. Actual pickup creation depends on your order flow and automation settings. ### What happens if the order is ready on a blocked pickup day? The pickup request may wait until the next valid pickup day. This depends on your operational setup and provider response. ### Why are delivery status updates not syncing? Webhook setup is usually required for automatic status updates. If the webhook is missing or incorrect, tracking updates may not sync back. ### Does one app configuration affect all orders? It affects orders routed through that provider. If multiple providers are used, each provider follows its own app configuration. ### Where can I check delivery details after shipment creation? Open the order and review the delivery data in [Delivery Details in Order (360 View)](/whatsapp-commerce/logistics-integration/logistics-core-module/delivery-details-in-order-360-view.md). ### What should I configure next? After connecting the provider, continue with: * [Fulfillment Workflow](/whatsapp-commerce/logistics-integration/fulfillment-workflow.md) * [Automatically Initiate Request to Pickup](/whatsapp-commerce/logistics-integration/logistics-core-module/automatically-initiate-request-to-pickup.md) * [Automatic delivery assignment](/whatsapp-commerce/logistics-integration/logistics-core-module/automatic-delivery-assignment.md) --- # 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: ``` GET https://help.pickyassist.com/whatsapp-commerce/logistics-integration/delivery-partner-integrations/faqs.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.