Skip to content

Changelog

Our commitment: transparency and longevity

This module is a one-off purchase: no subscription, no hidden cost. In the interest of full transparency and technical follow-up, this page records every change, fix and improvement made to the module. Each version is designed to update smoothly in one click from your PrestaShop back office, with no data loss and no interruption of service, while keeping up with the evolutions of PrestaShop.

All notable changes to the Octopia Sync module are documented on this page. The format is based on Keep a Changelog.

Each release groups its changes into the following sections:

  • Added — new features or capabilities.
  • Changed — changes to how an existing feature behaves.
  • Fixed — bug fixes.
  • Removed — features or options that were taken out.

1.2.16 — 2026-09-06

Changed

  • The module no longer presents itself as a payment module. Orders are created exactly as before.
  • Two payment hooks that did nothing were removed. No payment is offered at checkout.
  • The name shown in the module manager now says what the module is for.
  • The module description was rewritten.
  • Constructor parameters that no class ever read were removed.
  • Coding standard issues reported by the Addons validator.
  • The invoicing tutorial link now sits once at the top of the tab. The user guide is bundled with the module in three languages.
  • Shipments declared to the marketplace carry the real parcel number and tracking link when you ship with Boxtal.
  • In PrestaShop tariff mode, the additional shipping cost is now a share of the final cost rather than a fixed amount, at all three levels.
  • The additional shipping cost of a product is now part of the base shipping cost, as it is in PrestaShop. The cost per extra item comes from the Transport field alone.
  • Shipping costs calculated from PrestaShop now include your handling charges, for carriers set to add them.
  • The Relais Colis pickup mode is no longer offered by the marketplace. It stays visible in Transport, greyed out, and is never sent in an offer.
  • The line under each message of a discussion names the parties in plain words and states who the message went to and whether they have read it.

Fixed

  • Redundant guards reported as blocking by the Addons validator.
  • The cron log reported the same wording for every failed order import.
  • A product description could reach the marketplace as the word "Array" instead of its text.
  • Opening the module from the module manager failed on PrestaShop 9.
  • Static analysis findings raised by the Addons validator, including a catalogue search guard that could never catch anything.
  • Discussions never got marked as read. Opening one now marks everything waiting in it.

1.2.15 (Patch — improvement)

Changed

  • The Octopia tab of the product sheet restores the account set aside by a link opened from an order.

1.2.14 (Patch — improvement)

Changed

  • The account switch performed by "Ongoing discussion" is now temporary: the account you had chosen comes back as soon as you open another page of the module.

1.2.13 (Patch — bug fix)

Fixed

  • "Ongoing discussion" on an order opened the messaging of the account selected in the back office rather than the one owning the order.

1.2.12 (Patch — bug fix)

Fixed

  • Contacting the customer from an order used the account selected in the back office rather than the one owning the order — a problem only with several accounts on one shop.

1.2.11 (Patch — bug fix)

Fixed

  • The invoices cron did nothing at all with the standard source: it stopped before reaching it.

1.2.10 (Patch — hardening)

Fixed

  • An invoice the marketplace never confirms receiving is sent again after six hours, instead of staying Pending for ever with no way to act on it.

1.2.9 (Patch — bug fix)

Fixed

  • An invoice already attached to its Octopia order still offered the attach action, inviting you to send it a second time.

1.2.8 (Patch — bug fix)

Fixed

  • The invoices cron URL stayed hidden behind a notice saying invoicing was disabled, for a merchant using the standard invoice.

1.2.7 (Patch — bug fix)

Fixed

  • Attaching a PrestaShop invoice to an Octopia order raised an error and did nothing.

1.2.6 (Patch — bug fix)

Fixed

  • The tax detail of the invoice listed the products alone, with no line for the delivery, while the total VAT did include it.

1.2.5 (Patch — bug fix)

Fixed

  • An imported order could end up with three different totals — one on the order page, another on the invoice, a third on the payment, with a warning that the customer had underpaid.

1.2.4 (Patch — bug fix)

Fixed

  • A PrestaShop invoice attached to an Octopia order stayed shown as never delivered, still offering the attach action, although the file had gone through.

1.2.3 (Patch — bug fix)

Fixed

  • The real cause of the doubled VAT rate on imported orders: the VAT of the delivery was being added to the VAT of the goods. Each is now read for what it applies to, and the delivery VAT comes straight from the marketplace.

