Skip to main content

Black Friday Deal — 50% off all vendor listing plans.  Claim offer →

Connecting WooCommerce to Goji

Updated Aug 28, 2026

WooCommerce, like Shopify, is a content source rather than a posting channel. Goji does not post anything to your shop. It reads the products you publish there, so that each new one can be announced on the social channels you have connected — without you writing the same product twice.

What connecting WooCommerce gives you

  • New products become posts. Publish a product in WooCommerce and it can be shared automatically.
  • Your own site stays the original. Posts link back to the product page on your domain, where the sale actually happens.
  • Product data reused. Title, description and the product image become the post.
  • No plugin. The connection reads what your shop already publishes.

Before you start

A source belongs to a website, so add and verify the site first:

  1. Open Auto Social → Websites and add your WooCommerce site.
  2. Complete its verification.
  3. Then add the WooCommerce source to it.

Look for this under Auto Social rather than under Channels. Channels is where posts go out; sources are where content comes in. It is the commonest wrong turn with this feature.

Your products must also be published and publicly visible. Drafts, private products and anything behind a maintenance-mode plugin cannot be read, because Goji sees your shop exactly as a visitor does.

How to add it

  1. Open Auto Social → Websites and open your verified site.
  2. Add a content source and choose the WooCommerce products type.
  3. Confirm the shop address it should read.
  4. Save. Goji reads it once immediately so you know straight away whether it can see your products.

What happens next

Goji checks periodically for products it has not seen before, queues them, and publishes to whichever channels your rules route them to. Products that already existed when you connected are not published retroactively — an established shop would otherwise flood every channel the first time it ran.

Products without an image will be skipped on image-only networks such as Instagram while still publishing elsewhere. Since a product without a photograph rarely sells anyway, this is usually worth fixing at the source.

If something goes wrong

  • No products are found. The shop address is wrong, the products are not published, or a security plugin is blocking automated reads.
  • Only some products appear. The missing ones are drafts, private, or excluded from your shop's public listings.
  • Posts have no picture. Those products have no featured image set in WooCommerce.
  • Nothing publishes anywhere. The source is fine but no rule routes it. Check your publishing rules include this website.

Choosing which products get announced

Most shops do not want every product broadcast. A restock, a variant, or a low-value accessory rarely earns a post, while a genuinely new line does - and a feed that announces all of them equally trains followers to ignore it.

Publishing rules are where that judgement lives. You can route this source to a narrower set of channels than your articles use, or hold products for approval so somebody glances at them before they go out. It is worth setting that up before the first busy week rather than after it, because the alternative is disconnecting the source in a hurry.

One practical note on timing: Goji checks the source on a schedule rather than the instant you hit publish, so a product may be announced a little after it appears in your shop. If you need a launch to land at an exact moment, publish the product ahead of time and let the announcement follow, rather than expecting the two to be simultaneous.

Common questions

Can Goji create products in WooCommerce? No. It reads; it does not write to your shop.

Does it read orders, stock or customers? No. Only published product content.

How does this differ from the WordPress channel? The WordPress channel publishes posts to your site. This reads products from it. Many shops use both.

Can I connect several shops? Yes — one source per site, added against that website.

Was this helpful?