Bulk product updates time out. Not sometimes: reliably, on exactly the hosting your clients actually buy. You start an import of four thousand variations, the PHP execution limit fires, and you are left guessing which half of the catalogue made it.
The problem is structural. You are asking a shared-hosting PHP process, tuned for serving a page in under a second, to do an hour of batch work.
Why does the store's own server struggle?
A WooCommerce import is not one operation. Each product touches several database tables, regenerates lookup data, fires plugin hooks, and often pulls down an image. Multiply that by a few thousand rows and you are well past any reasonable request budget.
So the usual workarounds appear: chunk the CSV by hand, install a queue plugin, raise the memory limit, run it at 3am and hope. Each one adds a moving part, and none of them make the machine faster.
Running the heavy part somewhere else
Vibery does the expensive work on our infrastructure and talks to the store over its API. The import is parsed, validated, and resolved on our side. What reaches the store is a series of clean, ordinary writes, the same shape as a human saving a product.
That changes the failure mode. A malformed row is a reported error against that row, not a half-finished import with no record of where it stopped. In a recent run, twenty-four products were created and two were flagged as needing a price, listed individually, rather than the whole job dying at product 1,847.
What store work can an agent do?
The WooCommerce surface covers what you actually manage day to day:
- Products, including variations and their attributes
- Orders, refunds and order status changes
- Customers
- Coupons
Which means the request can be a sentence. "Import products from ./menu.csv." "Refund order 4471 and email the customer." "Find every product with no image and list them."
Does my store need a plugin installed?
Not for the standard connection. WooCommerce stores connect over the existing wc/v3 API using a WordPress application password, so there is nothing new to install and nothing to leave behind when you disconnect.
There is a plugin tier for the deeper things core WordPress will not expose, but you opt into it. The default is: connect, work, revoke.
No comments yet