Step inside DEMA's development journey

Feature Ideas: Dive into a community-driven pool of innovation where your voice matters. Explore feature suggestions from users like you, cast your vote to champion your favorites, and submit your own ideas. Your insights shape our priorities and innovation.

Planned Projects: Get an exclusive look at our quarterly roadmap. Follow the key projects DEMA has planned and see how user feedback, including yours, influences our direction and decisions.

Changelog: Stay informed with our latest advancements by visiting our changelog.

Ad platform metrics, adjust with country consent rate

When looking at conversions and adjusted epRoas (ads) reported from ad platforms in dema we would need to take the consent rate to be able to compare epRoas between countries, same as we do with expected returns by country. To the ad platforms we only send conversions for consented users, and the amount of consented users is very different by country, only 71% in DE and in US there is no consent needed so there we have 100% It could be a fixed config table on country level as a start, and in the future we should probably track consents in the dema tracker. This only applies to metrics marked with (ads) in dema, the normal epRoas does not have this issue as it uses commercetools data, not ad platform.

πŸ’‘ Feature ideas

Almost 2 years ago

Support for Pre-emptive Cost Configuration

Problem: The "Wait-and-Watch" bottleneck Currently, DEMA requires a cost category (e.g., a new shipping method, payment fee etc) to be present in the data stream before it can be configured. This creates an unsustainable "chicken and egg" workflow. Users are forced to manually monitor the platform to catch the exact moment the first transaction with a new cost item occurs. If the configuration isn't updated immediately after that first sale, the data remains inaccurate until manual intervention happens. This "wait-and-watch" approach leads to avoidable data gaps. Proposed Solution: Manual "Key-Value" Entry Implement a way for users to proactively define cost rules using a free-text input field for the Service ID or Cost Key. Manual Entry Point: A UI option to "Add New Cost Rule" where the user can manually type in the expected identifier (e.g., a specific UPS service code or a new provider name). Proactive Mapping: Once the user saves this manual entry with its associated costs, the system should automatically "handshake" with that ID as soon as it eventually appears in the data stream. Flexibility Over Rigidity: Prioritize user-defined inputs over waiting for system-validated logs. Even if there is a minor risk of a typo, the benefit of having the cost ready to fire from order #1 far outweighs the current manual monitoring requirement. Benefit Zero-Day Accuracy: Ensures 100% accurate margins from the very first transaction of a new service. Operational Freedom: Removes the need for staff to "babysit" the system during rollouts or carrier switches. Proactive Scaling: Allows teams to set up entire new markets or logistics flows in DEMA before they go live.

πŸ’‘ Feature ideas

8 days ago

"Other" costs (royalities, fees etc)

We see a need for a more flexible way to input additional order-related costs in the Cost Setup. Specifically, it would be highly valuable to have a customizable field (e.g., 'Other Variable Costs') to account for expenses that impact our margins but aren't strictly COGS or shipping. Examples of use cases: Royalty payments: Fees paid per unit sold. Sales Commissions: External commissions per order. Marketplace Fees: Third-party platform fees By allowing these costs to be defined in Dema, we can achieve a much more accurate 'True Profit' calculation per sales channel. Is this something on your roadmap, or perhaps something that could be solved via a generic cost-mapping feature?"

πŸ’‘ Feature ideas

9 days ago