lipscore / ratingsreviews-magento2
Lipscore - Supercharged Ratings and Reviews
Lipscore - Supercharged Ratings and Reviews
Magento 2 plugin by Lipscore. Tested with Magento 2 versions up to 2.4.7.
Requirements
- Magento Open Source / Adobe Commerce 2.4.x, up to and including 2.4.9
- PHP 7.4 or 8.1 – 8.5 (as supported by your Magento version)
Installation
1. a) Install From Marketplace
1. b) Install Using Composer
composer require lipscore/ratingsreviews-magento2:2.3.0
1. c) Install Manually
- Download the extension
- Unzip the file
- Create a folder
<Magento-root>/app/code/Lipscore/RatingsReviews - Copy the content from the unzipped folder
- Flush cache
2. Enable Lipscore App
bin/magento module:enable --clear-static-content Lipscore_RatingsReviews
bin/magento setup:upgrade
If required:
bin/magento setup:di:compile
3. Configure Lipscore App
Invitations
Stores > Configuration > Lipscore > General > Invitations
When an order reaches the configured Order status, the extension schedules an invitation in Lipscore (POST /invitations). Lipscore sends the invitation email to the customer later, according to your Lipscore settings. The Order status detection setting controls how the status change is detected:
| Option | Behaviour |
|---|---|
| On order status save | Default and previous behaviour. The invitation is scheduled right after Magento commits the order save with the new status, one API request per order. |
| Scheduled check (cron) | An hourly cron job looks for orders in the configured status and schedules their invitations in batches of up to 20 per API request. Use it when statuses are changed outside of Magento's order save, e.g. directly in the database by an ERP or third-party extension. |
The hourly check (lipscore_schedule_invitations, requires a working Magento cron) also retries invitations that failed because of a temporary error, in both modes: after 1, 3, 6 and 24 hours (5 attempts in total). It processes up to 500 orders per run.
Check orders updated within the last (days) (scheduled check only): how far back to look for orders in the configured status without a scheduled invitation. 1, 7 (default), 14 or 30 days. Failed invitations are only retried within this period, so set at least 7 days. Older orders can be scheduled with the bulk action described in Scheduling invitations manually.
How API responses are handled
| Lipscore response | Status | Retried |
|---|---|---|
| 201 Created | Scheduled | – |
| 409 Conflict (invitation exists, or the customer is within a repeat-block period) | Already scheduled, with the Lipscore message | No |
| 400, 422 (invalid invitation data, products blocked) | Rejected, with the Lipscore message | No; correct the data and use the bulk action |
| Timeout, connection error, 5xx, 503, 429, 403 "Feature is not available at the moment" | Failed | Yes, by the hourly check |
| 401, other 403 (credentials, IP, blocked or cancelled site, master account, invitation limit) | Failed | The store is paused for 24 hours or until its API key, secret or URL changes |
Within a batch, Lipscore creates the valid invitations and returns only those. Orders missing from the response are sent again one by one to record their individual result. A timeout, server or account error stops the store for the current run; its remaining orders are processed in the next run. If recording a result fails after Lipscore created the invitation, the order is sent again later and Lipscore answers 409, so no duplicate invitation is created.
Lipscore detects duplicate and repeat-purchase invitations according to the settings in Invitation setup in the Lipscore dashboard.
Invitation log
Every invitation scheduled by the extension (in any mode, and from the order grid) is recorded in the lipscore_invitation table, together with failed ones. An order is scheduled automatically at most once: not again when it returns to the configured status, or after the detection mode is changed. After updating the extension, run bin/magento setup:upgrade to create the table.
The status is shown in Sales > Orders: the Lipscore Invitation column (Scheduled, Already scheduled, Failed, Rejected or Not recorded, with a filter) and the optional Lipscore Invitation Date column. The order view page shows the details in the Lipscore Invitation section, including the Lipscore message.
After switching to the scheduled check, orders from the look-back period are scheduled even if a version before 2.3.0 already sent them; Lipscore detects the duplicates.
Scheduling invitations manually
In Sales > Orders, select orders and choose Schedule Lipscore invitations from the Actions menu. Invitations are scheduled regardless of the order status (also for canceled or closed orders), up to 200 orders at once, in batches of 20. Orders whose invitation is already scheduled (or reported by Lipscore as already scheduled) are skipped; failed and rejected ones are sent again. Use the Lipscore Invitation column filter (Not recorded, Failed or Rejected) together with the order status and purchase date filters to find orders without an invitation. The action requires the Sales > Operations > Orders > Actions > Schedule Lipscore Invitations permission.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.3.0 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-11-20 08:26:06 |
| 2.2.2 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-07-31 11:52:47 |
| 2.2.1 | stable | Not tested | Not yet tested Details | 2026-07-30 08:14:21 |
| 2.2.0 | stable | Not tested | Not yet tested Details | 2026-07-23 10:18:29 |
| 2.1.2 | stable | Fail | Not yet tested Details | 2025-05-09 09:44:01 |
| 2.1.1 | stable | Not tested | Not yet tested Details | 2025-05-06 09:54:23 |
| 2.1.0 | stable | Not tested | Not yet tested Details | 2025-04-23 08:56:52 |
| 2.0.8 | stable | Not tested | Not yet tested Details | 2025-03-31 19:54:15 |
| 2.0.7 | stable | Not tested | Not yet tested Details | 2025-03-19 11:58:44 |
| 2.0.6 | stable | Not tested | Not yet tested Details | 2025-03-04 13:07:50 |
| 2.0.5 | stable | Not tested | Not yet tested Details | 2025-02-20 13:43:16 |
| 1.4.20 | stable | Not tested | Not yet tested Details | 2025-02-19 10:31:03 |
| 2.0.4 | stable | Not tested | Not yet tested Details | 2025-02-19 10:30:38 |
| 2.0.3 | stable | Not tested | Not yet tested Details | 2024-11-29 11:52:32 |
| 2.0.2 | stable | Not tested | Not yet tested Details | 2024-11-29 11:47:09 |
| 2.0.1 | stable | Not tested | Not yet tested Details | 2024-11-29 11:45:41 |
| 1.4.19 | stable | Not tested | Not yet tested Details | 2024-11-29 11:43:32 |
| 1.4.18 | stable | Not tested | Not yet tested Details | 2024-11-29 11:41:03 |
| 1.4.17 | stable | Not tested | Not yet tested Details | 2024-11-29 10:26:44 |
| 2.0.0 | stable | Not tested | Not yet tested Details | 2024-11-21 11:15:25 |
| 1.4.16 | stable | Not tested | Not yet tested Details | 2024-11-12 12:55:59 |
| 1.4.15 | stable | Not tested | Not yet tested Details | 2024-10-30 09:11:23 |
| 1.4.14 | stable | Not tested | Not yet tested Details | 2024-10-24 05:53:40 |
| 1.4.13 | stable | Not tested | Not yet tested Details | 2024-10-14 13:07:40 |
| 1.4.12 | stable | Not tested | Not yet tested Details | 2024-08-09 11:31:10 |
| 1.4.11 | stable | Not tested | Not yet tested Details | 2024-05-08 09:27:36 |
| 1.4.10 | stable | Not tested | Not yet tested Details | 2023-04-03 13:14:32 |
| 1.4.9 | stable | Not tested | Not yet tested Details | 2023-03-30 12:43:30 |
| 1.4.8 | stable | Not tested | Not yet tested Details | 2023-03-08 12:15:37 |
| 1.4.7 | stable | Not tested | Not yet tested Details | 2023-01-16 10:26:56 |
| 1.4.6 | stable | Not tested | Not yet tested Details | 2022-12-08 15:45:12 |
| 1.4.5 | stable | Not tested | Not yet tested Details | 2022-12-02 14:19:21 |
| 1.4.4 | stable | Not tested | Not yet tested Details | 2022-09-26 09:41:31 |
| 1.4.3 | stable | Not tested | Not yet tested Details | 2022-07-12 09:44:00 |
| 1.4.2 | stable | Not tested | Not yet tested Details | 2022-07-06 13:39:30 |
| 1.4.1 | stable | Not tested | Not yet tested Details | 2022-07-05 09:09:19 |
| 1.4.0 | stable | Not tested | Not yet tested Details | 2021-01-28 10:10:49 |
| 1.3.1 | stable | Not tested | Not yet tested Details | 2020-10-31 10:30:17 |
| 1.3.0 | stable | Not tested | Not yet tested Details | 2020-10-19 07:28:16 |
| 1.2.2 | stable | Not tested | Not yet tested Details | 2020-01-17 10:31:01 |
| 1.2.1 | stable | Not tested | Not yet tested Details | 2019-05-06 10:55:28 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2019-05-05 16:53:10 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2018-05-10 05:12:43 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2018-02-14 12:54:29 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2018-02-01 16:51:09 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2017-06-23 12:01:18 |
Requires 18
| Package | Constraint |
|---|---|
| magento/framework | ^103.0 |
| magento/module-backend | ^102.0 |
| magento/module-bundle | ^101.0 |
| magento/module-catalog | ^104.0 |
| magento/module-config | ^101.2 |
| magento/module-configurable-product | ^100.4 |
| magento/module-cron | ^100.4 |
| magento/module-directory | ^100.4 |
| magento/module-eav | ^102.1 |
| magento/module-grouped-product | ^100.4 |
| magento/module-page-cache | ^100.4 |
| magento/module-review | ^100.4 |
| magento/module-sales | ^103.0 |
| magento/module-sales-rule | ^101.2 |
| magento/module-store | ^101.1 |
| magento/module-ui | ^101.2 |
| magento/module-widget | ^101.2 |
| php | ~7.4.0||~8.1.0||~8.2.0||~8.3.0||~8.4.0||~8.5.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Pass | 0 | |
| PHPMD | Warning | 30 | 30 rule violations (UnusedFormalParameter:15, MissingImport:7, IfStatementAssignment:4, UnusedLocalVariable:2, ExcessiveClassComplexity:1) |
| Cpd | Warning | 2 | 2 duplicated chunks spanning 109 total lines (min-lines=5, min-tokens=70) |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.