How to turn your WooCommerce store into a mobile app.

1. Decide what your shopping app needs to do

Begin with the journeys your customers use most: discovering a collection, finding a product, choosing a variation, saving a favorite and completing a purchase. A focused retail experience is easier to explain, maintain and improve than an app that tries to reproduce every page of a website.

List your product types, checkout fields, shipping rules and essential payment providers. Check how customer accounts and guest checkout are configured. If you sell subscriptions or bundles, or rely on a custom checkout extension, raise those requirements before choosing an app integration.

WooApp supports a Flutter storefront for simple and variable physical products. The compatibility handbook sets out the version requirements and product scope, so you can compare it with your actual store.

2. Prepare your products, categories and delivery rules

A mobile app uses the quality of your store data. Give each product a useful name, clear primary photo, gallery images and a description that answers buying questions. Check that variation prices and stock are complete. Assign category images so the browse screen gives customers a visual way into your catalog.

Configure currency, taxes, allowed countries and shipping zones in WooCommerce. Try addresses in the regions you serve and make sure there is an appropriate delivery method. Your app should display the store’s totals and eligible rates rather than inventing a separate shipping calculation.

• Keep important product details readable on a phone.
• Use accurate stock and purchasable variation combinations.
• Check coupon conditions and sale prices.
• Prepare real contact, privacy and terms pages for your business.
• Make sure WordPress can deliver account and order emails.

3. Install the WooCommerce app plugin

Extract the complete WooApp buyer download. Inside it, locate the WordPress plugin ZIP. In your WordPress administration area, choose Plugins → Add Plugin → Upload Plugin, upload that inner ZIP and activate it.

Open WooApp → WooApp and check the setup status. The app’s public discovery endpoint lives at /wp-json/wooapp/v1/bootstrap under your WordPress address. A working discovery response confirms that the app can obtain store configuration.

The installation walkthrough includes screenshots of the upload screen and WooApp status page. The plugin is installed from one ZIP; the complete buyer archive and Flutter source ZIP are not WordPress plugins.

4. Make the app look like your business

Open WooApp → General settings to select the in-app logo, its size, your header tagline, a font style and a complete color palette. These settings style the shopping experience across screens.

Then curate the home page. In the visual builder, search for products by name or SKU, add them to a section and choose a grid, carousel or compact list. Drag sections to set the browsing order. Add image or video banners and choose their destination through product/category search.

Think of your first screen as an edit of the store rather than the entire warehouse. Lead with a clear hero, a useful category strip and a few focused collections. Saved content changes appear after the app refreshes; they do not require a new app build.

Your installed app’s name and launcher icon are separate platform settings. Your developer applies those to the Android/iOS projects as part of your branded release.

5. Connect your store to the Flutter source

Your developer extracts the Flutter source and supplies the store’s canonical HTTPS URL at build time. The address should point to the WordPress installation, including a subdirectory where applicable. Do not append an administration or REST API path.

flutter run -d chrome --web-port 8090 --dart-define=STORE_URL=https://your-store.com

Customers never select a store themselves. Your app opens your configured storefront directly. Your merchant credentials are not entered into a customer-facing connection screen.

A browser preview lets you review the visual experience and COD checkout before moving through the platform release workflow. Its origin needs to be allowed by your store’s CORS configuration. The Flutter integration guide explains the source and connection model in more detail.

6. Configure the payment methods you want to offer

Cash on delivery follows the WooCommerce COD method and its restrictions. Stripe and PayPal use dedicated native app adapters configured under WooApp → Native payments. Your website gateway plugins do not automatically supply the native app configuration.

Set matching provider credentials, mode and webhooks. Your developer aligns the app’s return schemes with its application identity. The backend coordinates the order and confirms provider state; the app presents the approval flow.

Read the native payment guide for the distinction between store rules, provider approval and server-side confirmation. If you need another provider, share its developer documentation with item support so the integration can be assessed.

7. Prepare your Android and iOS releases

Choose your app identifiers, add your launcher assets, configure private signing and set the version/build number. Build the app against your production store address, then work through your merchant launch checklist and the relevant platform submission process.

For Android, the handbook covers upload signing and app-bundle builds. iOS uses macOS, Xcode and your Apple team. Each platform requires its own developer account and listing materials. Include accurate app screenshots, support details and privacy information for your business.

Use the Android release chapter, iOS release chapter and merchant launch checklist as your working reference. App-store review and publishing remain part of your own account’s release workflow.

What changes after the app is published?

Continue managing products, prices, stock, coupons, shipping and orders in WooCommerce. Curate new home collections and banners in WordPress as your merchandising changes. Your team can develop further app features through the supplied Flutter source.

Plan a new build when changing native code, platform identity, launcher assets or the connected store URL. Keep your signing materials backed up privately so future app updates remain under your control.