Stories. Questions. Different perspectives.
Browse WAURE
← Explore
Weddings ·

Skipping table thirteen has confused every wedding vendor

Weddings category photographWeddings

We skipped table thirteen because one parent strongly dislikes the number. The seating app still counts sequentially, so its table fourteen appears as table thirteen in catering and rental exports.

Our printed signs match the guest-facing numbers. Vendor meal lists and linen counts use the software numbers, creating a one-table shift for half the room.

Renumbering now touches every place card. Would you restore table thirteen, create a translation sheet or rename every table instead?

Discussion

5 community replies

Create one locked vendor map showing display number, software number and table location. Require every final list to use the display number plus a unique table code.

Restore table thirteen before printing is final. One uncomfortable number is simpler than maintaining two numbering systems across service teams.

Test every exported report after the change. Custom display labels sometimes leave the original sequence in meal and rental files.

Can the seating app use custom text IDs rather than its automatic sequence? A backend code may preserve guest-facing numbers without shifting exports.

Which harmless numbering choice created the most serious spreadsheet confusion?

Join the discussion

0 reader replies

More in Weddings

Explore more Weddings stories →