Implement virtual brand tax compliance by configuring separate tax profiles per virtual brand entity on Olo and validating marketplace facilitator tax coverage
Create separate Olo restaurant entities for each virtual brand and assign distinct tax configurations reflecting each brand's menu category tax treatment (e.g. prepared food vs grocery-adjacent items)
For each virtual brand, determine which delivery channel partners (DoorDash, Uber Eats, Grubhub) act as marketplace facilitators for tax in the brand's operating jurisdictions
In Olo's tax settings for each brand entity, set the marketplace_facilitator flag per channel to prevent double-remittance of sales tax
Validate the configuration by placing test orders on each channel and inspecting the order receipt to confirm tax is collected once (either by the marketplace or by the brand, not both)
Set up a monthly reconciliation job that compares tax collected per brand per channel against state filing requirements, accounting for facilitator coverage changes
Document the tax responsibility matrix per brand per channel per jurisdiction for audit purposes
Known gotchas
Marketplace facilitator laws vary by state and change frequently; the matrix of which platform remits tax in which jurisdiction must be reviewed quarterly and after any new state legislation
Virtual brands operating under the same legal entity as the parent restaurant but with different Olo restaurant IDs may still share a single tax filing obligation; the Olo entity split does not automatically create separate tax nexus
Some platforms apply marketplace facilitator tax only above a certain gross sales threshold; brands that cross the threshold mid-year will have a mixed year of self-remittance and facilitator remittance that must be tracked by month
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp