Product Availability Workflows

Nicolas Audet
Nicolas Audet
  • Updated

Overview

A Product Availability Workflow controls what customers see in the checkout when they enter their address. It works alongside Coverage Areas and adds more flexibility to define availability rules, modes, and scheduling options.

Workflows are triggered automatically when a customer enters their location in your white-label gaiia checkout.

What you Can Control

Each workflow helps you tailor what appears in checkout based on location and other inputs. You can configure:

  1. Available Products
    Choose which products or plans are visible for a given address.
  2. Checkout Modes
    Set the checkout mode automatically: ORDER, ORDER_REQUEST, PLANNED or UNSERVICEABLE. Check out these articles for more information about Order Modes and Planned Areas.
  3. Scheduling Settings
    Show or hide scheduling options like Preferred Activation Date or Scheduled Installation.
  4. Appointment Availability
    Customize what scheduling looks like for the customer:
    • Set earliest and latest appointment windows (e.g. 1–30 business days).
    • Define time slot options (e.g. 8:00–12:00 or 1:00–5:00).
    • Choose how many slots a customer must select (1–3).
    • Allow or block weekend scheduling.

How it Works

Each workflow is made up of decision nodes—blocks of logic that evaluate inputs and return outcomes.

Inputs

The workflow uses these data points to make decisions:

  • Address Data: Checks if an address is in gaiia, a Coverage Area, a Planned Service Area, or recognized by a third-party system like VETRO or ArcGIS.
  • Address Metadata: Custom fields like dwelling status or whether a drop is already connected.
  • Coverage and Service Data:
    • Planned Service Area slug
    • Coverage area status (planned, under construction, available, preorder)
    • Order mode (e.g. ORDER or ORDER_REQUEST)
  • Account Type: Residential, commercial, government, etc. Learn more about Account Types here.
  • Product Specifics: Details like technology type or provider linked to the product.

Outputs

The outcome of a workflow depends on how the decision nodes are set:

  • Binary output: For example, “Is the address in a coverage area?” → Yes / No
  • Non-binary output: For example, “Which city is the address in?” → Dallas / Houston / Else

Get Help Setting It Up

The gaiia team can help you design and deploy a workflow that matches your needs and data sources. Contact us at support@gaiia.com 

Was this article helpful?

Have more questions? Submit a request