Remark HB Limited's Cloud ERP Transformation with Eitekh
- Eitekh Marketing Team
- 5 hours ago
- 5 min read
Remark reduced the hours required for financial reporting and monthly VAT/tax filings by 33%, while keeping 90% of the solution aligned to global standards and limiting country-specific deviation to 10%.
Client Context
Remark HB Limited is a manufacturer of beauty and home-care products with 4,500 employees and reported revenue of US$31.8 million. Its operating model combines multi-category manufacturing, a broad brand portfolio, domestic retail and distributor channels, and export ambitions. The company currently has 18 product brands across cosmetics, skincare, personal care, home care, baby care, oral care, men's grooming, and adjacent categories, plus the Herlan retail concept. This profile describes a business that is classified as mid-market based on revenue, yet exhibits enterprise-level characteristics in terms of workforce size and operational complexity.
The ERP program addressed a specific growth constraint: Remark needed global process discipline without losing the ability to meet Bangladesh-specific tax, legal, and reporting requirements. The solution standardized core cloud processes, automated finance and compliance work, and connected distribution, VAT-management, point-of-sale, and secondary-sales processes.
Market expansion multiplies channels, tax regimes, reporting obligations, and data handoffs. Remark's experience shows that disciplined standardization, narrow localization, and deliberate integration can create scale without turning ERP into a custom software estate.
Business Problem
Remark's transformation was driven by the tension between growth and control. The company needed to maintain operating efficiency while meeting local tax, legal, and reporting requirements. Finance work depended heavily on manual processes, creating inaccuracy and delay risk in financial recording, VAT calculations, monthly tax filings, reports, statements, and payments.
The commercial edge was fragmented as well. Secondary sales and retail processes needed to be automated and integrated, and data had to move reliably between the core ERP, distribution management, VAT management, and point-of-sale systems. Without that connection, leadership would face delayed visibility, slower order processing, weak transaction traceability, and a higher risk that channel data and the financial record would disagree.
Remark was expanding brands and categories, developing a large manufacturing base, building a nationwide retail presence, and preparing for exports. In consumer products, every additional brand, pack size, channel, and market expands the number of product records, prices, tax treatments, promotions, orders, inventory movements, quality records, and financial postings that must remain synchronized.
Executive Concern | Problem | Business Consequence |
CFO: compliance and close | Manual financial recording, reporting, VAT calculations, and monthly filings. | Greater error, delay, and audit-exposure risk. |
COO: connected execution | Retail and secondary-sales processes were not sufficiently automated and integrated. | Slower order flow and weaker end-to-end visibility. |
CIO: scalable architecture | Country-specific requirements had to coexist with global standard processes. | Unchecked customization could raise upgrade cost and slow future growth. |
CEO: scale without loss of control | A fast-growing, multi-brand operating model required reliable data across channels. | Growth could increase working complexity faster than management capacity. |
ERP Scope
The transformation established a cloud-based operating and financial backbone that could preserve global consistency while adapting to Bangladesh-specific regulation. The public record supports five primary workstreams:
Financial control and reporting. Accelerate financial recording, management reporting, statements, and the recurring work behind monthly tax and VAT filings.
Country-specific compliance. Configure Bangladesh tax, legal, document, payment, and reporting requirements without altering most of the global template.
Sales and order flow. Improve order processing and accurate tracking while connecting secondary and retail sales to the central record.
Enterprise integration. Exchange data with distribution management, VAT-management, and point-of-sale systems so channel activity is reflected in finance and operations.
Real-time visibility and workflow automation. Replace manual handoffs with real-time reporting, automated workflows, and deeper operational insight.
Delivery Model
Remark adopted SAP S/4HANA Cloud with Localization as a Self-Service.
The design followed a global-template model: 90% of financial compliance was standardized, while 10% of deviation was handled through extensibility. This is strategically significant. It indicates that the team protected the standard cloud core and used controlled extensions for country-specific payments, reports, statements, and regulatory needs rather than allowing local exceptions to dominate the design.
The delivery was integration-led at the business edge. Distribution management, VAT management, and point-of-sale systems continued to perform specialized channel functions while the cloud ERP became the trusted system for financial and operational coordination. The public record does not state whether cutover was phased by company, site, channel, or function, nor whether implementation and support teams were colocated, hybrid, or offshore.
Integrations
Remark's value case depended on connecting the central cloud platform to systems where commercial and compliance transactions originated. SAP identifies the following integrations:
Connected system/process | Business rationale | Operational impact |
Distribution management | Bring distributor and secondary-sales activity into the central business record. | Improves channel visibility, order tracking, and alignment between sales, logistics, and finance. |
VAT management | Support Bangladesh-specific tax calculations, reporting, and filing obligations. | Reduces manual re-entry, compliance delay, and inconsistency between tax records and financial transactions. |
Point of sale | Capture retail transactions from Herlan's store network. | Connects front-line sales activity to reporting, customer service, and financial control. |
Secondary- and retail-sales processes | Automate commercial data flows beyond primary sell-in transactions. | Provides a more complete view of demand and enables faster order processing. |
API-based payments, reports, and statements | Adapt standard cloud processes to local payment and reporting requirements. | Reduces manual handling while preserving a standardized cloud core. |
Business Outcome
The program achieved a finance-and-compliance result with qualitative operational improvements. The 33% reduction is the key ROI anchor, leading to increased labor capacity, faster information access, and reduced compliance risk.
Performance Indicator | Result | Evidence and executive relevance |
Reporting and monthly VAT/tax effort | 33% reduction in hours required. | Releases finance capacity, accelerates information, and reduces dependence on manual work. |
Global standardization | 90% standard process; 10% localized through extensions. | Limits customization debt and supports lower lifecycle risk. |
Bangladesh compliance | Localization requirements successfully implemented. | Strengthens tax, legal, and reporting control. |
Manual work | Reduced through real-time reporting and automated workflows. | Improves consistency and auditability. |
Order and transaction visibility | Deeper insight, faster order processing, and more accurate tracking. | Supports service and operating responsiveness. |
Lessons Learned
Remark's experience yields several lessons for manufacturers and distributors scaling across products, channels, and jurisdictions:
Put regulatory design inside the transformation, not after it. Tax, payment, document, and reporting requirements affect core transactions. Treating localization as a late add-on would have recreated manual work and weakened control.
Use a standard-first architecture with an explicit exception budget. Remark's 90/10 ratio gives leaders a practical governance mechanism: require a business or legal justification for every deviation from standard.
Integrate the commercial edge, not only the general ledger. Point-of-sale, distributor, and secondary-sales data determine whether leaders can see demand, orders, fulfillment, and cash as one operating chain.
Protect future upgrades through controlled extensions. SAP's localization approach keeps country-specific needs separate from the standard core, reducing the likelihood that every cloud update becomes a retrofit project.
Build ownership for ongoing legal change. SAP's product documentation notes that customer local versions and extensions require customer or partner maintenance. Compliance ownership therefore continues after go-live.
Why Eitekh Was Selected
Remark needed global cloud capability combined with deep local expertise in Bangladesh-specific tax, legal, and reporting rules. That fit is consistent with Eitekh'sprofile.
Founded in 2013 and based in North America, we are an enterprise-technology consulting firm spanning advisory, implementation, integration, change management, support, cloud infrastructure, and security. Our SAP practice covers readiness and roadmaps, process and solution analysis, deployment planning, configuration, development, data migration, testing, user adoption, go-live, and optimization.
This case study is also featured as a customer success story on SAP official website.
Comments