WP to Firebase Pro: WooCommerce Firebase field mapping and push messages

WP to Firebase Pro is a yearly add-on for the free WP to Firebase plugin, which already syncs WooCommerce products, orders and WordPress users to Cloud Firestore or a Firebase Realtime Database. Pro adds two things to that WooCommerce Firebase sync: a field mapper, so the data arrives in the shape your app expects, and Firebase Cloud Messaging (FCM) push messages for new posts, order status changes and messages you write yourself. It costs $29 a year for one site.

From $29 a year. $29 for 1 site, $49 for 3 sites, $99 for 10 sites, billed yearly. 14-day money-back guarantee.

WP to Firebase free vs WP to Firebase Pro

WP to Firebase (free) compared with WP to Firebase Pro. Pro needs the free plugin and keeps every free feature.
FeatureWP to Firebase (free)WP to Firebase Pro
Sync to Cloud FirestoreYesYes
Sync to a Firebase Realtime DatabaseYesYes
WooCommerce products, with variations, images, categories and attributesYesYes
WooCommerce orders (HPOS on or off)YesYes
WordPress users (never passwords or reset keys)YesYes
Full sync in background batches of 50, on a scheduleYesYes
Live updates and deletes a few seconds after a changeYesYes
Skip unchanged items to save Firestore writesYesYes
Named Firestore database and collection prefixYesYes
Choose which fields are sentNo, a fixed set of fields (developers can change it in code with the wpwtf_record filter)Yes, a checkbox per field for products, orders and users
Rename Firebase keys (for example name to title)NoYes
Set a type per fieldNo, default typesText, whole number, decimal, true/false or Unix time
Map nested billing and shipping fields one by oneNoYes
Send custom meta keysNoUp to 30 per data type, each with its own key and type
Block meta keys that look like credentialsNot needed (no meta is sent)Yes, keys with pass, secret, token, session, api_key and similar are refused
Before-and-after preview of the newest itemNoYes, as JSON
Firebase Cloud Messaging (HTTP v1 API)NoYes, signed with the same service account
Segments: topics, or conditions of up to 5 topicsNoYes, checked before they are saved
Push message when a post is publishedNoYes, for the post types you choose, first publish only
Push message when an order status changesNoYes, to the customer's own topic, with no personal data
Compose screen: send now, schedule, or check with FCM without sendingNoYes, with image, link and up to 3 data pairs
Send history with retries, cancel and clean-upNoYes, kept 90 days by default
PriceFree on WordPress.org$29 (1 site), $49 (3 sites), $99 (10 sites) a year

What does WP to Firebase Pro add?

The free plugin decides what each record looks like. A product arrives with fields such as name, price, stock_quantity and images, an order with its totals, line items and billing details. That works for many apps. It stops working when your app already has a schema, when you build a FlutterFlow app around fixed field names, or when you need a custom field that WooCommerce stores as meta.

Pro fixes that without code, and adds a way to talk back to the people using your app. Both parts work with Cloud Firestore and the Realtime Database, and both use the service account you already saved in the free plugin.

  • Field mapper: choose, rename and type every field that reaches Firebase.
  • Extra meta keys: send custom fields such as a rating, a warranty or loyalty points.
  • Push messages: FCM notifications for new posts, order status changes and messages you compose.
  • Send history: every message with its status, the FCM message ID or the error.

How does the field mapper change the WordPress to Firebase data?

Under Settings > WP to Firebase Pro > Field mapper there is one table each for products, orders and users. Each row is one field. Untick a field to leave it out, type a new Firebase key to rename it, and pick a type. Nested billing and shipping fields have their own rows, so you can keep billing.city and drop billing.phone.

Types matter in Cloud Firestore, because a price stored as text sorts as text. The mapper can store a field as text, a whole number, a decimal, true or false, or a Unix time. A value that cannot be converted, such as letters sent to a whole-number field, is stored as empty (null) instead of a wrong number.

Below each table you can add up to 30 meta keys. Order meta is read through WooCommerce's own order functions, so it works whether High-Performance Order Storage is on or off. Keys that look like secrets are refused and never sent.

Before you save, the preview shows the newest product, order or user as JSON, before and after the map. The map applies to full syncs and live updates. Data already in Firebase changes when items are written again, so run Sync now after you change the map. In testing, a second Firestore sync skipped every unchanged record, and only the type whose map changed was written again.

How do Firebase push notifications work from WordPress?

Pro sends messages through the Firebase Cloud Messaging HTTP v1 API, the current API since Google began shutting down the legacy APIs in July 2024. You don't need a third-party push service. FCM itself has no charge on Firebase's free Spark plan or the Blaze plan.

Messages go to topics, not to stored device tokens. A segment is either one topic, such as news, or a condition that combines up to five topics with and, or and parentheses. Your app subscribes to the topics it wants. On Android, iOS and Flutter that is one call in the Firebase Messaging SDK.

Order updates go to the customer's own topic, user_42 for the WordPress user with ID 42 (the prefix can be changed). The app subscribes to it after the customer signs in. Topic names are not secret, so Pro never puts names, emails, phone numbers or addresses in the message: only the order number, status and order ID. Guest orders are skipped, because they have no user ID.

  • New post published: a message to a segment the first time a post of a chosen type goes live. Templates accept {title}, {excerpt}, {author} and {site}. Republishing does not send again.
  • Order status changed: a message when an order reaches a status you choose, such as Processing or Completed.
  • Compose: write a message with an optional image, link and up to 3 data pairs, send it now or schedule it in your site's time zone.
  • Check without sending: FCM validates the message without delivering it.
  • History: every message is stored with its status. Temporary FCM errors are retried up to 3 times, and scheduled messages can be cancelled.

