Editorial process
Source hierarchy, review cadence, and recommendation-change rules
Last trust review: June 9, 2026
Direct answer: Mulebuy editorial pages should prioritize current public sources, local data assets, visible page evidence, and clearly dated manual review notes. Comparison recommendations can change when live fee visibility, QC-photo access, route breadth, storage, support, payment behavior, or workflow fit materially changes.
The editorial policy now explains how guide and comparison claims are reviewed. It gives readers a clearer way to judge what is based on local data, what requires live verification, and what kind of material change should trigger a rewrite.
Name clarity
| Name | What it is | Controlled by this guide hub? |
|---|---|---|
| Mulebuy Info | Independent guide site with editorial content, comparison snapshots, disclosures, and correction policy. | Yes |
| Kakox | External spreadsheet/category browsing destination. | No |
| Mulebuy platform | Third-party shopping-agent platform controlling accounts, orders, warehouse QC, fees, refunds, and shipping. | No |
| mulebuy.com | External registration/referral URL. It may be monetized, but it is not controlled by Mulebuy Info and does not affect rankings. | No |
Evidence snapshot: Last checked: June 9, 2026. Checked by: Mulebuy Editorial Team. Data source: local Mulebuy trust pages, correction policy, editorial policy, affiliate disclosure, public data assets, and manual review of site-level support boundaries. Source confidence: High for Mulebuy editorial standards and local review workflow; medium for local comparison data fields; low for third-party account terms until rechecked live. Must verify live: source date, public URL or local data field, page section, affected recommendation, live fee or route field, support rule, payment condition, and whether the claim needs an update log.
Source hierarchy
- Use public platform pages, current account-side screenshots, local data assets, and visible Mulebuy page tables before relying on old community comments.
- Label fields as verified, listed, or unverified when the evidence level differs.
- Avoid presenting live fees, coupons, route availability, or support behavior as permanent.
Review cadence
- Priority comparison and money pages should be reviewed monthly or sooner after visible fee, route, storage, support, payment, or platform-access changes.
- Guide pages should be updated when workflows, buyer risks, or linked support assets materially change.
- Trust and policy pages should update when correction routes, disclosure wording, privacy handling, or entity boundaries change.
Recommendation-change rules
- Downgrade a recommendation when fee visibility weakens, QC-photo access changes, routes narrow, storage shrinks, support becomes unclear, or checkout no longer matches assumptions.
- Promote alternatives only when they show stronger evidence for the same seller link, destination, parcel constraints, and buyer context.
- Keep caveats visible when the best choice depends on live account details.
Editorial limits
- This guide hub does not authenticate products, certify sellers, provide legal/tax advice, or guarantee shipping outcomes.
- Affiliate relationships should be disclosed and should not decide ranking order.
- Material changes should be reflected in visible update logs, sitemap metadata, and supporting reports.
Update log: June 9, 2026: Added source hierarchy, review cadence, recommendation-change rules, editorial limits, source confidence, and live-check caveats.
Related trust resources: