Skip to content

Business identification - footer and shortcode

The Business identification module centralises the output of the shop’s business data (name, address, NIP, REGON, email, phone). Polish consumer law (Art. 12 of the Consumer Rights Act and Art. 206 of the Commercial Companies Code) requires e-commerce sellers to publish this information so the customer can identify the counterparty. This module helps you place the data consistently across the footer, order confirmations and legal pages.

All fields come from the polski_general option, populated by the setup wizard:

FieldKey
Company namecompany_name
Addresscompany_address
NIP (Polish tax ID)company_nip
REGON (statistical)company_regon
Emailcompany_email
Phonecompany_phone

Update them under Polski > Setup wizard > Business data.

Go to Polski > Modules and enable “Business identification”. There is no dedicated settings screen. Rendering is controlled per-usage via shortcode attributes or Gutenberg block settings.

[polski_business_info]
[polski_business_info format="inline" separator=" - " show_regon="1" show_label="0"]
AttributeDefaultValuesDescription
formatblockblock, inlineBlock format = one line per field in <div>. Inline = single <span>
separator|any stringSeparator used in inline format between fields
show_label11, 0Whether to prefix NIP / REGON with “NIP:” / “REGON:“
show_regon01, 0Whether to render the REGON line (many shops keep it hidden)

Block name: polski/business-info. Category: Widgets. Supports wide/full alignment. Attributes match the shortcode. Rendering is dynamic (server-side render_callback), so updating business data in the wizard propagates without re-saving the page.

Email templates can reuse the shortcode through WooCommerce filters:

add_filter('woocommerce_email_footer_text', function (string $text): string {
return do_shortcode('[polski_business_info format="inline"]');
});

The email address is wrapped in antispambot() before rendering, so crawlers see an HTML-entity encoded version instead of a parseable mailto.

  • Reading: public (shortcode / block are frontend-safe)
  • Editing the source data: manage_options (setup wizard)
  • Only one business entity - no multi-brand or per-language override
  • No structured-data output (schema.org/Organization) yet - planned for 2.2.0
  • Phone is rendered as plain text, not tel: (avoids unintended click-to-dial on desktop)
  • No per-country conditional rendering (the same data is shown to all visitors)