OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
REST v3 returns structured order objects.
WooCommerce REST API v3 Orders ↗
Order properties / Retrieve an order · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Order collections expose page and per_page.
WooCommerce REST API v3 Orders ↗
List all orders / Available parameters · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Order collection filters select dates, status and identifiers.
WooCommerce REST API v3 Orders ↗
List all orders / Available parameters · Checked 2026-10-16
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Merchant-controlled WooCommerce core is free and includes REST endpoints; hosting/paid extensions are separate.
WooCommerce free core and built-in REST endpoints ↗
Download WooCommerce now for free / Work your way · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Merchant selects the user and permissions for an integration key.
WooCommerce REST API key management ↗
Generate API keys · Checked 2026-10-16
Downstream permission -
-
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
The reviewed WooCommerce route does not establish downstream permission.
WooCommerce REST API v3 Orders ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
POST/PUT order operations create and update orders.
WooCommerce REST API v3 Orders ↗
Create an order / Update an order · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Merchant keys connect applications under selected user permissions.
WooCommerce REST API key management ↗
Generate API keys · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Merchant webhooks notify subscribed resource events.
WooCommerce core webhook setup and failures ↗
Creating webhooks · Checked 2026-10-16
Limit visibility -
-
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
The reviewed WooCommerce route does not establish limit visibility.
WooCommerce REST API v3 Orders ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Resource event topics distinguish updates and deletions.
WooCommerce REST API v3 Webhooks ↗
Topics / Available resources and events · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Default failure threshold is five retries, then webhook disabled; no durable replay established.
WooCommerce core webhook setup and failures ↗
Creating webhooks / delivery failures · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Order JSON responses are available to authorized external clients.
WooCommerce REST API v3 Orders ↗
Retrieve an order · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
The reviewed WooCommerce route does not establish post-cancellation access.
WooCommerce REST API v3 Orders ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Portable order records; entire store/extension/media restoration unverified.
WooCommerce REST API v3 Orders ↗
Order properties · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
Customer applications process store API responses externally.
WooCommerce REST API key management ↗
WooCommerce REST API · Checked 2026-10-16
Rights to custom logic -
-
Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries.
The reviewed WooCommerce route does not establish rights to custom logic.
WooCommerce REST API v3 Orders ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Merchants create API keys for a WordPress user and grant read, write or both. Revoking the key or changing the user’s permissions changes access; marketplace extension publication is separate.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The v3 Orders reference documents collection pagination, structured filters and create/update operations. A running store’s plugins and host can alter the available data and operational limits.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Merchant REST API v3 key | HTTP Basic | Customer | No | merchant creates key for a wordpress user with read/write permissions; https basic consumer key/secret | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
WooCommerce core is free to download and includes REST endpoints, with no provider API add-on for the assessed merchant-controlled route. Hosting and paid extensions are separate. No universal request-rate quota was established.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Order create and update endpoints require keys with write permission. Financial effects, statuses and extension-specific fields need validation against the installed store.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Core webhook topics include order updates and deletions. By default failed deliveries disable the webhook after five retries; the threshold can be changed by code.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Resource event topics distinguish updates and deletions. | WooCommerce REST API v3 Webhooks ↗Topics / Available resources and eventsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Default failure threshold is five retries, then webhook disabled; no durable replay established. | WooCommerce core webhook setup and failures ↗Creating webhooks / delivery failuresChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Paginated JSON order records can leave the store under merchant authorization. That scoped route does not establish recovery of media, every extension’s tables or a complete WordPress installation.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
The merchant can extend webhook behavior with WordPress filters. This review credits external integration logic while leaving native artifact rights and independent restore unestablished (API records are not a site backup).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. REST v3 returns structured order objects. | WooCommerce REST API v3 Orders ↗Order properties / Retrieve an orderChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Order collections expose page and per_page. | WooCommerce REST API v3 Orders ↗List all orders / Available parametersChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Order collection filters select dates, status and identifiers. | WooCommerce REST API v3 Orders ↗List all orders / Available parametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Merchant selects the user and permissions for an integration key. | WooCommerce REST API key management ↗Generate API keysChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Merchant-controlled WooCommerce core is free and includes REST endpoints; hosting/paid extensions are separate. | WooCommerce free core and built-in REST endpoints ↗Download WooCommerce now for free / Work your wayChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. The reviewed WooCommerce route does not establish downstream permission. | WooCommerce REST API v3 Orders ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. POST/PUT order operations create and update orders. | WooCommerce REST API v3 Orders ↗Create an order / Update an orderChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Merchant keys connect applications under selected user permissions. | WooCommerce REST API key management ↗Generate API keysChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Merchant webhooks notify subscribed resource events. | WooCommerce core webhook setup and failures ↗Creating webhooksChecked 2026-10-16 |
| How are integration limits disclosed? | -Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. The reviewed WooCommerce route does not establish limit visibility. | WooCommerce REST API v3 Orders ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Order JSON responses are available to authorized external clients. | WooCommerce REST API v3 Orders ↗Retrieve an orderChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. The reviewed WooCommerce route does not establish post-cancellation access. | WooCommerce REST API v3 Orders ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Customer applications process store API responses externally. | WooCommerce REST API key management ↗WooCommerce REST APIChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Merchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. The reviewed WooCommerce route does not establish rights to custom logic. | WooCommerce REST API v3 Orders ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMerchant-controlled WooCommerce REST API v3 order resources and core webhooks; hosting, plugins and WordPress database backup are separate operational boundaries. Portable order records; entire store/extension/media restoration unverified. | WooCommerce REST API v3 Orders ↗Order propertiesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Native extension/workflow ownership and restore rights
- Complete custom-table/media migration
- Webhook retained replay and deletion-topic coverage outside orders
- Hosting termination and retrieval rights
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.