1.2.2 (Patch — bug fix)

Fixed

  • Shipping was invoiced as untaxed on imported orders whose carrier has no tax rule of its own. With the marketplace tax source, shipping now follows the VAT of the goods it carries.

1.2.1 (Patch — bug fix)

Fixed

  • Imported orders still showed a doubled VAT rate with the marketplace tax source — 40% on a line taxed at 20%. Fixed at its source.

1.2.0 (Minor — invoicing sources)

Added

  • Invoicing now has a source, chosen per account: None, Standard invoice or Abby.
  • Standard invoice delivers your PrestaShop invoice to your Octopia orders exactly like Abby does — to the customer in a discussion, or attached to the order on Cdiscount. You have nothing to create: it is picked up as soon as PrestaShop issues it.
  • None leaves invoicing out of the module: nothing is created, nothing is sent. Nothing is erased either, so you can pick a source again whenever you want.

Changed

  • An order can only be invoiced once, whichever source issued it, and switching source never leaves an invoice undelivered.
  • Delivery follows the marketplace: Cdiscount takes the invoice attached to the order, the others in a discussion.

1.1.99 (Patch — consistency)

Changed

  • The empty state of the invoicing section reads the same whichever source is active.

1.1.98 (Patch — bug fix)

Fixed

  • No action showed on a PrestaShop invoice row of the order page. Send, attach and download now appear there, and the row reads like the Abby ones.

1.1.97 (Patch — hardening)

Changed

  • The invoices cron only takes invoices issued since you activated the source, instead of queueing every past one for delivery. Opening an order still records its invoice whatever its date.

1.1.96 (Patch — hardening)

Changed

  • Your PrestaShop invoice is now also picked up when you open the order page, so the section works even if your cron is not running.

1.1.95 (Patch — bug fix)

Fixed

  • An order already invoiced by one source could be invoiced again by the other after you changed source, leaving your customer with two documents for one purchase. An order can now only be invoiced once, whichever source issued it.

1.1.94 (Patch — bug fix)

Fixed

  • The order page kept offering "Create the invoice" while the standard invoice was selected, and returned an error when pressed. That button belongs to Abby alone: PrestaShop issues its invoice by itself.

1.1.93 (Patch — bug fix)

Fixed

  • The invoice section of the order page only showed when Abby was the source. It now shows for either one.

1.1.92 (Minor — new feature)

Added

  • The Standard invoice panel gets its own delivery settings: auto-send, attach to the order, and the message sent to the customer with the invoice.

Changed

  • Each source keeps its own settings. Configuring one never governs the other, and switching between them leaves each configuration where it was.

1.1.91 (Minor — new feature)

Added

  • The invoice history on the order page shows both sources, each line saying where it came from. Switching from one to the other no longer hides what was sent before.

Changed

  • The manual actions follow the document rather than the source currently selected.

1.1.90 (Minor — new feature)

Added

  • Your PrestaShop invoices are now delivered to your Octopia orders, exactly like the Abby ones: sent to the customer in a discussion, or attached to the order on Cdiscount, with the same switches and the same cron. You have nothing to create — the invoice is picked up as soon as PrestaShop issues it, and orders invoiced before are picked up too.

Changed

  • Whatever source you select, the cron and the manual actions keep an eye on both. Switching from one to the other never leaves an invoice stranded.

1.1.89 (Patch — bug fix)

Fixed

  • Imported orders could show a doubled VAT rate on the invoice — 40% where the marketplace charged 20%.

1.1.88 (Patch — groundwork)

Changed

  • Internal groundwork for delivering PrestaShop invoices. No change to how the module behaves.

1.1.87 (Patch — groundwork)

Added

  • Groundwork for delivering PrestaShop invoices to Octopia orders. No change to how the module behaves yet.

1.1.86 (Minor — bug fix)

Fixed

  • Invoice delivery now follows the marketplace: Cdiscount takes the invoice attached to the order and refuses it in a discussion, every other channel does the opposite. The cron routes each order accordingly, and the manual actions on the order page appear only where their channel accepts them.

Changed

  • The delivery channels description is rewritten around that rule.

1.1.85 (Patch — in development)

Changed

  • Invoicing tab: the Abby on/off switch is gone, the Source selector above now turns it on or off — one control instead of two doing the same thing.

1.1.84 (Minor — new feature)

