Feature requests are reviewed by the Arcus team and may be grouped with similar workflow
improvements. Please do not include passwords, API keys, access tokens, payment details,
or private customer information.
Good requests include
The workflow, page or setting, current friction, expected outcome, frequency, team impact,
and any workaround you use today.
How requests are used
The Arcus team reviews the workflow, checks whether there is already a good way to do it,
and follows up when more detail would help.
Before You Submit
Describe the real workflow, not only the button or field you want. That helps the team avoid building a narrow fix when the better answer is a cleaner flow across orders, purchasing, inventory, fulfillment, accounting, reports, settings, or the customer portal. Useful examples:- “Orders: I need a faster way to spot unpaid orders that are already packed.”
- “Settings: I want clearer controls for which emails customers receive.”
- “Products: kits need an easier way to explain component availability before selling.”
- “Reports: we need a monthly view that compares freight spend to order margin.”
- “Help Center: add a walkthrough for how purchase orders become bills and inventory receipts.”