Community

Hi everyone,

We are currently auditing Billsby's plan architecture to transition our traditional vehicle leasing into a hybrid subscription/membership model. Our primary operational deployment handles high-volume Rent a Car Queen Beatrix Airport logistics, which introduces a specific compliance challenge regarding localized airport authority surcharges and terminal concession fees.

Because these regional tourism taxes and airport fees are mandatory but fluctuate based on seasonal flight data and vehicle tiers, we want to avoid creating dozens of static, redundant billing plans.

We are looking for insights on the cleanest workflow to handle this within Billsby:

Option A: Utilizing custom fields and passing real-time location/airport identifiers via the API to dynamically inject the surcharge onto the base subscription invoice at checkout.

Option B: Structuring the localized airport fee as a mandatory, non-optional addon attached to a baseline regional plan.

Has anyone in the mobility, travel-tech, or localized logistics space successfully configured Billsby to handle hyper-local destination fees without cluttering the product catalog? Any advice on API constraints or webhook triggers for this specific logic would be highly appreciated.