Added

  • Invoicing tab: a Source section where you choose who issues the invoices of your Octopia orders — the standard PrestaShop invoice, or Abby. The panel below follows your choice.

Changed

  • The E. Invoicing tab is renamed Invoicing, now that it covers both.

1.1.83 (Patch — cleanup)

Removed

  • The marketplace reference no longer appears in the invoice Comment: it was showing twice since it moved under the Carrier table. Whatever you write in that Comment is left untouched.

1.1.82 (Minor — new feature)

Added

  • PrestaShop invoices of imported orders now show the marketplace reference just under the Carrier table. Any legal free text of your own is kept, the reference is simply added below it.

1.1.81 (Patch — bug fix)

Fixed

  • The sales channel and order number added in 1.1.80 did not appear on the invoice when the order was imported straight into a status that issues one.

1.1.80 (Minor — new feature)

Added

  • PrestaShop invoices of imported orders now show the sales channel and the Octopia order number in their Note, just like the Abby ones. Anything you have written in that note yourself is kept.

1.1.79 (Patch — bug fix)

Fixed

  • PrestaShop invoices for imported orders, with VAT applied on import set to Marketplace: a line showed its VAT amount in the totals but with no rate and no detail. This only happened when the product carries no tax rule in PrestaShop while Octopia charges VAT on it. The rate and its detail now appear on the invoice.

1.1.78 (Patch)

Changed

  • On PrestaShop 8.0, the Reference column of the products list is now renamed "Ref. / EAN / GTIN" like on the other versions, and given the same width. That list writes its column titles itself, so the title is changed in the page once it is displayed.

1.1.77 (Patch — bug fix)

Fixed

  • From PrestaShop 8.1, searching a GTIN or a combination reference in the products list returned nothing, even though the column was correctly renamed.

1.1.76 (Patch — revert)

Fixed

  • The products list search no longer worked after the previous update. Reverted to the behaviour of 1.1.73.

1.1.75 (Patch — bug fix)

Fixed

  • From PrestaShop 8.1, searching a GTIN or a combination reference in the products list returned nothing.

1.1.74 (Patch — bug fix)

Fixed

  • On PrestaShop 8.0, a GTIN search returned nothing when you came back to the products list, even though the search field still showed what you had typed.

1.1.73 (Minor — new feature)

Changed

  • The GTIN option now widens the Reference column of the products list instead of adding one: searching it finds a product by its reference, its GTIN / EAN, or the reference or barcode of any of its combinations. The column is renamed "Ref. / EAN / GTIN".
  • The setting moves next to Export type. It matters most when you export by ID or Shop ID: the reference sent to Octopia is then a generated key, and the barcode becomes the only value you can search for to match a product between the two back offices.

1.1.72 (Patch — bug fix)

Fixed

  • The GTIN was shown twice on the products list, in its own column and inside the Reference column. It now appears only in its own column. Searching the Reference box still finds a product by its reference or by any of its barcodes.

1.1.71 (Minor — new feature)

Added

  • The products list search of PrestaShop 8.0 is now covered as well, alongside the more recent versions.

1.1.70 (Patch — documentation)

Changed

  • The setting now explains when the GTIN / EAN column shows on PrestaShop 8.0: turn on "New product page" in Advanced parameters > Experimental features. It is on by default from 8.1.

1.1.67 (Patch — bug fix)

Fixed

  • The GTIN / EAN cell stayed empty for products whose barcodes are on their combinations.

1.1.66 (Minor — in development)

Changed

  • Products list, GTIN / EAN column: when the barcodes are on the combinations rather than the product itself, the cell shows the first one followed by how many others there are. Searching any variant barcode still finds its product.

1.1.65 (Patch — bug fix)

Fixed

  • The GTIN / EAN column did not appear on the products list on PrestaShop 8.0.

1.1.64 (Patch — in development)

Changed

  • The GTIN / EAN column of the products list is now wide enough for a barcode and its search field to stay on one line.

1.1.63 (Patch — bug fix)

Fixed

  • The GTIN / EAN column did not show up on the products list even with the option enabled.

1.1.62 (Minor — new feature)

Added

  • Settings, Catalogue section: a new option adds a GTIN / EAN column, with its search filter, to the PrestaShop products list — like the Octopia ID column on the orders list. Disabled by default.

1.1.60 (Patch — bug fix)

