A Belgian delivery line puts the street name before the house number, then an optional box designation. The UPU guide distinguishes bus in Dutch, bte in French, and box; a bare slash is not a substitute for that designation. The following line contains a four-digit postcode and locality, without a B- or BE- prefix. For cross-border mail, the country occupies its own line. Building, floor or internal routing instructions belong above the delivery line. These distinctions matter when an international checkout offers only one apartment input.
Treat the house-number suffix and the box number as separate fields in a Belgian fixture. A value such as 24A is not the same thing as house 24, box A. Test both the optional unit case and the no-unit case, and confirm that rendering does not introduce a duplicate box label when an imported value already contains one. The illustrated street below is invented to demonstrate the layout. It is not evidence of a real building, and changing its postcode cannot turn it into a verified delivery destination.
Belgium also tests assumptions about language. The UPU says a street name should use a language appropriate to the locality rather than combining translations in a single street field. Keep accented characters and the original street spelling through search, sorting and CSV export. Store an optional translated display separately if your product needs one. A user-facing place name and an administrative region are different concepts; do not force the region into a postal label just because it appears in your database. The Netherlands page illustrates why sharing a language does not mean sharing a postcode format.
This generator uses the Dutch Belgian nl_BE locale with English fallbacks, not a representative sample of all Belgian languages. Its fifteen city anchors cover places across the country, while names and street details come from the same locale pool regardless of the selected city. That can produce a Dutch-style fictional street beside a Walloon locality. The output is useful for checking four-character postcode fields, diacritics and exported record structure, but it is not a source of region-specific residents or verified street records. Use postal reference data for deliverability checks rather than treating a successful generation as validation.
A practical test is to download several profiles, retain their original Unicode strings, and compare the displayed address against the underlying JSON fields. Build the postal label yourself from the relevant fields instead of copying the profile card's generic city-and-region line. For a long company name or a separate building instruction, add that case deliberately to your fixture set; this person generator does not promise coverage of every postal layout. See data and methodology for the difference between geographic anchors and invented street details.