Description
Reach more buyers in Chile without running a second store.
Moku is a Chilean marketplace. This plugin connects your WooCommerce store to it: your products and their photos come into Moku as private drafts, and their stock and prices keep up with your store. Once Moku opens sales for your store, you publish the products you choose, and every sale on Moku arrives in WooCommerce as a regular order.
Moku opens sales to WooCommerce stores in stages. The WooCommerce page in your Moku account shows whether your store can sell yet and what is missing.
Watch a store connect in under three minutes (video in Spanish):
Your WooCommerce store stays in charge. Connecting changes nothing in it, and you review each step in Moku before anything is published or sold.
What you get
- A free check of your store, no account needed. WooCommerce > Moku reviews how your WordPress runs (pending updates, HTTPS, scheduled tasks, database tables) and what your published products lack for buyers and couriers: price, photos, description, weight, category, names in capitals and stock that is not counted. Each finding links to the product to fix, and nothing leaves your WordPress. You choose which checks run and the minimum photos and description length.
- Free shipping tools for every order, no account needed. An «Envío» box on each order for the courier and tracking number, a column with both in the orders list, a «Copiar datos» button for the courier’s app or form, address labels («rótulos») printed one by one or in bulk at 10×15 cm, 10×10 cm or two per letter or A4 sheet, and the courier, number and a tracking button in WooCommerce’s «Pedido completado» email. Blue Express, Chilexpress, Starken and Correos de Chile come ready, and you can add your own couriers. Each tool can be turned off, and you choose what the label shows and what the email says.
- Free cart reminders, no account needed. When a shopper types their email at checkout and leaves, your store sends them one reminder email (in your WooCommerce email design, with today’s prices and a button back to their cart). If they don’t come back, WooCommerce > Moku > Carritos tells you, and you can write to them once by WhatsApp from your own phone, with the message ready, when they ticked the box allowing it. Off until you turn it on. Checkout shows a short notice with «No quiero» under the email field, or an unticked box if you prefer to ask permission; WhatsApp always needs its own unticked box. Sensitive categories (health, intimate products and similar) get a reminder that names no product and no WhatsApp. A request to stop, by email link, «No quiero» or WhatsApp, blocks every later reminder. «Los recordatorios se guardan y se envían desde tu WordPress; Moku no recibe ni guarda estos datos. Tu tienda es responsable de tratarlos conforme a la ley y a su política de privacidad. Los textos sugeridos están escritos para Chile.» «El aviso del correo se basa en el interés legítimo que permite la Ley 21.719; si prefieres pedir permiso con una casilla, cámbialo en los ajustes.»
- Free boleta tools, no account needed. A «Boleta» box on each order for the boleta, factura or nota de crédito you issued: its number and PDF (dropped on the box or uploaded), and a «Copiar datos para la boleta» button that copies the total and a short detail for the SII’s e-Boleta or your own system. The PDF goes to the buyer attached to WooCommerce’s «Pedido completado» email, or in its own «Tu boleta del pedido» email when you add it later. A «Boleta» column and a «Sin boleta» filter in the orders list, a daily email and a count on the Moku menu tell you which orders still lack one, and a refund asks for its nota de crédito. WooCommerce > Moku > Boletas shows the month’s summary with a CSV for your accountant (no buyer names or RUTs; «No reemplaza el Registro de Compras y Ventas del SII.»), and the rótulos can print a packing list for inside the box. Everything can be turned off or changed: which documents you issue, which order states need one and after how long, the email’s words, the file name, the daily email’s days, hour and recipients, the CSV’s columns and the packing list’s size and parts. Payments whose voucher you declared to the SII as your boleta can be marked so their orders never count as «Sin boleta». «Las boletas y facturas se guardan en una carpeta protegida de tu WordPress. Moku no las recibe, salvo las de pedidos de Moku, que se envían a Moku para entregarlas al comprador. Conservarlas es responsabilidad de tu tienda.»
- Your catalog in Moku in minutes. Import your products and their photos as private drafts. Once sales open for your store, publish the ones you want, one by one.
- Stock that stays right. Moku follows your WooCommerce stock and prices, so you don’t sell what you no longer have.
- Orders where you already work. Once your store sells on Moku, each sale becomes a WooCommerce order paid with “Moku”, already processing and with its stock taken. Complete it when you ship, or cancel it to return the stock. Moku hears either way.
- No surprises. Your prices and promotions stay as they are. An optional price rule for Moku applies only after you review and turn it on.
- Made for Chile. Prices in pesos (CLP), boleta or factura details on every order, and an interface in Chilean Spanish.
How it works
- Create your free seller account at https://moku.cl/sell.
- Install this plugin and paste the credential Moku gives you in WooCommerce > Moku. Your catalog comes into Moku as private drafts.
- Once Moku opens sales for your store, agree to receive orders and publish the products you want to sell.
- Each sale arrives in WooCommerce: you ship it and issue the boleta or factura.
Pricing
Installing the plugin and keeping your stock in sync are free. Selling on Moku’s marketplace is optional: Moku charges a commission on each sale, listed at https://moku.cl/pricing.
Requirements
- The WordPress and PHP versions shown in the plugin details, with the PHP Sodium extension.
- WooCommerce 10.4.4 or later.
- HTTPS and a working WordPress cron. Running WordPress cron from the server’s cron (DISABLE_WP_CRON) is recommended: when only site visits run it, Moku’s orders arrive with the next visit.
- InnoDB tables to keep stock in sync with Moku. A store that imports its catalog into Moku can also run on MyISAM tables, with a notice recommending InnoDB.
- A store that sells in Chilean pesos (CLP).
External services
The store check in WooCommerce > Moku runs entirely inside WordPress. It reads your settings and published products and sends nothing to Moku or anyone else.
The shipping tools (the «Envío» box, the orders column, «Copiar datos», the labels and the tracking block in the «Pedido completado» email) also run entirely inside WordPress and send nothing to Moku, the couriers or anyone else. The email’s tracking button is a link to the courier’s own tracking page, the one shown in the shipping settings; it is opened only if the buyer clicks it. On an order Moku sent you, the carrier and tracking number you save reach Moku as described below.
The cart reminders also run entirely inside WordPress. The shopper’s email, name, phone and cart are saved in two tables in your own database and the reminder is sent by your WordPress, with WooCommerce’s email settings; nothing is sent to Moku or anyone else, and Moku never receives or keeps this data. Cart data is deleted when the shopper orders, asks to stop, or after 30 days; a minimal record (keyed hashes of the email and phone, never the email or phone itself, and what was sent or refused) is kept for up to 4 years so a request to stop keeps being respected. The WhatsApp message is opened only when you tap «Escribir por WhatsApp»: it opens https://wa.me (WhatsApp, a Meta service) on your device with the shopper’s phone and the message, and you send it yourself. WordPress’s personal data export and erasure tools include these carts, and a suggested privacy policy paragraph is added to Settings > Privacy.
The boleta tools also run inside WordPress. The documents’ numbers are saved on the orders and their PDFs in a protected folder of your uploads that cannot be opened by its address; the buyer’s emails and the daily email to you are sent by your WordPress, and the monthly CSV downloads from your WordPress. Nothing is sent to Moku or anyone else, except on an order Moku sent you: there, the PDF you save is sent to Moku as described below. The box’s link to the SII (https://eboleta.sii.cl or https://www.sii.cl, the Chilean tax service, or the address you set) opens only when you click it, and the plugin sends it nothing; «Copiar datos» only puts the order’s total and detail on your clipboard.
This plugin connects to the Moku service at https://moku.cl/api/v1 after you configure a credential. It sends authorization credentials over HTTPS and binds the connection to your store URL and installation identity. Discovery sends product and variation identifiers, catalog fields, image references, prices, stock observations and native compatibility information. Reviewed synchronization also exchanges mappings, operational permissions, stock/price commands, receipts, order identifiers, quantities, amounts, statuses and timestamps. Requests happen during setup, administrator actions, scheduled reconciliation and order events.
Native order observations omit the buyer’s contact email, delivery address, card details and payment-gateway credentials.
If you import your catalog into Moku and agree in Moku to receive its orders, the plugin also fetches the orders buyers paid on Moku for your products: the items, quantities, amounts paid, shipping charged, delivery terms, billing choice (for a factura, the buyer’s RUT, business name, line of business and billing address), and the recipient’s name, delivery address and phone. It creates each one in WooCommerce, takes its stock, and reports back the WooCommerce order number, the stock it took, whether you shipped or cancelled it, and the carrier and tracking number you recorded for a shipment. When you save a boleta, factura or nota de crédito on such an order, the plugin sends its PDF, its kind and its file name to Moku, which keeps it on the buyer’s order and emails it to the buyer. After every check for orders it also tells Moku whether the check worked (a problem code only), the plugin version, the storage engine of its order table, whether WooCommerce uses high-performance order storage, and whether WordPress runs its scheduled tasks from the server’s cron. Moku never sends the buyer’s email. The plugin keeps an encrypted copy of each order in its own table: the recipient’s details are erased from it as soon as the WooCommerce order holds them, or the plugin refuses the order, and the rest once Moku records what became of it. The WooCommerce order is then your record.
When your store imports its catalog into Moku, or once you choose its synchronization sources there, the plugin uploads the product and variation images it reads from your media library (never from a URL) to Moku’s private catalog media. Only you see them in Moku until you publish each product.
Service: https://moku.cl/
Terms: https://moku.cl/terms
Privacy policy: https://moku.cl/privacy-policy
Support: https://moku.cl/contact
Support: support@moku.cl
Privacy requests: privacy@moku.cl
API documentation: https://developers.moku.cl/
Source and build tools
PHP and CSS are included as readable source. The Spanish catalog is readable JSON. Its canonical messages, compiler and rebuild instructions are included in source/. No build tools or Node.js are needed to install or run the plugin.
Installation
- Install and activate WooCommerce, and back up your store.
- In WordPress, go to Plugins > Add New Plugin, search for “Moku for WooCommerce”, then install and activate it.
- Sign in to Moku, or create your account at https://moku.cl/sell, and open Integrations > WooCommerce.
- Create a connection credential and paste it in WooCommerce > Moku.
- Back in Moku, find your products as private drafts in Catalog, and choose their Moku prices on the WooCommerce page.
FAQ
Is the plugin free?
Yes. Installing it and keeping your stock in sync cost nothing. If you choose to sell on Moku’s marketplace, Moku charges a commission on each sale, listed at https://moku.cl/pricing.
Do I have to sell on Moku?
No. Publishing on Moku’s marketplace is optional, and syncing never publishes a product by itself: you publish each one.
When can I start selling on Moku?
Moku opens sales to WooCommerce stores in stages. Until then, your imported products stay as private drafts that keep up with your store. The WooCommerce page in your Moku account shows whether your store can receive orders and what is missing, such as your agreement to receive them.
Will it change my products or prices in WooCommerce?
Not unless you approve it. Connecting and importing your catalog never change your store. Writing stock, catalog or prices back to WooCommerce needs a reviewed activation in Moku, and your prices and promotions stay as they are unless you turn on a price rule. The plugin never creates WooCommerce products or replaces your descriptions.
How do Moku orders reach me?
Once Moku opens orders for your store and you agree to receive them, each paid order arrives as a WooCommerce order paid with “Moku”, already processing and with its stock taken. Each item needs its own managed stock with backorders off. If it doesn’t, or the stock is gone, the plugin refuses the order and Moku refunds the buyer. Complete the order when you ship it, or cancel it to return its stock. If Moku refunds the buyer before you ship, the plugin cancels the order and returns its stock.
How does Moku learn the tracking number?
Before you complete a Moku order, write the carrier and tracking number in the order’s «Envío» box, or record them with WooCommerce Shipment Tracking. When you complete the order, Moku marks it shipped and tells the buyer, who can confirm the delivery. A tracking number you add or change after completing the order, in the box or with Shipment Tracking, reaches Moku as soon as it is saved on the order.
Who issues the boleta or factura?
You do, as with any sale in your store. The order shows whether the buyer asked for a factura and their billing details. Save the document’s number and PDF in the order’s «Boleta» box in WooCommerce: on an order from Moku, the plugin sends the PDF to Moku, and Moku gives it to the buyer, so the plugin never emails that buyer. You can also upload it on the order in Moku.
What happens if I pause, deactivate or uninstall?
Pausing stops new work, while operations already accepted finish. Deactivating or uninstalling does not disconnect Moku: the plugin keeps its encrypted credentials, mappings and operation records. Disconnect in Moku first, and ask support if you want that data removed. Deleting the plugin removes only the settings and saved results of the free store check, shipping tools, boleta tools and cart reminders, including the reminders’ saved carts and their record of requests to stop; the courier and tracking number saved on your orders stay with the orders, and so do your boletas, facturas and notas de crédito with their PDFs, which your store must keep. Never delete the plugin’s journals or change WordPress authentication salts to clear pending work.
What is not supported yet?
More than one WooCommerce store per Moku account, currencies other than Chilean pesos, products with more than 100 variations, and variations that share stock. Those products stay visible for your review instead of being cut.
Where can I get help?
Write to support@moku.cl or use https://moku.cl/contact. Developer documentation is at https://developers.moku.cl/.
Screenshots





Changelog
0.4.18
- New «Boletas» tab in WooCommerce > Moku, free and with no Moku account. Each order gets a «Boleta» box for the number and PDF of its boleta, factura or nota de crédito, with a «Copiar datos para la boleta» button for the SII’s e-Boleta (the total and a detail of up to 80 characters) and a link to the SII.
- The PDF goes to the buyer attached to «Pedido completado», named for them («boleta-1291.pdf»), or in a new «Tu boleta del pedido» email when you add it after completing the order. Both use your store’s email design, and you can change or turn off the new email in WooCommerce > Ajustes > Correos.
- The orders list gets a «Boleta» column and a «Sin boleta» filter; the tab lists the orders that lack a document, and a daily email (weekdays at 09:00 by default) tells you how many. Refunds ask for their nota de crédito. Orders placed before you updated are never counted.
- The tab shows the month’s boletas, facturas and notas de crédito, with a CSV for your accountant that names no buyer.
- Printing rótulos can add a packing list for inside the box, with a box to tick per product.
- Every tool and text can be turned off or changed in the tab, beside a live preview.
- On an order from Moku, the PDF you save goes to Moku on the next poll, and Moku gives it to the buyer. The plugin never emails that buyer.
- The PDFs are kept in a protected folder of your WordPress that no one can open by its address; deleting the plugin keeps them. Exporting personal data in WordPress lists a buyer’s documents, and erasing keeps them, as the tax law requires.
0.4.17
- New «Carritos» tab in WooCommerce > Moku, free and with no Moku account: cart reminders. Off until you turn them on. One reminder email to a shopper who typed their email at checkout and did not finish (sent 1 hour later by default, with today’s prices, without items that ran out, and not at all if they already bought); if they don’t come back in 24 hours and ticked the WhatsApp box, the tab and a daily email list them with an «Escribir por WhatsApp» button that opens WhatsApp on your phone with the message ready, once per cart. «Me pidió no escribirle» and the email’s stop link block every later reminder.
- Checkout shows a notice with «No quiero» under the email field (or, if you choose, an unticked box), and an unticked WhatsApp box by the phone, on the classic and the block checkout.
- Carts in sensitive categories get a reminder that names no product and no WhatsApp; categories named like health, pharmacy, intimate or adult products are marked to start with.
- The reminder is a WooCommerce email («Recordatorio de carrito (Moku)»), so it uses your store’s email design, and you can change its subject and heading or turn it off there. The tab sends you a test email.
- Everything is saved and sent from your WordPress; nothing reaches Moku. Carts are deleted on the order, on a request to stop or after 30 days. Exporting and erasing personal data in WordPress include them, and the tab gives a suggested paragraph for your privacy policy.
0.4.15
- Moku imports phone photos whose file ends a few bytes early, as browsers and WordPress already show them. Before, the plugin called them “not a JPEG, PNG or WebP image”.
- When your site’s image editor cannot convert a photo, the plugin tries WordPress’s other built-in editor (GD) before reporting a problem.
- Photos an earlier version refused for these reasons are checked again on their own, with nothing for you to do.
- Orders from Moku no longer send WooCommerce’s «New order» email, since Moku already emails you about each one. Your other orders still send it.
0.4.14
- New «Envíos y rótulos» tab in WooCommerce > Moku, free and with no Moku account: an «Envío» box on every order for the courier and tracking number, an «Envío» column in the orders list, a «Copiar datos» button, address labels printed from the order or in bulk with «Imprimir rótulos de despacho», and the courier, number and a tracking button in the «Pedido completado» email. Each tool turns on or off, couriers and their tracking links can be changed or added, and you choose the label size, what it shows, the sender and the email text, with a live preview. Nothing is sent outside WordPress.
- The «Envío Moku» box on Moku’s orders is now the same «Envío» box; Moku’s orders still report the courier and number to Moku.
- The store check gets its own settings: turn any check off and set the minimum photos and description length.
- Deleting the plugin removes the free tools’ settings and saved results. The connection keeps its data, as before.
0.4.12
- New «Revisión de tu tienda» tab in WooCommerce > Moku, free and with no Moku account: it checks pending updates, HTTPS, currency, store address, inventory, scheduled tasks and MyISAM tables, then lists published products without a price, photo, weight or category, with a single photo, a short description, a name in capitals, photos in HEIC, TIFF or BMP, or stock that is not counted. Products you make to order can be marked so the check stops listing them. It shows how many products already have what Moku asks to publish. The check sends nothing to Moku.
- A store that has not connected opens the plugin’s page on the check; a connected store keeps opening on its connection.
0.4.11
- Stores whose WooCommerce tables use MyISAM can sell on Moku. The plugin takes each order’s stock one safe step at a time, only while the units are still there, and shows a yellow notice recommending the conversion to InnoDB.
- Stores that keep their orders in WordPress posts storage, instead of WooCommerce’s high-performance order storage, can receive Moku’s orders too.
- Stores whose WordPress runs its scheduled tasks only on site visits can receive Moku’s orders: they arrive with the next visit, and the plugin’s page recommends the server’s cron so they arrive within a minute.
0.4.10
- A product photo Moku could not import names its product and the real reason, such as a photo file missing from the server, with a link to edit the product. Replacing the photo and saving the product clears the problem and imports the new photo on its own.
- When database tables that cannot roll back a change, such as MyISAM tables, keep Moku from confirming stock, the plugin says so and names the tables to convert to InnoDB.
0.4.9
- Orders placed by Moku get an “Envío Moku” box for the carrier and tracking number. When you complete the order, Moku marks it shipped and tells the buyer, who can confirm the delivery. The plugin also reads the tracking number WooCommerce Shipment Tracking recorded.
- A tracking number added or changed after you complete the order, in the box or with Shipment Tracking, reaches Moku as soon as it is saved on the order.
0.4.8
- When the site does not meet the requirements yet, the notice names Moku for WooCommerce and lists exactly what is missing, with the versions the site has.
- The external-link icon on setup buttons is centered vertically.
0.4.7
- Runs on WordPress 6.8 and PHP 8.2 or later. WooCommerce 10.4.4 or later is still required.
0.4.6
- The setup reminder appears only on the Dashboard and Plugins screens.
- Admin form nonces are sanitized before verification.
- Local journal writes detect an open WooCommerce transaction through the WordPress database API only.
0.4.5
- The plugin’s directory address is wordpress.org/plugins/moku-for-woocommerce/, and its text domain now matches it.
0.4.4
- Moku’s Channels page is now Integrations, at moku.cl/dashboard/integrations. The plugin’s steps and links point there; links from older versions still arrive.
0.4.3
- Tested with WordPress 7.1.
- The plugin’s “Visit plugin site” link now opens its setup guide.
0.4.2
- A store that imports its catalog into Moku now sends its product photos too, read from your media library, so its products can be published without uploading each photo again in Moku. They stay private until you publish each product.
- When Moku does not let the current connection send photos, the plugin checks again every five minutes instead of failing, and connecting again restarts the photo import.
0.4.1
- Cancels an order Moku placed when Moku refunds the whole order before you ship it, and returns its stock; an order you already completed stays a shipment.
- Tells Moku after every check for orders whether it worked, which storage its order records use, and whether WordPress runs its scheduled tasks from your server’s cron. The plugin’s page warns when orders are not arriving, or when only site visits run those tasks.
0.4.0
- Receives the orders buyers paid on Moku, once you agree in Moku: each becomes a processing WooCommerce order with its stock taken in one step, or is refused when the stock is gone, and Moku hears when you complete or cancel it. Receiving orders needs WooCommerce’s high-performance order storage, the default for new stores.
0.3.2
- A store that imports its catalog into Moku, without choosing sources there, sees its import as done once its products are in Moku, with a link to follow the import instead of a request to activate synchronization.
0.3.1
- Runs on WooCommerce 10.4.4 and later. Background jobs no longer wait on each other with the Action Scheduler WooCommerce 10.4 ships.
0.3.0
- Removed the earlier advanced connector profiles (hand-picked products, Moku-owned checkout and signed webhooks). Every store connects by pairing.
0.2.2
- Downloaded from the Moku workspace through a private, short-lived link. No connector changes.
0.2.1
- First public release, downloadable from the Moku workspace while the directory listing is pending.
- Discovery reports its capacity waits, retries, failures and stalls to the Moku workspace.
- Fairer paired write budget and faster full-catalog backfill, rescans and media scans.
- Discovered variation attributes keep their store labels, including numeric labels.
- Plugin dates use the numeric es-CL form.
0.2.0
- Paired discovery and reviewed activation for catalog, inventory and prices.
- Durable operation evidence and protected recovery for uncertain outcomes.
- WordPress.org package preparation under the moku-os directory identity.
