Tbilisi and the regions: splitting sales without inventing a story

Georgian trading companies often want a page that says Tbilisi versus the rest. Sometimes the ledger can carry that page. Often it cannot. The difference is whether a customer in Kutaisi is actually coded as Kutaisi, or whether they live inside a Tbilisi warehouse account because that is where the invoice is raised.

What we will draw

If the extract has a region, city, or route mark that the sales office recognises, we will draw it. We will also show how much of the book sits in “unmarked” so the room can see the hole. A territory page that silently dumps the unmarked remainder into Tbilisi is a fiction, and we will not print it.

Vans and warehouses

A van that leaves Gldani on Monday and returns on Thursday is not a region. It is a route. If you want a regional cut, we need the drop points, not the depot. Some clients keep drop points. Many keep only the van number. In the second case we can draw a route page and we will label it as a route page. We will not colour it like a map of Kakheti.

Shared codes

Adjara is the example we use in intake because it happens so often: Batumi hotels and inland wholesale sharing one customer code. Until that is split, a “coastal” review is a wish. We would rather delay the Channel and Territory Review than brief a coastal story that the invoice cannot defend.

How the briefing should use the page

When the cut is honest, the territorial argument becomes practical: van time, stock at the regional warehouse, who is allowed to grant terms outside Tbilisi. When the cut is dishonest, the argument becomes personal — whose memory of last summer in Telavi is right. We are hired to keep the second kind of argument off the table.