Italy's CIN: Where the Code Has to Be Shown

A national identification code is only useful if it shows up where guests and platforms can see it. Placement is the part hosts get wrong.

Last updated: October 5, 2026

A code only works if it's where people look. A national identification code is easy to obtain and easy to misplace, because its value depends on it appearing where guests and platforms can see it. Placement, not paperwork, is the part hosts get wrong.

Key Takeaways

• A code identifies a unit, not a host. Each listing carries the code that belongs to its own registration.
• It has to appear in more than one place. The listing, the confirmation, the property and your records each serve a reader.
• One source of truth keeps copies in line. Hold the code with the unit, then make every channel match it.
• Changes are where alignment breaks. A new name or unit type can move a code out of date on one surface.
• Confirm the required places locally. What must be shown, and where, is set by the authority and each platform's terms.

What the code identifies

The code is an identifier. It ties a specific listing to a registration, so a guest, a platform or an inspector can tell one unit from another.

It isn't a rating, and it isn't a licence in disguise. It's a reference number that says which registered property a listing refers to. That's the whole job, and it's a narrower one than hosts sometimes assume.

Because it identifies a unit, it belongs to that unit. Two listings need two codes, even when one host runs both. The number isn't a host badge you can carry from property to property, and treating it as one is where the first mistake usually starts.

That sounds obvious until a host reuses a code across a portfolio, or copies last year's number onto a new listing. The number looks right and points to the wrong place, which is worse than a missing one because it's harder to spot.

A second check follows from the first. A code should match the listing it's shown on, which means the code and the listing have to be read together. A code that's current but attached to the wrong page causes the same confusion as an out-of-date one.

A code that's wrong is different from a code that's missing. A missing code is an obvious gap. A wrong one looks complete, which is why it survives longer and costs more to untangle. Keep the code short and exact, too, because a close copy is still a wrong copy.

A code also isn't a substitute for the registration behind it. It points to a record; it doesn't replace it. If the registration changes, the code follows, which is why the two should always be kept together.

Where it is expected to appear

The code is expected to show up in more than one place, and each place serves a different reader.

On the listing, it tells a guest that the property is registered. In the booking confirmation, it ties the stay to the unit. At the property itself, it connects the physical place to the record. Your own files need it too, so the listing, the confirmation and the property all point to the same registration.

Think of the code as travelling with the stay, from the search a guest runs to the door they open. Every surface on that journey is a place someone could look, and each one is a chance for the number to be missing or wrong.

Where exactly it must appear, and in what form, is set by the local authority and by each platform's own terms. Those can differ, so read both rather than assuming one covers the other.

A code that shows in one place and not another is the common failure, and it's also the one an inspector or a guest is most likely to notice first. It's rarely a deliberate omission. It's usually a page that was updated a year ago and never revisited.

It helps to think about what a guest actually sees. They don't read your file. They read the page in front of them, and the page is where the code has to be. Written down, the four surfaces are easy to check. In the abstract, they're easy to skip.

The order of the check is simple: the listing, then the confirmation, then the property, then your own file. If all four carry the same code, there's nothing to fix.

Keeping it aligned across channels

Most hosts don't list in one place, and that's where alignment slips.

Each channel has its own listing page, its own fields and its own update cycle. A code added to one and forgotten on another creates a mismatch that stays invisible until someone checks. LOCALSBNB connects four OTAs, Airbnb, Booking.com, Agoda and Trip.com, and shows each connected channel's source price and status on one calendar, so you can see the channels you're keeping aligned.

The habit that prevents drift is a single source of truth. Keep the code with the unit in your own records, then treat every channel as a copy that has to match. When you change a detail, change it everywhere in the same sitting, and note the date.

It also helps to decide, in advance, who owns the check. On a small portfolio it's you. On a larger one it may be a co-host or an assistant, and the job needs a name attached to it, or it quietly becomes nobody's.

A channel you updated yesterday and forgot today is the one that causes the problem, because the mismatch sits there quietly until it's read. The cost of noticing late is almost always higher than the cost of checking early.

Updates should travel in one direction. Make the change in your own record first, then push it outward, so every surface copies a source rather than a copy. If two people manage the paperwork, agree on the order of the update and write it down, because most mismatches come from two people fixing the same thing in a different sequence.

What to do when a listing changes

Listings change. A new unit, a renamed property, a switch from a whole home to a room: each one can affect the code.

Work through it in order. First, decide whether the change needs a new code or a correction to the existing one, and check the local requirements if it isn't clear. Second, update the listing page, the confirmation and your own records together. Third, keep a short note of what changed and when, because a note answers a question faster than memory does.

You can see your connected channels in one view at localsbnb.com. The point of all this is quiet. A code that's current in every place it appears doesn't draw attention. One that's stale does, and by the time it's noticed, fixing it usually means explaining the gap as well.

Treat the update as finished only when all four surfaces agree. A listing page that carries the new code and a confirmation that carries the old one isn't half-done. It's a mismatch, and a mismatch is what gets questioned.

Keep the note with the listing, not in a folder somewhere else. A record that lives beside the thing it describes is the one that's still there when it's needed. And re-check the whole set once a season, because the quiet errors are the ones that wait. Set a date rather than waiting to notice, since the errors that matter are the ones nobody is looking for.

Price isn't part of this, but the same discipline applies to it. The code and the rate are both facts about the listing, and both stay true more easily when there's one place they come from.

FAQ

Does every listing need its own code?

Yes, a code identifies a specific property, so each listing carries the one that belongs to it. Two listings normally need two codes, even under one host. Confirm the local requirements for your case.

Where should the code be shown?

It's expected to appear where guests and platforms can see it, and the exact places are set locally and by each platform's terms. Check both, because they can differ. If they do differ, the stricter reading is the safer one to work to.

What if I change a listing's name or unit type?

Treat it as a change that may affect the code. Check whether it needs a new code or a correction, then update the listing, the confirmation and your records together.

The code is the easy part. Keeping it in the right place, on every surface, is the work. Get the placement right once and it stays quiet. If you'd like to keep an eye on your connected channels while you do it, it's worth a look at localsbnb.com.

---

This guide offers general advice for hosts. It isn't legal advice. Rules change over time and differ by place, and platform terms can change too, so check the current requirements of your local authority and the current terms of each platform you use.