If you sell self-guided tours, city quests, or tickets with mooveGO through WooCommerce, this release is for you. We’ve added a native logging layer so you can see exactly what happened on every order—no guessing, no black box. That means quicker setups, faster debugging, and fewer support pings.
Why this matters: mooveGO was built for e-commerce—customers buy online, receive their game link automatically, and play on their phones with zero staff intervention. A transparent log makes that whole flow easier to launch and maintain.
What’s new
- Built-in logs (WooCommerce → Status → Logs) for the mooveGO integration.
- Granular events: server URL checks, hook installation, order status transitions, request/response markers.
- Safer failure handling: on a failed request, the order is moved back to a non-delivery status so you can retry after fixing the root cause.
- Clearer setup in Settings → Integration → mooveGO.
Bonus: if you’re using Mooveteam across team events and tourism experiences, this logging sits neatly behind the same product stack you already know.
Download the new version
➡️ Get the latest mooveGO for WooCommerce build
Quick start: enable & view the log
- Enable logging
WooCommerce → Settings → Integration → mooveGO → tick Enable logging → Save. - Verify your server URL
Set it to your endpoint (e.g.,https://go.mooveteam.com) and save. - Choose when to send codes
Most shops trigger on Processing (recommended). - Find your logs
WooCommerce → Status → Logs → select the latestmoovego-*.log.
How to read the entries
✅ Successful request
2025-09-02T12:27:40+00:00 Info 173 set to PROCESSING
2025-09-02T12:27:40+00:00 Info product Go Remote moovecode HkOEYj5E•••••••••••••
2025-09-02T12:27:40+00:00 Info order has moovecode, inform moove
2025-09-02T12:27:46+00:00 Info Payment has been received for order 173
2025-09-02T12:27:47+00:00 Info server url: https://go.mooveteam.com
2025-09-02T12:27:47+00:00 Info woocommerce - moovego hook installed
What it means: Order #173 moved to Processing, the product contains a mooveGO code, the plugin notified the server, payment was confirmed, and the hook ran normally.
❌ Failed request (auto-rollback)
2025-09-02T12:22:36+00:00 Info 171 set to PROCESSING
2025-09-02T12:22:36+00:00 Info product Go Remote moovecode HkOEYj5E•••••••••••••
2025-09-02T12:22:36+00:00 Info order has moovecode, inform moove
2025-09-02T12:22:41+00:00 Info response code
2025-09-02T12:22:41+00:00 Info request failed
2025-09-02T12:22:41+00:00 Info 171 set to PENDING
What it means: The order contained a mooveGO code, but the server didn’t return a valid response. The plugin safely moved the order back to Pending so you can retry after fixing the connection.
Sample log entries; tokens are partially obfuscated for security.
Common causes of failures (and quick fixes)
- Server URL typo → Double-check
https://go.mooveteam.comin Integration settings and save. - Outgoing requests blocked → Ask your host to allow outgoing HTTP(S) from WordPress, or temporarily disable security plugins/firewalls that block
wp_remote_post. - Wrong trigger status → If you customized “Send code on,” confirm your payment workflow actually reaches that status (e.g., Processing vs Completed).
- Product not flagged as mooveGO → Ensure the product/variation has the mooveGO meta set so the plugin knows it’s a code-delivery item.
Best practices
- Test in staging with logging ON; ship with it OFF (to keep logs tidy).
- Keep it simple: standardize on Processing as your send point unless you have a strong reason.
- Capture context: when something fails, save the order ID and ~10 lines around the failure to share with support.
- Sanitize before sharing: keep only the first 8 chars of any token visible (as in our samples).
Ready to upgrade?
➡️ Download the latest mooveGO for WooCommerce
Launch smoother. Diagnose faster. Get players into your experiences with less back-and-forth.
