Beta
Documentation index
Concepts

Connections

What a connection is and how it relates to your store.

6 min read

In Noobit, a connection is a configuration that links your account to an external platform: WooCommerce, CSV export, or the ones still to come (Shopify, PrestaShop). Each connection has credentials, settings and a status.

One store and your outputs

By default, each account connects one WooCommerce store. Alongside it you can have CSV exports and outputs for other channels, within the destinations your plan includes. If you sell in several stores, we turn on multi-store mode on request. Typical examples:

  • Your WooCommerce store
  • Your ERP, via CSV: you import what it exports and send it back a file with its columns
  • Amazon's product file, with its structure
  • A second store, with multi-store mode turned on

With multi-store mode, you choose the store when you publish, product by product or in bulk. Each store has its own category mapping, its own publishing log and its own status, and you can decide which products go to each one: bulk publishing respects that list and tells you how many it skipped.

Connection status

Noobit checks each store regularly and shows its status in «Configuración» → «Conexiones» (Settings → Connections):

«Operativa» (Operational)
The store responds. Sync and publishing work normally.
«Lenta» (Slow)
It responds, but it takes a while. Everything keeps working, just more slowly.
«No responde» (Not responding)
Noobit pauses sending to that store and retries automatically once it's back. You'll see a notice at the top of the screen.

Anatomy of a WooCommerce connection

URL
Your store's address (https://...)
Consumer Key and Consumer Secret
The credentials you generate in WooCommerce so Noobit can read from and write to your store
WordPress access (optional)
A username and application password, to read the brands that some plugins store
Webhooks
The notifications Noobit registers in your store so it hears about every change as it happens
Taxonomy
Your store's categories, brands, tags and attributes, downloaded
Mappings
How each category in your tree, and each brand, translates to the store's own
Publishing preferences
The status products are published with, what gets sent (content, prices, stock) and where your store keeps data like the EAN or the brand

Two-way sync

The connection works both ways. What changes in your store (new products, price, stock, EAN, orders) comes into Noobit right away through webhooks, and you can run a sync by hand whenever you want. Written content, on the other hand, only changes when you take action: if someone edits it in the store, you'll see it in «Conflictos» (Conflicts) and decide whether to adopt it. And if you rewrote a text by hand, Noobit asks you to confirm before regenerating it.

Categories, brands and tags

When you connect a store, Noobit downloads its taxonomy: categories, brands, tags and attributes. Categories go through category mapping: each category in your tree is linked to the store's by exact name or because you confirm it in «Categorías» (Categories). If it isn't certain, Noobit doesn't guess: it publishes without that category and flags it for you to resolve. Brands are matched with the store's and, if there's any doubt, Noobit asks you; it never creates a new brand on its own.

Brands are remembered
Every matched brand is saved for next time. The first time you publish a new brand it takes a little longer, because it has to be matched to a brand in the store; after that it's instant.

CSV export

CSV export is a simple connection: it has no URL or credentials, just a format (columns, separator and encoding). It generates the CSV when you ask for it. If a channel needs its own structure (your ERP, the Amazon file…), create an output for it: we explain how in Concepts · Outputs.