Fixed

  • Products import: the link to a product already in your catalogue opened an "Invalid token" page.
  • Ten texts showed in English whatever your back-office language — mostly on the Categories and Settings tabs. All are now translated.

1.1.59 (Minor — in development)

Added

  • Products import: if the product is already in your catalogue, its PrestaShop name is shown as a link to its page — combinations included, named with their attributes.

Removed

  • The Octopia permissions line on the result card.

1.1.58 (Patch — in development)

Fixed

  • Products import: when your back-office session had expired, the screen reported a failure instead of offering to reload the page as the rest of the module does.

1.1.57 (Patch — in development)

Changed

  • Products import: errors are now shown in a proper alert box, and say what actually went wrong instead of a generic failure message.

1.1.56 (Patch — bug fix)

Fixed

  • The Settings screen still returned an error page after the previous update. Fixed.

1.1.55 (Patch — bug fix)

Fixed

  • The Settings screen returned an error page after the previous update. Fixed.

1.1.54 (Patch — bug fix)

Fixed

  • Products import: the screen did nothing when the back office was in French. Some translated texts broke the page script as soon as they contained an apostrophe.

1.1.53 (Minor — in development)

Added

  • Products import: each result now tells you which model, profile and PrestaShop category the product falls under, and names the tab where to create the missing one when the chain is incomplete.

1.1.52 (Minor — in development)

Changed

  • Products import: results are shown as product cards — picture, label, description, GTIN, SKU, brand, category and language — instead of raw data. Pictures are browsable with previous / next arrows.

1.1.51 (Patch — in development)

Changed

  • Products import: internal work on the catalogue search.

1.1.50 (Patch — in development)

Removed

  • Products import: the sales channel selector is dropped. It read the offers published under your own account, which tells you nothing about a catalogue product you do not sell yet — exactly what this screen is for.

1.1.49 (Minor — new feature, in development)

Added

  • Products import: pick a sales channel before searching. The search now reads both the Octopia product sheet and your offer on that channel, since a PrestaShop product needs the label and images from one and the price and stock from the other.

1.1.48 (Minor — new feature, in development)

Added

  • Products import: search the Octopia catalogue by GTIN / EAN, up to 10 codes at once. The screen is still under development and only shows the raw result for now.

1.1.47 (Patch — declaration)

Added

  • The module manager no longer asks you about multistore: the module declares itself as partially compatible, which matches how it works — one Octopia account per shop, so you pick a shop before configuring it.

1.1.46 (Patch — bug fix)

Fixed

  • Dashboard: switching account from the header bar had no effect, the page reloaded on the same account. It now switches like on the other screens.

1.1.45 (Patch — cleanup)

Removed

  • Dashboard: the tutorial notice is dropped, it was never displayed.

1.1.44 (Minor — new feature)

Added

  • Products & Offers: a new Products import tab, which will let you create PrestaShop products from the Octopia catalogue.

Changed

  • Small clean-up of the tutorial notice on the Products, Offers and Customer service screens.

1.1.43 (Patch — bug fix)

Removed

  • The automatic backup written before an update is dropped. Producing it during the update was heavy enough to make the update itself fail on a large shop, leaving the module disabled. Export a backup from the Backup tab before updating instead — it is the same file, taken when you choose.

1.1.42 (Patch — bug fix)

Fixed

  • Updating the module now restores any event the module was not attached to, so a feature added by a previous version cannot stay inactive. The Diagnostic panel keeps showing the current state.

1.1.41 (Patch — bug fix)

Fixed

  • Messages relayed by e-mail: the module added "Order - " in front of the object you typed. An object using the whole 50-character budget ended up as a 71-character subject. Your object is now sent exactly as you wrote it.

1.1.40 (Patch — bug fix)

Fixed

  • A feature added by an update could stay inactive without any sign, if PrestaShop had not attached the module to the corresponding event. The module now checks and repairs this by itself when you open one of its screens.

Added

  • Diagnostic panel: a line telling you whether the module is correctly connected to everything it needs in PrestaShop.

1.1.39 (Patch — bug fix)

Fixed

  • The module could fail to install with the message "module installation failed, it has been disabled". A single optional liaison PrestaShop declined was enough to abort the whole installation; that can no longer happen.

1.1.38 (Minor — new feature)

