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 uninstall remove customer CPF/CNPJ or order data?
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.
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.
How do I control field width on a checkout row?
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.
Why did checkout columns look broken after activating 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.
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 layout as desktop. What can I do?
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.
What should I test before enabling block checkout on production?
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.
