lillik / magento2-price-decimal

lillik/magento2-price-decimal

Magento 2 Price Decimal Precision

  • LillikPro
magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass Apache-2.0

Are you the maintainer of lillik?

Packagento pulls lillik's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Introduction

The «Price Decimal Precision» Magento 2 extension allows a store administrator to setup a custom display decimal precision for the prices and other currency values (discounts, taxes, sales amounts, etc.) both for the frontend and the backend areas.
The price display settings are individual per currency and per store.
The extension supports an unlimited number of currencies.

alt text

The «Price Decimal Precision» extension allows you to change or delete the decimal number (precision) in a price, that is displayed in the front office of your store. The extentension supports multi store and multi website configuration and can be useful in managing multiwebsites / multisore shops. The ** "Price Decimal Precision" ** extension is a free and fully configurable and can be helpful for your business.

What can the extension do for you?

Remove decimal precision from price

Price with one decimal precision

Features

  • Free and open source and fully configurable extension;
  • Easy to install and unistall;
  • Easy to configurate;
  • Remove or change the price precision from a specific website or store;
  • Supports English translation.

Installation

The preferred way of installing lillik/magento2-price-decimal is through Composer. Simply add lillik/magento2-price-decimal as a dependency:

php composer.phar require lillik/magento2-price-decimal

Configuration

Stores -> Configuration -> Catalog

Contribution

If you have any issues, please contact me or open a bug report in GitHub's issue tracker.

License

The code is licensed under Apache-2.0 License.

TODO

  • Remove decimals in cart and checkout
  • Remove only zero decimal option (description)

Donation

If this project help you reduce time to develop, you can give me a cup of coffee :)paypal

[image: img]

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.0.9 stable Fail Magento 2.4.7-2.4.9 Details 2026-03-17 19:35:00
1.0.8 stable Not tested Not yet tested Details 2021-03-06 21:25:46
1.0.7 stable Not tested Not yet tested Details 2020-03-20 23:05:01
1.0.6 stable Not tested Not yet tested Details 2018-10-23 08:04:50
1.0.5 stable Not tested Not yet tested Details 2018-10-23 07:13:38
1.0.4 stable Not tested Not yet tested Details 2018-06-19 20:31:38
1.0.3 stable Not tested Not yet tested Details 2018-03-22 19:58:55
1.0.2 stable Not tested Not yet tested Details 2018-02-18 19:52:03
1.0.1 stable Not tested Not yet tested Details 2017-09-28 19:37:51
1.0.0 stable Not tested Not yet tested Details 2017-02-14 14:04:02

Requires 2

Package Constraint
php ^5.6 || ^7.0.6 || ^8.0
magento/framework *

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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 19 19 warnings (ruleset: Magento2) — 13 auto-fixable with phpcbf
PHPMD Warning 5 5 rule violations (UnusedFormalParameter:5)
Cpd Pass 0
Composer validate Pass 0

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 9 9
2.4.8 9 9
2.4.9 9 9

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

Unit tests results by Magento and PHP version
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

Integration tests

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit — "./composer.json" does not match the expected JSON schema "./composer.json" does not match the expected JSON schema:
Malware scan Pass 0
License
Apache-2.0
Authors
Make it pay

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.