What the floor is asking for — invoice-to-ledger posts at Vail Village
Vail Village is where invoice-to-ledger posts runs into purchase orders in chat, and Gore Creek is usually the other pressure the same week, so built automation on the loops that already hurt only helps if it is aimed at that collision.
A build that can survive peak week — a seasonal on/off switch for invoice-to-ledger posts
We would rather install a seasonal on/off switch at Vail Village and stop than decorate a stack, and inventory reorder pings becomes a second loop only when double-booked guides is still true at Gore Creek.
Why the calendar is the spec — invoice-to-ledger posts between Lionshead Village and Golden Peak
Vail Village and Golden Peak are not interchangeable desks for invoice-to-ledger posts, which belongs to the people who work Gore Creek and is why a statewide template fails on a Tuesday in May.
Vail Village can show purchase orders in chat in Vail without us pretending to occupy Vail Village as a shopfront from the Eagle County home base.
What we will not pretend — purchase orders in chat
Acceptance is local when invoice-to-ledger posts no longer produces purchase orders in chat at Vail Village and someone at Gore Creek can explain a seasonal on/off switch without calling us.
Staff who cover Gore Creek in winter and Vail Village in summer should not relearn a product every April, which is why invoice-to-ledger posts needs a seasonal switch even if the first ship is only a seasonal on/off switch.
A direct next step with no catalog of products, timed to the season
Bring the messy workflow first, no rate card on this page, write the constraint in a few lines, name the season that actually hurts.