Multiple EANs per product
- One year of technical support and lifetime updates; from the second year, support is extended for €27.20/year and includes taking on your general improvement ideas for the module.
- Renews automatically; cancel whenever you want, with no minimum term.
- One year of technical support and lifetime updates; after that, support ends (with the subscription it is extended for €27.20/year).
- A single payment, with no automatic charges.
A single barcode system for the entire warehouse: multiple codes per item, the same code for multiple items, checkout codes that total multiple units, and scale labels. Shared for purchasing, expiration dates, and picking.
Compatible with PrestaShop 8 and 9.
Store
It shouldn't have two codes. But it does.
The manufacturer changes the EAN between production runs, the box has its own code, the scale prints a different one on each package, and the supplier reuses theirs. PrestaShop stores one EAN per item. RKR Multiple EANs accommodates all the others.
When a code can be two items, ask
Grabbing the first item that matches is the fastest way to make a mistake without any warning: the error is discovered weeks later, in the inventory or when the customer opens the package. That's why the initial check focuses on what's possible here and now —the lines on that delivery note, those on that wave, the items with expiration dates—which almost always resolves the issue automatically. And if there are still several, ask. It takes two seconds.
What it brings
Discover the duplicate EANs you already have
The Conflicts screen displays shared codes, codes that clash with the catalog, duplicate EANs already in your product listings—PrestaShop doesn't warn you about these, and none of its screens show them—, mismatched check digits, and orphaned codes. Almost every store that's been around for years has some of these and never knew it.
It installs and works right away: the registration expands the catalog, it doesn't replace it . The EANs you already have continue to work. It connects with RKR Purchase Manager, RKR Expiration Dates, and RKR Picking, which are installed separately and in any order and continue to function without it. Scale rules are intentionally disabled: the digit allocation is determined by each scale.
Compatible with PrestaShop 8.x and 9.x
Developed and maintained by REKIRE
v1.0.1
Arranged
- All screens returned HTTP 500 (
ClassNotFoundErrorinRekire \Module\MultiEan\Controller\Admin\CodeController) as soon as the back office cache was hot. PrestaShop only loadsmodules/When the kernel started, and the module didn't include it:/vendor/autoload.php config/autoloader.phponly runs when compiling the container. Nowvendor/(just the Composer autoloader, without dependencies) is in the module and in the repository. Incidentally,composer.jsonwasn't valid JSON (\Mnot escaping the namespace).
4 other products in the same category
Product Videos
Product Videos
También podría interesarte
Questions and answers
Nobody has asked anything about this product yet.