How was WP to Firebase Pro built and tested?

I'm Ali Nawaz, a WordPress developer since 2017, and I wrote both the free plugin and Pro. Pro does not change the free plugin's sync code. It plugs into the wpwtf_record filter that the free plugin added in version 2.2.0, so with Pro switched off the free plugin sends exactly what it sent before. I checked that by exporting the same products, orders and users with and without the change and comparing them.

The field mapper was tested against the real Cloud Firestore emulator from Google's Firebase tools, with WooCommerce 11.3 and PHP 8.5, with HPOS on and off. Realtime Database writes were checked by recording the exact request body the plugin sends.

Push messages were tested against simulated Google endpoints. The tests check the exact URL, headers, sign-in claims and JSON body against Google's FCM HTTP v1 documentation, plus retries, scheduling and cancelling. They have not yet been sent through a live Firebase project in those tests. Before you turn on a trigger, use "Check with FCM without sending" with your own project, then send one message to a test topic on a test device.

Who needs Pro, and when is the free plugin enough?

Stay on the free plugin if your app can read the default fields, you only need products, orders and users in Firebase, and you don't send push messages. It is not a trial: Firestore, the Realtime Database, live updates and scheduled syncs are all free. A developer can also change records in code with the wpwtf_record filter.

Pro is worth it when:

  • Your app or FlutterFlow project expects its own field names and types.
  • You need custom product, order or user meta in Firebase.
  • You want fewer fields in Firebase, for example no phone numbers.
  • Your mobile app should tell customers when their order ships, or tell readers about a new post.
  • You want to send and schedule push messages from WordPress instead of the Firebase console.

How does it compare with other WordPress Firebase plugins?

Most WordPress Firebase plugins focus on Firebase Authentication, so people can log in to WordPress with Firebase accounts. WP to Firebase does not do login. It moves store data to Firebase and, with Pro, sends push messages. Prices below were checked on 16 November 2026.

miniOrange Firebase Authentication sells three yearly plans: $149, $249 and $449. Its page lists Firestore sync of WooCommerce products, orders and subscriptions only in the $449 All-Inclusive plan, which is bought through its sales team. Integrate Firebase PRO by TechCater covers login, Firestore and Realtime Database data, FCM and a WooCommerce extension, but no public price was shown on its shop when I checked. GravityExtra's WooCommerce Firebase add-on ($39 to $169 a year) writes paid orders to Firestore.

WP to Firebase syncs products, orders and users to either database for free, and Pro adds mapping and push for $29 a year. If you need Firebase login, use one of the plugins above alongside it.

How do you set it up?

  • Install the free WP to Firebase plugin, save your service account key and run a first sync.
  • Install WP to Firebase Pro and paste the licence key from your purchase email.
  • Open the Field mapper tab, switch on the map for a data type, adjust fields and check the preview.
  • Run Sync now so the mapped records replace the old ones.
  • For push, add your segments, choose the post types and order statuses that send messages, and test with "Check with FCM without sending".

How much does WP to Firebase Pro cost?

Pro is sold through Freemius, which handles checkout, sales tax and VAT, licence keys and updates. Every plan includes all Pro features and renews each year until you cancel. There is a 14-day money-back guarantee.

If the licence expires, Pro's features switch off and the free plugin keeps syncing with its default fields. Scheduled messages are marked as skipped, not sent.

Yearly price of WP to Firebase Pro, by number of sites
LicencePrice
1 site$29 per year
3 sites$49 per year
10 sites$99 per year

WP to Firebase Pro FAQs

How do I connect WooCommerce to Firebase without code?+

Install the free WP to Firebase plugin, paste a Firebase service account key, choose Cloud Firestore or the Realtime Database and click Sync now. Products, orders and users are then kept in step automatically. Pro adds field mapping and push messages, also without code.

Does it work with a FlutterFlow app?+

FlutterFlow's built-in database is Cloud Firestore, and the free plugin writes to Firestore with proper types. Pro's field mapper lets you match the collection fields your FlutterFlow schema uses. For order push messages, the app has to subscribe to the customer's topic after sign-in, which in FlutterFlow may need a small custom action.

Does Firebase charge for push notifications?+

Firebase does not charge for Cloud Messaging, on the free Spark plan or the Blaze plan. Firestore writes are billed separately above the free daily quota, which is why the free plugin skips items that have not changed.

Does the field mapper change data already in Firebase?+

Only when items are written again. After you change the map, click Sync now in the WP to Firebase settings, and every item of that type is rewritten in the new shape.

What happens when my licence expires?+

Pro's features switch off and the free plugin keeps working with its default fields. Scheduled messages are marked as skipped. Renew the licence to switch Pro back on; your map and segments are kept.

Do I need another licence for a staging site?+

Each licence covers 1, 3 or 10 sites. You can move a licence by deactivating it on one site and activating it on another, so the 3-site plan suits a live store plus a staging copy.

Can I get a refund?+

Yes, within 14 days. You get a full refund if you haven't downloaded the add-on yet, or if a bug makes it unusable and I can't fix it. Freemius handles the refund, and the refund policy has the details.

What do you need to run it?

You need WP to Firebase 2.2.0 or later, with a service account key saved under Settings > WP to Firebase. Both plugins need WordPress 6.2 or later and PHP 7.4 or later, and are tested up to WordPress 7.1. Product and order features need WooCommerce 7.1 or later (tested up to 11.3). The post trigger and user mapping work without WooCommerce.

For push messages, the Firebase Cloud Messaging API must be enabled in your Google Cloud project, and your app must subscribe to the topics you use. Scheduled messages run through Action Scheduler, which ships with WooCommerce, or through WP-Cron on sites without it.