Added

  • Deleting a shop now also deletes the Octopia accounts attached to it and all their data. Until now those rows stayed in the database with no way to see or remove them. Your other shops are not affected.
  • Uninstalling the module now asks for confirmation and tells you exactly what will be lost.
  • Before a module update, a settings backup of each account is written automatically to the download/octopiasyncs-pre-upgrade/ folder of your shop. It uses the same format as the Backup tab and can be restored from there.

Changed

  • The multistore notice pointed to the shop selector on the left; it is on the right.

1.1.37 (Patch — bug fix)

Fixed

  • E-invoicing: the invoice message box and its language selector could be missing entirely, leaving only the variable list and the reset link. This happened when the shop's default language was not one of the languages assigned to that shop.

1.1.36 (Patch — bug fix)

Fixed

  • Multistore: on a shop other than the one you installed the module from, all the tabs of the module screens were displayed one under another instead of switching. The module now loads its stylesheet and script itself on its own pages, so this cannot happen again.

1.1.35 (Patch — bug fix)

Fixed

  • Creating an attribute from the Mappings tab failed with an error page on PrestaShop 8 and 9, because PrestaShop renamed the class behind it. Creating a feature was never affected.
  • Order import: on PrestaShop 9, a failed order creation ended on an error page instead of the clear "order could not be created" message.

Changed

  • Internal code-quality pass, with no change to how the module behaves.

1.1.34 (Patch — security hardening)

Changed

  • Internal hardening of the back-office screens: every value the module prints is now escaped, with no exception left. No visible change.

1.1.33 (Patch — bug fix)

Fixed

  • Restoring a full backup ended on a 500 error about the cookie size. The preview summary was kept in the browser cookie, and a full backup lists every table of the module, which alone filled most of the space PrestaShop allows. It is now stored server-side, next to the uploaded backup, and still discarded as soon as you apply or cancel the restore.
  • Messages shown after saving a form are now shortened when unusually long, for the same reason.

1.1.32 (Patch — bug fix)

Fixed

  • Full backup, preview and restore crashed with "Unknown column 'id_account' in 'WHERE'" as soon as the archive contained value correspondences. Those correspondences are global, shared by every account of the shop, so their table has no account column. The export already handled that; the import now does too: the table is counted as a whole, never wiped on restore — which would have destroyed the other accounts' correspondences — and merged so a correspondence already present on the shop is kept. The preview now names the table "Value correspondences" instead of showing its raw database name.

1.1.31 (Patch — bug fix)

Fixed

  • Offer export, Tax management (Settings) set to "No": the Vat attribute was written with an empty value in the offer XML, which Octopia rejects. It is now written as 0. Applies to both the full export and the stock/price export. No effect when Tax management is left on "Yes" (default).

1.1.30 (Patch — bug fix)

Changed

  • Image type (Settings) is now stored by id instead of by name, so renaming a PrestaShop image type no longer breaks the setting (only a deletion can, already handled since 1.1.29). Existing installs are migrated automatically; a name that no longer matches any image type falls back to "Original".

1.1.29 (Minor — new feature)

Added

  • Automatic upkeep of three settings that reference other PrestaShop objects by id/name: if the merchant deletes the referenced PrestaShop object, the setting is reset instead of silently dangling.
    • Image type (Settings): resets to the new "Original" option if the referenced image type is deleted.
    • VAT rule for service fees (Settings, INTERBCA): resets to "No tax (amount is TTC)" if the referenced tax rules group is deleted.
    • Order status mapping (Settings, also read by the order import cron): resets the affected entry to "Not mapped" if the referenced PrestaShop order status is deleted.
  • New "Original" image type option (Settings): sends the image exactly as uploaded, with no PrestaShop resizing. Never goes stale since it doesn't reference a PrestaShop image type.

1.1.28 (Patch — bug fix)

Fixed

  • A pinned category (used to resolve profile ambiguity) could go stale: if the category was later removed from the product, or unmapped, the pin kept being silently applied, possibly routing the product through the wrong profile with no warning. The pin is now revalidated against the product's current categories on every build; a stale pin is ignored (falls back to normal resolution) and the profile-selection warning reappears if the product is still ambiguous. Applies to both the product push and the offer export. A still-valid pin behaves exactly as before.

1.1.27 (Patch — bug fix)

Fixed

  • Transport, PS mode: the shipping cost computed from a mapped PrestaShop carrier (min cost) was tax-excluded (HT) instead of TTC like every other price the module exports. The carrier's own tax rule (set on the carrier in PrestaShop's Shipping settings) is now applied.

