ManoMano Connector FAQs

These frequently asked questions cover the most common setup, sync and troubleshooting topics for the TeqStars ManoMano Connector. For a full feature list, see ManoMano Connector Features.

Getting Started

Yes. It is fully compatible with Odoo Enterprise (On-premise and Odoo.SH) and Odoo Community. It is not compatible with Odoo Online (SaaS), because Odoo Online does not support third-party apps.

Yes. Upload your ManoMano offer export in Marketplaces ‣ ManoMano ‣ Products ‣ Import Listings (CSV). Each row is matched by SKU or EAN: a match is updated, otherwise a new product and listing are created. So you get no duplicates. After that, you can run the Import Listings Offers operation to refresh the price, stock and offer status of those listings. This operation only refreshes listings that already exist in Odoo and never creates new ones. Set Import Order After on the instance to your switch date, so older orders are skipped. Details: Import Products In Odoo.

Yes. Create one instance per ManoMano seller account. Each instance has its own API key, B2B and B2C seller contract IDs, warehouse, pricelists and feed URLs.

B2B and B2C are separate seller contracts on the instance. Each contract has its own seller contract ID, its own price grid and its own product feed. Details: ManoMano Seller Contracts.

Yes, for the product feed. ManoMano reads the feed from your feed URL, so your Odoo must be reachable over HTTPS and its base URL must be your public address. Orders and offers are imported by Odoo calling ManoMano, so they need no inbound connection.

Yes. You get a free 60 to 90 minute live screen share with the developer who built the connector. Together you go from a fresh instance to your first live products.

You get free support for the first 60 days after the purchase date. Each app version is sold separately as per Odoo Policy. Details: ManoMano Connector Support Policy.

Setup

Create an instance in Marketplaces ‣ Configuration ‣ Instance. On the Credentials tab, paste the API Key you generate in ManoMano Toolbox and your B2B Seller Contract ID and B2C Seller Contract ID. Click Test Connection, then Confirm. Details: Create a ManoMano instance in Odoo.

No. You need at least one of the two seller contract IDs on the Credentials tab before you can confirm the instance. An instance holds at most one B2B and one B2C contract. When you use both, the two IDs must be different.

The connector imports ManoMano categories and brands for you. If this fails, Odoo tells you so, and you can retry with Fetch Categories and Fetch Brands. Details: Import Categories From ManoMano and Import Brands From ManoMano.

You set up a CSV feed channel in ManoMano Toolbox and paste the feed URL of each seller contract into it, as explained in ManoMano Product Feed.

Each seller contract has its own selling pricelist and a separate retail pricelist for the struck-through price, and the feed price comes from the selling one. Details: ManoMano Seller Contracts.

Only orders with the statuses you list in Import Order Status on the instance. Add Any to import every status. Orders placed before the Import Order After date are skipped.

Add one workflow row per ManoMano order status on the Workflow tab of the instance. Each status can have only one workflow. Details: ManoMano Order Workflow Configuration.

Yes. Turn on Create Company Contact? on the instance. When an order carries a company, a company record is created and the billing and shipping contacts are placed under it. Otherwise a single customer is created. Details: Customer Creation During Order Import.

The carrier name is sent to ManoMano exactly as written when a shipment is declared. Every listing also needs at least one shipping grid (carrier) before it can go into the feed. Details: ManoMano Carriers.

Daily Use

No. Products are matched by SKU (Internal Reference) first, with the EAN (barcode) as a fallback. Offers read back from ManoMano and imported orders use the same matching, so no duplicates are created.

Run the Export Listings operation. The products are written to the feed for both contracts. They are marked as listed once ManoMano confirms the offer. The Verify B2B Feed Status and Verify B2C Feed Status scheduled jobs check this for you. Details: Export Products From Odoo.

Run Update Offer Price or Update Offer Stock for a seller contract. These send the change through the Offers API, without waiting for the feed cycle. ManoMano processes them in the background, so the change can take a while to go live. Run Import Listings Offers afterwards to confirm the result. Details: Export Price From Odoo and Export Inventory From Odoo.

Yes. In the Import Orders operation, enter one Marketplace Order ID, or several IDs separated by commas. The date range is then ignored. With only a date range, all orders updated in that range are imported for all seller contracts. Details: Import ManoMano Orders In Odoo.

Open the sales order and click Accept Order. Details: Accept ManoMano Orders From Odoo.

The Update Order Status operation declares the carrier, tracking number and tracking URL of your validated deliveries. Only deliveries that are done and not yet reported are sent, so none is sent twice. The Export Order Status/Tracking Information scheduled job does this for you. Details: ManoMano Update Order Status From Odoo.

Open the credit note in Odoo and click Refund in ManoMano. Choose the Refund Reason (Customer Cancellation or No Stock) and set the quantity for each product. ManoMano takes shipping as yes or no, so Refund Shipping Charges? refunds shipping in full or not at all. Details: Refund ManoMano Orders From Odoo.

Open the instance and go to the Automatic Jobs tab. There you set the schedule of each job, such as the order import, price and stock export, feed regeneration and tracking export. You can also click Run Manually to run a job right away.

Odoo tells you when the feed URL of an instance changes. Update it in your ManoMano Seller Central store. Details: ManoMano Product Feed.

Troubleshooting

One bad record never blocks the queue. Each failure is logged with the SKU or ManoMano order reference and the error message. Open the queue in Marketplaces ‣ Queues, fix the cause and click Retry on the failed line. You find all messages in Marketplaces ‣ Queues ‣ Logs.

Each product needs at least one image and at least one shipping grid (carrier). A product that misses one of them is skipped, and the log lists the skipped SKUs. Add the image or the carrier, then update the listing again.

Open the listing item and go to the Listing Offer tab. Offer Errors shows why ManoMano rejected the offer. Fix what it shows, update the listing, then run Import Listings Offers to read the new status back. Details: Update Products From Odoo.

Check the log for the order. The common causes are:

  • No workflow exists for the order status. Add a matching row on the Workflow tab of the instance.

  • No Odoo product has the SKU or barcode of an order line. Create the product with that Internal Reference or Barcode, then import the order again.

  • The order was placed before the Import Order After date.

  • The customer or address details are missing on the order.

  • The order is already in Odoo, so it is not imported again.

This operation only refreshes the price, stock and status of listings that already exist in Odoo. Import or export your products first, then run it again.

ManoMano did not answer at that moment. Wait a few minutes and try again. If you get “ManoMano API Key is missing”, fill in the API Key on the Credentials tab of the instance.

The order has no seller contract reference, so ManoMano cannot tell which contract to refund. Also make sure you set a quantity on at least one product before you click Send Refund.

See also