Mydybox Taiwan For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Mydybox Taiwan for WooCommerce is a localization toolkit built for stores selling to customers in Taiwan. It adapts the WooCommerce checkout to Taiwanese conventions, integrates with local logistics and payment providers, and provides a visual rule engine for common business logic.
Core Features
- Taiwan Checkout Optimization — City/District cascading dropdowns and 3+2 digit postcode auto-fill.
- Tax ID Fields — Collect Unified Business Number (UBN), Company Name, Mobile Barcode, Citizen Digital Certificate, and Donation Code at checkout.
- Optional Tax ID Lookup — When the site owner explicitly opts in, an entered 8-digit Tax ID can be looked up against the Taiwan GCIS open-data API to pre-fill the company name. Disabled by default.
- Visual Rule Engine — Manage payment, shipping, and cart rules with a visual interface; no coding required.
- Custom Order Numbers — Sequential number formats (e.g.,
Prefix + YYYYMMDD + Sequence). - Checkout Countdown — Optional reservation timer.
- Mobile Sticky Bar — Sticky “Buy” button for mobile product pages.
- Social Login — One-click login with LINE, Google, and Facebook (each optional and disabled by default).
- Convenience-Store Pickup — 7-11 / FamilyMart / Hi-Life / OK pickup via ECPay or NewebPay logistics.
- HPOS Ready — Compatible with WooCommerce High-Performance Order Storage.
External services
This plugin can connect to several third-party services. Each connection only happens when the corresponding feature is enabled in the plugin settings. By default, every external integration is disabled.
1. Taiwan GCIS (Government Open Data) — Tax ID Lookup
- What it is: The Ministry of Economic Affairs (Taiwan) open-data API that returns the registered company name for a given Unified Business Number.
- When data is sent: Only when the site owner has enabled “Tax ID Lookup” in Checkout settings, and a customer types an 8-digit Tax ID during checkout. The 8-digit Tax ID is then sent to
data.gcis.nat.gov.tw. No other customer data is sent. - Disabled by default; explicit opt-in is required both in the JS payload and on the server endpoint.
- Terms of use: https://data.gov.tw/license
- Privacy policy: https://data.gov.tw/about
2. LINE Login (OAuth)
- What it is: LINE Corp’s OAuth 2.0 / OpenID Connect endpoint used to authenticate the customer with their LINE account.
- When data is sent: Only after the site owner enables LINE Login and a visitor clicks the “Login with LINE” button. The authorization code, your configured Channel ID/Secret, and the redirect URL are sent to
api.line.me; the response (LINE user ID, display name, optional email, profile picture URL) is used to create or match a WordPress user. - Terms of use: https://terms2.line.me/LINE_Developers_Agreement
- Privacy policy: https://line.me/en/terms/policy/
3. LINE Messaging API — Abandoned-Cart Push Notifications
- What it is: LINE Corp’s Messaging API used to push a recovery message to a customer who linked their LINE account.
- When data is sent: Only when the site owner enables abandoned-cart LINE notifications and a customer has linked their LINE account and abandoned a cart. The configured channel access token and the recipient’s LINE user ID + message body are sent to
api.line.me. - Terms of use: https://terms2.line.me/LINE_Official_Account_Terms_of_Use
- Privacy policy: https://line.me/en/terms/policy/
4. Google OAuth
- What it is: Google’s OAuth 2.0 endpoints used to authenticate the customer with their Google account.
- When data is sent: Only after the site owner enables Google Login and a visitor clicks “Login with Google”. The authorization code, your configured Client ID/Secret, and the redirect URL are sent to
oauth2.googleapis.com; the returned ID token (Google user ID, name, email, picture URL) is used to create or match a WordPress user. - Terms of use: https://policies.google.com/terms
- Privacy policy: https://policies.google.com/privacy
5. Facebook Graph API (Login)
- What it is: Meta’s Graph API OAuth endpoints used to authenticate the customer with their Facebook account.
- When data is sent: Only after the site owner enables Facebook Login and a visitor clicks “Login with Facebook”. The authorization code, your configured App ID/Secret, and the redirect URL are sent to
graph.facebook.com; the returned profile (Facebook user ID, name, email, picture URL) is used to create or match a WordPress user. - Terms of use: https://www.facebook.com/legal/terms
- Privacy policy: https://www.facebook.com/policy.php
6. ECPay (Green World) — Payment Gateway and CVS Pickup
- What it is: ECPay’s online payment gateway and logistics (CVS pickup) APIs.
- When data is sent: Only when the site owner enables the ECPay payment gateway and/or CVS shipping method, and a customer chooses ECPay at checkout. The order summary (order ID, total amount, item names, customer name/email/phone, billing/shipping address as needed by the chosen ECPay service) is posted to
payment.ecpay.com.tw(or the staging host in test mode) orlogistics.ecpay.com.twfor store-pickup selection. - Terms of use: https://www.ecpay.com.tw/About/Term
- Privacy policy: https://www.ecpay.com.tw/About/Privacy
7. NewebPay (藍新金流) — CVS Pickup
- What it is: NewebPay’s convenience-store pickup map API.
- When data is sent: Only when the site owner enables the NewebPay CVS shipping method and a customer opens the store-selection popup. The configured Merchant ID and a return-URL nonce are posted to
cvsmap.newebpay.com. NewebPay then returns the selected store’s ID, name, and address to the plugin. - Terms of use: https://www.newebpay.com/website/Page/content/term
- Privacy policy: https://www.newebpay.com/website/Page/content/privacy
Source Code & Build Process
This plugin’s JavaScript is written with the official WordPress tooling and compiled with @wordpress/scripts (webpack). The human-readable, un-minified source for every generated file is bundled inside the plugin so it can be reviewed, modified, and rebuilt:
build/index.jsis compiled fromsrc/index.js(which importssrc/invoice-block.js).
To rebuild the compiled assets from source:
- Install Node.js 18+ and run
npm installin the plugin directory. - Run
npm run buildfor a production build, ornpm startfor a watch-mode development build.
The build entry points and tooling are defined in package.json.
Bundled third-party libraries
- SweetAlert2 v11.26.25 — MIT License — https://github.com/sweetalert2/sweetalert2 — bundled as the official minified distribution at
assets/vendor/sweetalert2.all.min.js.