1.1.26 (Patch — bug fix)

Fixed

  • The full backup failed as soon as it contained value correspondences: unlike everything else, those are shared by every account of the shop and were treated as belonging to one. They are now saved as they are.

1.1.25 (Patch — bug fix)

Fixed

  • Cron report showed "API calls: 0" and an empty request/response trace: logApi() returned early when Debug (persistent logging) was off, before collecting the in-memory trace. The trace is now always collected; only the DB write stays gated by the Debug toggle.

1.1.24 (Patch — bug fix)

Fixed

  • Cron report e-mail was never sent due to an error while clearing old reports; fixed so the report is recorded and its e-mail sent.

1.1.23 (Patch — diagnostics)

Added

  • Cron report diagnostics logged in the module logs (gating + Mail::Send result) to diagnose missing report e-mails.

1.1.22 (Minor — new feature)

Changed

  • Manual customer contact (e-mail relay): the object is now a free-text field instead of a predefined list.

1.1.21 (Patch — bug fix)

Fixed

  • Contacting the customer (messaging shortcut, manual invoice send and invoices cron) falls back to the e-mail relay instead of erroring when the sales channel configuration cannot be read. Centralized in the API client.

1.1.20 (Minor — new feature)

Added

  • Clear, localized (FR/ES/EN) error messages for every Octopia API call, mapped centrally by HTTP status code; the alert shows only the clean message (endpoint/detail stay in the log). Messaging falls back to the e-mail relay when the sales channel configuration cannot be read.

1.1.19 (Patch — bug fix)

Fixed

  • Fixed a "No active account" error when saving the cron report e-mail; the per-account e-mail migration is also re-run for installs already on 1.1.18.

1.1.18 (Patch — bug fix)

Fixed

  • The cron e-mail report is now configured per account (not per shop), so it is reliably sent with &report=1 whatever the shop context. Existing addresses are migrated automatically.

1.1.17 (Patch — bug fix)

Fixed

  • The Mappings tab now only lists fields that use an existing feature/attribute with a predefined Octopia value list; free-form PS feature/attribute fields (no Octopia list) are no longer shown.

1.1.16 (Patch — bug fix)

Fixed

  • Fatal error during order import (protected trans() method) is fixed; the importer now uses the public translator.

1.1.15 (Patch — bug fix)

Fixed

  • The "Follow our online tutorial" banner was missing on the product page panel; it is now displayed.

Changed

  • Wired the online tutorial links across the tabs to the published documentation.

1.1.14 (Patch — bug fix)

Fixed

  • "Create as attribute" failed in PrestaShop while "Create as feature" worked; the attribute group is now created correctly (required is_color_group field set) and associated with the current shop.

1.1.13 (Minor — new feature)

Added

  • "Map with" mode: reuse an existing PrestaShop feature/attribute for a specific field instead of creating a new one, and match each PrestaShop value to an Octopia value in the new Mappings tab. Ideal for large catalogs already filled. Stored by PS value ID; unmapped values send nothing at export.

1.1.12 (Patch — bug fix)

Fixed

  • Sales-season discount priority: a manual specific price now always wins over a catalog price rule — (1) manual on product, (2) manual global, (3) catalog rule on product, (4) catalog rule global — most recent within each level.

1.1.11 (Patch — bug fix)

Fixed

  • Sales-season discount now follows a clear rule: a product-level reduction always wins; the shop or global reduction only applies otherwise. The most recently created one wins within that level, and the discount is always exposed over the configured sales-season window.

1.1.10 (Patch — bug fix)

Fixed

  • Sales-season discount selection now matches what a public (non-logged) visitor sees (visitor group + default country/currency), so a product reduction is no longer wrongly skipped in favour of a global one. Quantity-tiered reductions are excluded. Sales-season date rules are unchanged.

1.1.9 (Minor — new feature)

Added

  • A created field's value turns green once the model is saved, indicating the value is used when publishing offers (grey while created but not yet saved).

1.1.8 (Patch — bug fix)

Fixed

  • Deleting the created feature/attribute in PrestaShop is now cleaned up immediately, so a mandatory field can no longer publish empty from a phantom mapping when pushing products.

1.1.7 (Patch — bug fix)

Fixed

  • Creating a feature/attribute from a field with a long value list could return an HTML error instead of JSON; the creation now uses a POST request and works regardless of the list length.

