RaCar Checkout Manager for Brazilian Stores
Adds brazil's input fields to checkout & more. Plugin p/ lojas brasileiras com CPF, CNPJ e outros campos ao checkout, auto-preenchimento de endereços.
Will this break my store?
What the WordPress.org registry says about keeping RaCar Checkout Manager for Brazilian Stores running.
Tested to 7.1
Tested against the WordPress branch in use today.13 days ago
8.0
Your host must be running at least this version.6.5
woocommerce
These must be installed and active first.1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how RaCar Checkout Manager for Brazilian Stores is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
Not enough dataListing transparency
10 / 10Ratings
No one has rated this plugin on WordPress.org yet. That is a statement about the ratings page, not about the plugin — plenty of well-kept plugins never collect them.
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 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é 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). 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 for more details.
Yes, the plugin is fully compatible with WooCommerce’s High-Performance Order Storage (HPOS).
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.
Yes, you can enable or disable individual fields like CPF, CNPJ, RG, and more from the plugin’s settings page.
Yes, the plugin is fully localized and ready for translation into other languages.
Yes, you can enable input masks for fields like CPF, CNPJ, and cellphone to improve the user experience.
Yes, you can disable the autofill feature entirely from the plugin settings (Tab 2: Autofill Addresses). When disabled, no external API calls are made.
No. Uninstall removes plugin options and logs an audit entry when WooCommerce logging is enabled, but user meta (for example billing_cpf) and order meta are preserved so fiscal history and ERP integrations remain intact.
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.
In Checkout Fields (Tab 1), open a field’s settings (cog) and choose Row layout: Full row (one line), Left column, or Right column. Priority controls vertical order only. On classic checkout this maps to WooCommerce form-row-* classes; on Checkout Block it maps to flex width rules generated by the plugin.
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.
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.
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.
Classic checkout: 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 restores two-column widths for fields set to Left column / Right column when themes stack everything full width.
Block checkout: Below ~700px container width, WooCommerce and this plugin stack address fields full width by design (better mobile UX). Adjust Row layout on desktop; mobile stacking is expected.
Use this go/no-go checklist after enabling Block checkout support on Tab 1 (test on your store’s block checkout URL):
- Persistence: Guest and logged-in orders; confirm
_wc_billing/rbsmhao/*,_wc_shipping/rbsmhao/*,billing_*, and_billing_*meta on the order. - Validation: Invalid CPF/CNPJ blocks checkout; optional fields do not block when empty.
- Display: Order admin, order emails, My Account overview, and WooCommerce REST order payload show the same Brazilian data (legacy and Blocks meta).
- PF/PJ: Toggle shows/hides the correct field groups; server validation matches the selected person type.
- Conflicts: With Brazilian Checkout Toolkit active, RaCar block registration stays off and an admin notice explains why.
- Mobile UX: Masks do not jump the caret while typing CPF/CNPJ/phone on iOS/Android.
- Rollback: Disable Block checkout support or add
add_filter( 'rbsmhao_disable_blocks_checkout_support', '__return_true' );— classic checkout and existing orders must remain intact.
Categories
Plugin details
Tags on WordPress.org
Alternatives
Other plugins in the same categories.
Checkout Field Editor (Checkout Manager) for WooCommerce
Fluid Checkout for WooCommerce – Lite
Wallet for WooCommerce
YayPricing – WooCommerce Dynamic Pricing & Discounts
