> For the complete documentation index, see [llms.txt](https://docs.globo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.globo.io/pre-order/integrations/third-party-integration/integrate-with-shopify-flow/faqs.md).

# FAQs

<details>

<summary>Should I notify waitlist customers immediately after restock?</summary>

You can, but only after confirming inventory and operational readiness. It is best to add guard conditions before sending notifications.

</details>

<details>

<summary>Can I use one workflow for all preorder scenarios?</summary>

Technically, yes, but it is safer to split workflows by lifecycle stage (launch, payment, fulfillment, post-campaign) so each flow is easier to maintain and debug.

</details>

<details>

<summary>What is the safest way to change fulfillment states?</summary>

Use a single controlling workflow for hold/open/release operations and avoid multiple workflows changing the same order state in parallel.

</details>

<details>

<summary>How do I reduce duplicate customer messages?</summary>

Use conditions and delay windows, and avoid overlapping workflows that react to similar events without mutual guards.

</details>

<details>

<summary>Should support teams be included in these automations?</summary>

Yes. Every customer-facing automation should have internal visibility so support can answer quickly and consistently.

</details>

***

📩 Need Help? \
\
If you encounter any difficulties during setup, please don’t hesitate to reach out via **chat** or email us at **<contact@globo.io>.** We're always here to help!