1.1.6 (Patch — bug fix)

Fixed

  • Deleting the created feature/attribute in PrestaShop now also clears the model mappings that pointed to it, so no phantom mapping remains.

1.1.5 (Patch — bug fix)

Fixed

  • Deleting the created feature/attribute in PrestaShop no longer leaves the field stuck: orphan bindings are detected and cleaned, and the "Create as …" button comes back.

1.1.4 (Patch — bug fix)

Fixed

  • The feature/attribute created from a specific field is now global to PrestaShop (not tied to the active Octopia account) and can exist as both a feature and an attribute for the same field, depending on where it is Recommended/Optional or Mandatory. Also fixes a created field showing the create button again when reopening a model.

1.1.3 (Minor — new feature)

Added

  • Specific fields with predefined Octopia values can be created directly in PrestaShop from the model with a single button — "Create as attribute" (Mandatory) or "Create as feature" (Recommended/Optional) — building the object with all Octopia values at once. Once created, the mapping is locked to that object and the button disappears; deleting the object in PrestaShop is the way to undo.

1.1.2 (Minor — new feature)

Added

  • Fallback e-mail delivery for seller-initiated messages. When a sales channel forbids the seller from opening a discussion (e.g. Cdiscount), the "Contact customer" panel now sends the message as an email to the order's masked customer address, which Octopia relays to the buyer. Includes an extensible object selector (currently: tracking number), a per-order HMAC token so the module's own email-blocking liaison lets the relay mail through (the token is never shown in the subject or body), and a delivery notice ("may take up to 1 hour to be processed by Octopia"). File attachments (up to 3, 4 MB total) can be added, like the discussion composer.
  • The invoice send (manual and cron) uses the same fallback delivery: when the channel forbids seller-initiated discussions, the invoice is emailed to the masked customer address with the PDF attached, instead of failing.

1.1.1 (Patch — bug fix)

Fixed

  • Eco-taxes were swapped in the offer output: the furniture eco-participation (eco_mobilier) was sent as EcoPart and the DEEE eco-participation as DeaTax. They are now mapped correctly — eco_mobilier → DeaTax (DEA), eco_deee → EcoPart (DEEE).

1.1.0 (Minor — new feature)

Added

  • GDPR support: the module now responds to customer data export and erasure requests (marketplace buyer reference and Abby customer id), as required for PrestaShop Addons.

Fixed

  • Carrier mapping no longer breaks when a merchant edits a carrier: the stored PS-carrier link is repointed to the new carrier version automatically (actionCarrierUpdate).
  • Service-fee line (virtual product mode): the INTERBCA fee line is now always listed last on the order page instead of floating to the top.

1.0.9 (Minor — new feature)

Added

  • The marketplace commission (amount incl. and excl. VAT, and rate) is now shown on the order panel and per line in the order detail.

1.0.8 (Patch — bug fix)

Fixed

  • Orders could not be declared shipped when a line was numbered 0 (single-line orders were never shippable, and the first line of multi-line orders was skipped).

1.0.7 (Patch — bug fix)

Fixed

  • The Octopia ID column in the back-office orders list is now wide enough to show the marketplace ID on a single line.

1.0.6 (Minor — new feature)

Added

  • When an Octopia order is cancelled, the cancellation reason and who requested it are now copied into the PrestaShop order's private note on import.

1.0.5 (Patch — bug fix)

Fixed

  • Order import and offer sync now work on PrestaShop 8.0 (removed an instruction that the bundled MariaDB rejected).

1.0.4 (Patch — bug fix)

Fixed

  • Excel export now works on PrestaShop 8.0 (the styled table feature is skipped when the bundled library is older; the export and its filters still work).

1.0.3 (Patch — bug fix)

Fixed

  • Fatal error that could break the cron report page.

1.0.2 (Patch — bug fix)

Changed

  • The order page now shows the Message and Upload badges independently, so an invoice that was both sent to the customer and attached to the order displays both.

Fixed

  • The Message badge is now clearly colored on PrestaShop 8 and 9.

1.0.1 (Minor — new feature)

Added

  • Invoices can now be officially attached to the marketplace order (Octopia orders-invoices), where the customer can retrieve them. Enable it in the E-Invoicing tab; the invoices cron uploads them in bulk and you can also attach an invoice manually from the order page.

1.0.0 (Major — initial release)

Added

  • Initial release.