Title: RaCar Checkout Manager for Brazilian Stores
Author: Rafa Carvalhido
Published: April 29, 2026
Last modified: May 16, 2026
---
Search plugins
# RaCar Checkout Manager for Brazilian Stores
By [Rafa Carvalhido](https://profiles.wordpress.org/rafacarvalhido/)
[Download](https://downloads.wordpress.org/plugin/racar-checkout-manager-for-brazilian-stores.0.6.1.zip)
* [Details](https://wordpress.org/plugins/racar-checkout-manager-for-brazilian-stores/#description)
* [Reviews](https://wordpress.org/plugins/racar-checkout-manager-for-brazilian-stores/#reviews)
* [Installation](https://wordpress.org/plugins/racar-checkout-manager-for-brazilian-stores/#installation)
* [Development](https://wordpress.org/plugins/racar-checkout-manager-for-brazilian-stores/#developers)
[Support](https://wordpress.org/support/plugin/racar-checkout-manager-for-brazilian-stores/)
## Description
**RaCar Checkout Manager for Brazilian Stores** is a powerful WooCommerce plugin
designed specifically for Brazilian stores. It enhances the WooCommerce checkout
experience by adding essential fields like CPF, CNPJ, RG, and more and allowing
control of all WooCommerce fields. Additionally, it includes an address autofill
feature that uses CEP (Brazilian postal codes) to automatically populate address
fields, saving time and improving accuracy.
O **Gerenciador de Checkout RaCar para Lojas Brasileiras** é um poderoso plugin
para WooCommerce desenvolvido especificamente para lojas no Brasil. Ele aprimora
a experiência de finalização de compra no WooCommerce, adicionando campos essenciais
como CPF, CNPJ, RG e outros, além de permitir o controle de todos os campos do WooCommerce.
Adicionalmente, inclui um recurso de preenchimento automático de endereços que utiliza
o CEP para preencher automaticamente os campos de endereço e bloquenado-os (à escolha
do admin), economizando tempo e aumentando a precisão.
### Key Features:
* **CPF, CNPJ, and RG Fields:** Add and validate these essential fields for Brazilian
customers.
* **Address Autofill:** Automatically fill in address fields based on the CEP entered
by the customer.
* **Customizable Checkout Fields:** Enable, disable, or customize checkout fields
to suit your store’s needs.
* **Input Masks:** Add input masks for CPF, CNPJ, and cellphone fields for better
user experience.
* **WooCommerce HPOS Compatibility:** Fully compatible with WooCommerce’s High-
Performance Order Storage (HPOS).
* **Admin Interface:** Modern and intuitive admin interface for managing settings.
* **Translation Ready:** Fully localized and ready for translation.
This plugin is free and always will be. If it saves you time, consider [buying me a coffee](https://linknabio.gg/rafa_carvalhido_wp)
to support its development.
* **Campos CPF, RG, CNPJ, IE, número da residência, bairro e telefone:** Adiciona
e valida esses campos essenciais para clientes brasileiros.
* **Preenchimento automático de endereço:** Preenche automaticamente os campos
de endereço com base no CEP inserido pelo cliente.
* **Bloqueio de campos de endereço:** Ao preencher os campos de endereço, pode
bloqueá-los ao comando do admin.
* **Campos do checkout personalizáveis:** Habilite, desabilite ou personalize os
campos de finalização de compra para atender às necessidades da sua loja.
* **Máscaras de entrada:** Adiciona máscaras de entrada (pontos e traços) para
os campos CPF, CNPJ, CEP e celular para uma melhor experiência do usuário.
* **Compatibilidade com WooCommerce HPOS:** Totalmente compatível com o High-Performance
Order Storage (HPOS) do WooCommerce.
* **Interface administrativa:** Interface administrativa moderna e intuitiva para
gerenciar as configurações.
* **No seu idioma:** Já vem traduzido para o pt-BR, mas você pode mudar qualquer
texto que aparece para o usuário.
Este plugin é gratuito e sempre será. Se ele economizar seu tempo, considere me
[oferecer um café](https://linknabio.gg/rafa_carvalhido_wp) para apoiar o desenvolvimento
deste e outros plugins.
### External Services
This plugin connects to external APIs to obtain address information based on Brazilian
postal codes (CEP), which is needed to autofill address fields during checkout and
registration. These services are used only when the user enters a CEP during checkout
and the autofill feature is enabled.
### BrasilAPI (Primary Service)
The plugin sends the user’s postal code (CEP) to BrasilAPI when the user enters
a valid CEP in the address field ‘postcode’.
This service is provided by “BrasilAPI”:
https://brasilapi.com.br/docs (terms of use and privacy policy available on their
website).
**What is it?**
BrasilAPI is a free public API that provides Brazilian address
data based on postal codes (CEP).
**What data is sent?**
– Only the CEP (postal code) is sent via a GET request to`
https://brasilapi.com.br/api/cep/v2/{cep}` (e.g., `https://brasilapi.com.br/api/
cep/v2/01234567`). – No personal user data (name, email, order details, or IP address)
is transmitted. – Requests are made only when the user enters a valid CEP and triggers
the autofill feature (via JavaScript on the frontend).
**When is it used?**
– When a customer enters a CEP in the billing or shipping
address field during checkout. – Only if the address autofill feature is enabled
in the plugin settings (Tab 2: Autofill Addresses).
**What data is returned?**
– Street name (logradouro) – Neighborhood (bairro) –
City (cidade) – State (uf)
**Terms and Documentation:**
– BrasilAPI Terms of Service: https://brasilapi.com.
br/#termos-de-uso – BrasilAPI Documentation: https://brasilapi.com.br/docs
### ViaCEP (Fallback Service)
If BrasilAPI does not return a usable address (network error, HTTP error, invalid
JSON, or CEP not found), the plugin tries **ViaCEP** once as a secondary source.
The plugin sends only the same Brazilian postal code (CEP) in a GET request to `
https://viacep.com.br/ws/{cep}/json/` (see [ViaCEP](https://viacep.com.br/)). ViaCEP
is a widely used public CEP lookup service in Brazil. Formal terms of use are not
published as clearly as some larger APIs; the plugin documents this connection here
for transparency and WordPress.org compliance.
**What data is sent?**
– Only the CEP digits in the URL path (same scope as BrasilAPI).–
No personal user data (name, email, order details, or IP address) is transmitted
by the plugin.
**When is it used?**
– Only after BrasilAPI fails or returns no valid address for
that CEP. – Only when autofill is enabled and the customer triggers a CEP lookup
as described above.
### Data Handling
* **No data storage:** The plugin does not store or track any data beyond the single
request to the API.
* **Optional feature:** The address autofill integration is optional and can be
disabled in the plugin settings (Tab 2: Autofill Addresses).
* **Fallback mechanism:** The plugin tries BrasilAPI first, then ViaCEP. If neither
service returns a valid address, the checkout continues with manual entry without
fatal errors.
* **User control:** Users can disable the autofill feature at any time through
the plugin settings.
### Data Transmission
Data sent: Only the Brazilian postal code (CEP) entered by the user.
When: Every
time a user enters or modifies a CEP field (postcode) during WooCommerce checkout
or My Account registration. Conditions: Only when the user manually enters a CEP
value. No data is sent if the field is left empty. Purpose: To automatically populate
address fields (street, neighborhood, city, state) based on the provided CEP. Storage:
The CEP and returned address data are stored locally in the user’s browser session
and WooCommerce order/customer data. Responses come from BrasilAPI when available,
otherwise from ViaCEP; third-party APIs do not retain that payload beyond normal
HTTP handling.
### License
This plugin is licensed under the GPLv2 or later. See the [GNU General Public License](https://www.gnu.org/licenses/gpl-2.0.html)
for more details.
## Screenshots
[⌊Checkout Fields Settings - Customize the fields displayed at checkout.⌉⌊Checkout
Fields Settings - Customize the fields displayed at checkout.⌉[
**Checkout Fields Settings** – Customize the fields displayed at checkout.
[⌊Address Autofill Settings - Enable or disable the address autofill feature.⌉⌊Address
Autofill Settings - Enable or disable the address autofill feature.⌉[
**Address Autofill Settings** – Enable or disable the address autofill feature.
[⌊Frontend Display - Manage settings like priority, classes, label, placeholder,
etc. Blocked fields after CEP search.⌉⌊Frontend Display - Manage settings like priority,
classes, label, placeholder, etc. Blocked fields after CEP search.⌉[
**Frontend Display** – Manage settings like priority, classes, label, placeholder,
etc. Blocked fields after CEP search.
## Installation
1. Upload the plugin files to the `/wp-content/plugins/racar-checkout-manager-for-
brazilian-stores` directory, or install the plugin through the WordPress plugins
screen directly.
2. Activate the plugin through the ‘Plugins’ screen in WordPress.
3. Navigate to **RaCar Plugins > Gerenciador de Campos para Lojas Brasileiras** in
the WordPress admin menu to configure the settings.
4. Customize the checkout fields and enable the address autofill feature as needed.
## FAQ
### Does this plugin work with WooCommerce HPOS?
Yes, the plugin is fully compatible with WooCommerce’s High-Performance Order Storage(
HPOS).
### How does the address autofill feature work?
The plugin uses Brazilian CEPs (postal codes) to fetch address data: it calls BrasilAPI
first, and uses ViaCEP as a fallback if BrasilAPI does not return a valid address.
This data is then used to automatically populate the address fields during checkout.
### Can I disable specific checkout fields?
Yes, you can enable or disable individual fields like CPF, CNPJ, RG, and more from
the plugin’s settings page.
### Is this plugin translation-ready?
Yes, the plugin is fully localized and ready for translation into other languages.
### Does this plugin support input masks?
Yes, you can enable input masks for fields like CPF, CNPJ, and cellphone to improve
the user experience.
### Can I disable the address autofill feature?
Yes, you can disable the autofill feature entirely from the plugin settings (Tab
2: Autofill Addresses). When disabled, no external API calls are made.
### Does order meta stay compatible with Brazilian Market-style integrations (shipping carriers, ERPs)?
Yes. From 0.6.1 onward, person type is stored on orders and customers as **1** (
individual) / **2** (company), matching **Brazilian Market on WooCommerce**. When
checkout ships to the billing address (no separate shipping address), **number**
and **neighborhood** are mirrored into shipping meta (`_shipping_number`, `_shipping_neighborhood`)
when those shipping fields would otherwise be empty—matching what many Brazilian
carriers expect.
Third-party plugins that read the same meta keys (for example **Loggi**, **Correios
Automático Infix**, **Melhor Envio** buyer payloads, **Link Nacional** improved
shipping calculator conventions) continue to work without Brazilian Market installed.**
Melhor Envio** may still show its own admin notice until their plugin explicitly
recognizes RaCar—configure shipping fields here regardless.
### Why did checkout columns look broken after activating the plugin? I still use WooCommerce field classes.
Classic checkout rows often use `form-row-first` / `form-row-last` together with
theme CSS floats. The plugin keeps those WooCommerce classes but changes **which
rows are visible** (PF/PJ toggles) and interacts with WooCommerce scripts that can**
reassign row classes** when country or locale rules change (the plugin also restores
your configured postcode row classes after `country_to_state_changing`). That can
misalign float pairs even though class names match WooCommerce defaults.
### How do I fix overlapping checkout columns safely?
In **Checkout Fields (Tab 1)**, enable **Classic Checkout Layout (Float Compatibility)
Recover floated checkout columns**. It is **off by default** so normal themes are
unaffected; when enabled, it outputs a **checkout-only** rule (`clear: both` on `
form-row-first`) with exclusions for wide rows and the plugin’s three-column helpers.
Test checkout with your theme after enabling; disable again if anything looks worse.
### How should I verify layout after changing float compatibility?
Use the classic checkout page (shortcode checkout). With the option **off**, confirm
billing/shipping look as before. Turn it **on** only on stores that showed overlap;
recheck billing, shipping, switching PF/PJ (when applicable), and changing country
if customers can. Storefront is a good baseline; themes that rely heavily on floats
benefit most.
### On phones my checkout fields stack full width, but I want the same row classes as desktop (form-row-first / form-row-last). What can I do?
In **Checkout Fields (Tab 1)** **Classic Checkout Layout (Float Compatibility)**,
enable **Preserve two-column row layout on small screens** (default **off**). It
applies **classic shortcode checkout only** (not block checkout): under `max-width:
768px` it outputs scoped CSS on `.woocommerce-checkout form.checkout` to restore
WooCommerce two-column widths/floats and this plugin’s three-column helpers when
themes force full-width rows, keeps `form-row-wide` full width, uses `clear: both`
on `form-row-first` (with the same exclusions as float recovery), and slightly reduces
checkout label size (`font-size: 70%`) so labels are less likely to wrap and misalign
paired fields. Test on real devices; disable if your theme looks worse.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“RaCar Checkout Manager for Brazilian Stores” is open source software. The following
people have contributed to this plugin.
Contributors
* [ Rafa Carvalhido ](https://profiles.wordpress.org/rafacarvalhido/)
[Translate “RaCar Checkout Manager for Brazilian Stores” into your language.](https://translate.wordpress.org/projects/wp-plugins/racar-checkout-manager-for-brazilian-stores)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/racar-checkout-manager-for-brazilian-stores/),
check out the [SVN repository](https://plugins.svn.wordpress.org/racar-checkout-manager-for-brazilian-stores/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/racar-checkout-manager-for-brazilian-stores/)
by [RSS](https://plugins.trac.wordpress.org/log/racar-checkout-manager-for-brazilian-stores/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 0.6.1 – 2026-05-16
* Order/customer persistence: read billing/shipping extras from WooCommerce’s sanitized
checkout payload (same `billing_*` / `shipping_*` data used to build the order),
so **new customers** and account-creation checkouts save CPF, number, neighborhood,
etc. to **order meta** and **user meta** reliably for REST (Bling) consumption.
* User meta: invalid CPF/CNPJ values no longer block saving **all** other Brazilian
fields — only the invalid document meta is omitted.
* Order/customer persistence: store `billing_persontype` as **1** / **2** (Brazilian
Market contract); checkout UI still uses pf/pj via `default_checkout_billing_persontype`.
* When shipping to the billing address (no “Ship to a different address?”), mirror**
billing** number/neighborhood into **shipping** meta (`shipping_number`, `_shipping_number`,`
shipping_neighborhood`, `_shipping_neighborhood`) if shipping extras are empty—
helps carriers and integrations that only read `_shipping_*`.
* Admin order edit: **Customer information** block shows each label and value on
the same line (removed the `address` wrapper class so WooCommerce admin CSS no
longer forces `strong` labels to `display: block`).
* New pt-BR translations.
#### 0.6.0 – 2026-05-15
* WooCommerce REST API: exposes Brazilian checkout fields on orders and customers(`
billing.cpf`, `billing.cnpj`, `billing.number`, `billing.neighborhood`, `persontype`
as F/J, etc.) for Bling and similar integrations — no new public endpoints; uses
existing WC REST permission checks.
* Order persistence: mirrors extra field meta as `_billing_*` / `_shipping_*` alongside
existing keys for compatibility with legacy Brazilian Market data.
#### 0.5.1 – 2026-05-15
* Checkout account field validation: fixed required checks for `account_username`
and `account_password` to use WooCommerce account keys (instead of legacy `billing_*`
prefixes), preventing false “required field” errors when those fields are filled
on checkout.
* CEP autofill (classic checkout): while “searching” or “not found” feedback is
shown, the next field row reflows as a full line below the postcode field (Storefront-
like behavior) via a temporary row-break element — no changes to `form-row-first`/`
form-row-last` / `form-row-wide` classes.
* CEP autofill: initial lookup on page load waits until checkout layout is ready(`
updated_checkout` or `window` load) to avoid a brief broken layout flash.
* CEP autofill: manual address lookup runs as soon as 8 numeric digits are entered(`
input` event); non-digits (e.g. hyphen from mask or manual typing) are ignored—
lookup no longer waits for leaving the postcode field (blur).
#### 0.5.0 – 2026-05-13
* Checkout Fields (Tab 1): optional Preserve two-column row layout on small screens(
default **off**) for classic checkout — under `max-width: 768px`, scoped inline
CSS restores `form-row-first` / `form-row-last` and three-column helper classes
when themes stack fields full width; `form-row-wide` stays full width; `form-
row-first` uses `clear: both` (with wide / three-col exclusions); checkout labels
use `font-size: 70%` in that mode to reduce row misalignment; block checkout
unaffected; FAQ entry added
* When plugin Select2 is disabled: SelectWoo/select2 removal is limited to checkout,
My Account, and cart by default so third-party Select2 (theme filters, variations,
etc.) keeps working site-wide
* Developer filter `rbsmhao_force_legacy_global_selectwoo_strip` (returns `bool`,
receives settings array): return `true` to restore the previous site-wide strip
behavior on stores that depended on it
* Checkout Fields (Tab 1) dimensions: when **select height** is set, inline CSS
aligns **text-only** country rows (themes/filters that remove the country `select`
and leave markup inside `#billing_country_field` / `#shipping_country_field` `.
woocommerce-input-wrapper`) using scoped `display:flex`, `min-height`, and optional
select line-height — **not** a global `span.woocommerce-input-wrapper` rule (
avoids breaking other fields)
* Same dimension block: checkout `select.country_to_state` / `select.country_select`
and My Account `select.country_to_state` get native height rules even when the
theme drops `rbsmhao-select-field` on the country row
* Checkout frontend CSS: scoped `clear: both` on `.woocommerce-checkout .woocommerce-
shipping-fields` so “Ship to a different address?” is not pulled beside floated
billing rows (e.g. some Woodmart layouts)
* Birthdate: stored and validated as **d/m/Y** (Brazilian); legacy **Y-m-d** values
in customer meta are normalized on checkout default; input mask treats ISO `Y-
m-d` prefill before applying `dd/mm/aaaa`
#### 0.4.1 – 2026-05-06
* Checkout Fields (Tab 1): added optional field dimension controls for classic
checkout (separate height/line-height for all checkout selects and for text inputs);
empty values inherit theme defaults
* Checkout frontend: unified select sizing model for native WooCommerce selects
and Select2-rendered selects using the same checkout-scoped selectors/tokens (`.
woocommerce-checkout`, `rbsmhao-select-field`) to reduce cross-theme mismatch
* Select2 frontend CSS: removed broad global overrides and reduced reliance on `!
important`; styles are now scoped to checkout/plugin context to lower risk of
theme conflicts
* Checkout layout compatibility: added optional **Classic Checkout Layout (Float
Compatibility)** toggle (default off) with scoped `clear: both` behavior for `
form-row-first` plus exclusions for wide rows and plugin three-column helper
classes
* Documentation: expanded FAQ/troubleshooting with root-cause notes for float layouts(
PF/PJ visibility changes, WooCommerce `country_to_state` row-class changes, and
postcode class restore flow)
* Checkout locale integration: added support for WooCommerce `woocommerce_get_country_locale_base`
and `woocommerce_get_country_locale_default` hooks (priority 20) in addition
to `woocommerce_get_country_locale`
* Locale formatter internals: split callbacks by payload type (full locale map
vs base/default locale fields) and introduced a shared merge helper to avoid
duplicate logic
* Locale field classes: country field class enrichment is now idempotent (`update_totals_on_change`
is appended only when missing), preventing duplicate classes in repeated locale
passes
* My Account: billing/shipping **Edit address** (`woocommerce_billing_fields` /`
woocommerce_shipping_fields`, priority 20) now includes Brazilian extras **Number**
and **Neighborhood** when enabled in Checkout Fields settings (same visibility
rules as checkout via `get_active_fields()`)
* My Account: Checkout Fields **dimension** settings (select/input height and line-
height) and baseline plugin CSS now apply under `.woocommerce-account` as well
as `.woocommerce-checkout` (registration, edit-address, etc.); **Classic Checkout
Layout (Float Compatibility)** remains checkout-only
#### 0.4.0 – 2026-05-04
* Checkout Fields (Tab 1): optional **Classic Checkout Layout (Float Compatibility)**
toggle (default **off**) applies a scoped `clear: both` on `form-row-first` inside`.
woocommerce-checkout form.checkout`, excluding `form-row-wide` and three-column
helper classes; documented FAQ on PF/PJ visibility, `country_to_state`, and postcode
row class restore
* Registration Form Fields (Tab 4): `rff` toggles for `account_username` and `account_password`
follow WooCommerce Account & Privacy (manual username/password), are read-only
in the admin UI with notice + link to WC settings, and are forced on sanitize;`
updated_option` / `woocommerce_update_options_account` keep `rff` aligned when
those WC options change
* Registration: user meta for optional account username/password from the extended
registration form now uses WooCommerce keys `account_username` / `account_password`(
not `billing_*`)
* Checkout Fields (Tab 1): WooCommerce-synced account username/password (`account_username`,`
account_password`) — default settings and the checkout reset action now persist`
enabled`/`required` from WooCommerce Account & Privacy (`woocommerce_registration_generate_username`,`
woocommerce_registration_generate_password`); first-install activation uses the
same default merge base instead of schema-only `enabled => false`
* When WooCommerce Account settings change, stored checkout field flags are reconciled
if `enabled`/`required` for those account fields diverge (hooks: `woocommerce_update_options_account`,`
updated_option` on the two registration options above)
* One Account Per CPF/CNPJ (Tab 3): “Use CPF or CNPJ as login username” (`cpf_login`)
is available only when WooCommerce **Generate account login** is enabled; otherwise
the toggle is off, read-only, with notice + link to **WooCommerce Settings
Account & Privacy**, hidden input forces `cpf_login` off on save, and sanitization
blocks forged POST values
* When WooCommerce disables generated account login (`woocommerce_registration_generate_username``
no`), `cpf_login` is persisted off (`woocommerce_update_options_account`, `updated_option`);
turning WC generation back on unlocks the toggle without auto-enabling the plugin
option
* ROAPC: `cpf_as_username` and duplicate-login checks honour the same WooCommerce
rule; CNPJ path now respects `cpf_login` instead of the non-existent `cnpj_login`
key
#### 0.3.5 – 2026-05-02
* Uninstall: records an informational entry in **WooCommerce Status Logs** (log
source `racar-checkout-manager-uninstall`) with the user performing the uninstall(
when available) and which plugin options were deleted; requires WooCommerce active
and WC logging enabled per store settings
* Uninstall: fires the `rbsmhao_plugin_uninstalled` action so developers can persist
an audit trail elsewhere (payload: `user_id`, `user_login`, `uninstalled_at`,`
options_deleted`)
#### 0.3.4 – 2026-05-01
* Checkout: added `RBSMHAO-checkout-frontend-style.css` (order notes / additional
fields full-width when shipping row float layout breaks)
* Restored ViaCEP as a fallback CEP lookup when BrasilAPI fails or returns no valid
address (same REST proxy `racar/v1/cep/{cep}`)
* Documented BrasilAPI + ViaCEP behaviour under External Services for WordPress.
org transparency
#### 0.3.2 – 2026-04-30
* Restructure of the RBSMHAO_Checkout_Fields class into smaller files, optmizing
the load
- Refactored checkout responsibilities into dedicated modules (schema, settings
normalizer, sanitizer, validators, persistence, address formatter, and field
filter)
* Standardized boolean operators in PHP codebase (`AND`/`OR` replaced by `&&`/`
||`)
* Fixed One CPF/CNPJ registration validation flow that could allow duplicate CPF/
CNPJ registration in some scenarios
* Fixed registration data persistence for first and last names on account creation
flows
* Added `order_comments` management in Checkout Fields Tab with controls for enable/
disable, label, placeholder, and required
* Improved first-activation migration to import existing WooCommerce field settings
from billing, shipping, and order sections (including order notes)
* Registration Form Fields (Tab 4) now lists only billing fields, preventing shipping/
order fields from appearing there
* Added safe key handling for ROAPC `rff` reads in Tab 4 to avoid PHP `Undefined
array key` warnings on partial/legacy settings arrays
* Added synchronization between Checkout Tab (Tab 1) and ROAPC settings so `rff`
follows `persontype`, CPF/CNPJ toggles, and `company_as_name`
* Added PF-only guard: when `persontype` is PF and Billing Company is disabled,`
company_as_name` is automatically turned off and `rbsmhao_one_cpf_settings[rff][
company]` is forced to `0` on save
* Added Tab 4 blocked-field behavior and contextual tooltips for:
- `first_name`/`last_name` when PJ-only + Company as Name is enabled
- `company` when PF-only + Billing Company is disabled
* Improved Tab 4 accessibility by associating text labels with their form controls
via matching `for`/`id` attributes (fixes DevTools warning: “A `