Maropost Commerce Cloud (Neto)

Maropost Commerce Cloud, still sold in Australia as Neto, is a live
connector in the Commerce category. Find it under
Settings → Integrations → Maropost Commerce Cloud (Neto). It reads your
store over a read-only connection. Twelfth never writes back to Maropost.

Only workspace owners and admins can connect, sync or disconnect a store.
The connector only appears where it is configured for the environment.

Setup at a glance

  1. In Maropost, create a read-only staff user for Twelfth and generate its API
    key (see Before you start below).
  2. In Twelfth, open Settings → Integrations, choose Connect on
    Maropost Commerce Cloud (Neto), and enter the store domain, username and
    key (see Connect a store).
  3. Choose Sync now to check that orders arrive.
  4. Optional: set up the order webhook so changes
    arrive within seconds instead of 15 minutes.

Pages in your Maropost control panel

Replace your-store.mymaropost.com with your store’s domain.

Page Address What it is for
Control panel https://your-store.mymaropost.com/_cpanel Staff users and permission groups
API Settings https://your-store.mymaropost.com/_cpanel/setup_wizard?id=api The global API key, and the webhook fields

You don’t need to type the API Settings address. Once you enter the store
domain in the connect dialog, the dialog links to that page.

What Twelfth reads

Data Status
Orders and their lines: SKU, quantity, unit price, cost price, order date Live. Lines land with your other sales, so web orders show in Performance next to POS sales. Cancelled orders zero their lines out.
Products Planned
Stock Planned

The first sync reads back up to 12 months of orders. After that, each sync reads
only the orders that are new or changed.

Before you start: a staff user for Twelfth

Give Twelfth its own staff user rather than a person’s login or the global API
key. Then you can see what Twelfth reads, and you can switch it off without
affecting anyone else.

In the Maropost control panel:

  1. Under Settings & Tools, create a permission group named
    Twelfth integration. Give it API read access to Products,
    Orders, Customers and Categories, and nothing else.
  2. Create a staff user named twelfth_api and put it in the
    Twelfth integration group.
  3. Open the twelfth_api user and generate its API key. Copy the key.
Read access is enough

Twelfth only reads. Do not give the group write access to anything.

Connect a store

  1. Open Settings → Integrations and choose Connect on the
    Maropost Commerce Cloud (Neto) row.
  2. Enter the store domain, for example your-store.mymaropost.com, or your
    own domain if the store runs on one.
  3. Enter the API username: twelfth_api. Leave it blank only when you use
    the store’s global API key. That key is on the API Settings page, and
    the dialog links straight to it once you have entered the domain.
  4. Paste the API key and choose Connect.

Twelfth checks the key against your store before it saves anything. If Maropost
rejects the key, nothing is saved and the dialog says why. The key is
encrypted at rest and is never shown again or returned to the browser.

A store can be connected to only one Twelfth workspace at a time. To move it,
disconnect it from the other workspace first.

Sync cadence

  • Twelfth checks for new and changed orders every 15 minutes.
  • Sync now in the store’s Manage dialog runs a sync straight away and
    says how many orders it read. Use it to test a new connection.
  • The Manage dialog shows when the store last synced, and the error from the
    last sync if it failed.

Order updates (webhook)

The webhook is optional. Without it, the 15-minute sync still picks up every
order. With it, Maropost tells Twelfth when an order changes, so the update
arrives sooner. The 15-minute sync stays the source of truth either way.

  1. In Twelfth, open the store’s Manage dialog and expand
    Order updates (webhook). Copy the webhook URL and the
    verify token.
  2. In the Maropost control panel, open Settings & Tools → API Settings.
  3. Paste the token into Maropost Webhook Verify Token.
  4. Tick Enable Maropost API webhook.
  5. Paste the URL into Maropost API webhook URL.
  6. Choose Save Changes.
  7. Back in Twelfth, choose Send test call, then change any order in
    Maropost.

Each Maropost field name in the dialog links straight to your store’s
API Settings page, opened in one tab you can keep switching back to.

Check the webhook

Webhook calls, in the Manage dialog below the webhook setup, lists the last calls
Twelfth received, newest first, and refreshes every 10 seconds while the dialog
is open. Next to Order updates (webhook):

  • Receiving means Maropost has called Twelfth with the right token.
  • Token rejected means a call arrived with no verify token or a different
    one, and Twelfth turned it away. Copy the token again, paste it into
    Maropost Webhook Verify Token, and save.

Send test call sends a call to the webhook URL the way Maropost does, over
the internet, with the verify token. It proves Twelfth’s end works: the address
is reachable and the token is accepted. It does not prove Maropost is set up,
and it does not start a sync. Only a call from Maropost itself turns the status
to Receiving.

Disconnect

  1. In Maropost, deactivate the twelfth_api staff user, so its API key stops
    working. If you set up the webhook, untick Enable Maropost API webhook
    under Settings & Tools → API Settings.
  2. In Twelfth, open the store’s Manage dialog and choose Disconnect.

Disconnecting stops the sync and discards the stored key. Orders already read
stay in the workspace.

Troubleshooting

“Maropost rejected that API key.” Check that you copied the whole key, that
the username matches the staff user the key belongs to, and that the user is
active. A key from the global API Settings page needs a blank username. If
you generated a new key, the old one no longer works.

Orders are not updating. Open the store’s Manage dialog:

  • If it shows Last sync failed, the message after it is Maropost’s answer.
    An authentication error usually means the staff user was deactivated or its
    key was regenerated. Disconnect, then connect again with the new key.
  • Choose Sync now. If it reads orders, the connection works.
  • Check that the twelfth_api permission group still has API read access to
    Orders.

The webhook shows Token rejected. Maropost is calling, but with a token that
does not match. Copy the verify token again, paste it into Maropost
Webhook Verify Token with nothing before or after it, and choose Save
Changes.

Send test call says the address is not reaching Twelfth. The webhook URL
answers, but nothing is serving behind it, so Maropost’s calls fail too. Orders
still arrive through the 15-minute sync. Contact support.

“Twelfth couldn’t reach that store.” Check the domain. Use the domain you
reach your store on, without https:// or a path.

Maropost’s own documentation:

Previous Shopify Next Qoblex