If you run a food truck, a mobile coffee cart, or any mobile food vendor in Arizona, the hardest part of Arizona food truck sales tax is not the rate math — it is location. Transaction Privilege Tax (TPT) is reported by jurisdiction, so every sale has to land under the correct AZDOR location code and business code before your return is right. Miss that, and you are looking at manual jurisdiction lookups, a wrong multi-jurisdiction filing, and notices from the Arizona Department of Revenue. This guide walks through how mobile vendor TPT location mapping actually works, and how CactusComply automates the messy part.

Watch: food trucks and Arizona TPT location mapping

One truck, many jurisdictions — but only one location code

Here is the rule that trips up most vendors. According to guidance from the Arizona Department of Revenue, a mobile vendor receives only one AZDOR location code — the three-digit code (for example, 001) tied to the headquarters address on your TPT license. You do not get a separate location code for each city you visit. That single code goes on every city line of your return.

The distinction to remember: a location code identifies your headquarters (one per mobile vendor), while a region code identifies where each sale was sourced. Your return carries one location code but multiple region codes — one for each city where you actually did business. You still owe a municipal license fee for each city you operate in, and fees vary by jurisdiction, but paying a new city fee never creates a new location code.

The mapping pipeline: from a messy POS export to the right code

Point-of-sale exports almost never carry a clean AZDOR location code. A Square or Stripe file might list a plan name, an item category, a raw address, or nothing usable at all. CactusComply closes that gap with two layers working together: fuzzy location matching and rule-based assignment. Together they turn a raw transaction into a correctly sourced line on your Arizona TPT return.

Fuzzy matching scans all of the columns in your upload — not just the address field — and compares them against your known locations and their learned aliases. A high-confidence match is assigned automatically and remembered as an alias, so the next upload is instant. A borderline match is surfaced for a one-click confirmation instead of a silent guess. On top of that, rule-based assignment lets you say things like “sales in this date range at this event map to this jurisdiction and this business code,” which is exactly how a food truck’s real week looks.

Restaurant vs retail: two sourcing rules on one truck

Food trucks often carry two business codes at once. Under Arizona Department of Revenue guidance, restaurant sales (business code 011) are sourced to where the truck is parked — the truck itself is the premises. Retail sales such as merch (business code 017) are sourced to where the order is received. CactusComply keeps those classifications separate so each stream lands under the right code, instead of everything defaulting to one bucket.

Legitimate mobile-vendor patterns vs. a genuine mismatch

Here is the subtlety that generic tax software gets wrong. For a mobile vendor, the POS “home” location differing from where a sale physically happened is usually legitimate — a food truck registered to a home-base code will show sales all over the map, all reporting under the same location code. That is exactly correct, and it should never be flagged as an error. CactusComply distinguishes that expected mobile-vendor pattern from a genuine mismatch that actually needs your attention.

The payoff is simple: less manual jurisdiction lookup, a correct multi-jurisdiction TPT return, and fewer notices from the Arizona Department of Revenue. You file it right, automatically — no chasing codes row by row, and no false alarms on sales that were correct all along. That is the difference good food truck tax software in Arizona makes.

Stop mapping jurisdictions by hand

Upload your POS export and let CactusComply map every sale to the right AZDOR location and business code. See it work on your own numbers before you file.

Frequently asked questions

Do food trucks pay TPT in Arizona?

Yes. Food trucks and other mobile food vendors owe Arizona Transaction Privilege Tax on their sales, and they report it by jurisdiction. You must also hold a TPT license and pay a municipal license fee for each city where you do business. The key is sourcing each sale to the correct city so the tax is reported accurately.

What location code does a mobile vendor use?

A mobile vendor uses a single AZDOR location code — the three-digit code tied to the headquarters address on the TPT license (often 001). Per Arizona Department of Revenue guidance, that same code is used on every city line of the return. You do not get a separate location code for each city; instead, each city is identified by its own region code.

How do food trucks file TPT across multiple cities?

One TPT return carries your single location code plus a separate region-code line for every city where sales occurred. Restaurant sales source to where the truck is parked; retail merch sources to where the order is received. CactusComply builds those multi-jurisdiction lines for you from your POS export, so the food truck TPT filing in Arizona is assembled correctly instead of by hand.

Why does my POS show a different home city than where I sold?

For a mobile vendor, that is normal and legitimate. Your POS is registered to a home-base location, so sales made across many cities still trace back to that home code — and they should report under your single location code. CactusComply recognizes this expected mobile-vendor pattern and does not flag it as an error, while still catching genuine mismatches like a code that is not in your profile.