New Help area prototype released

• Navigate to 'Help' and click 'Overview' to open the new help area. Browse through the 'Help' via the content tree on the left.
• The new help already contains an extensive documentation of the structure and components of the minubo data model and some of the tools of the Commerce Intelligence Suite.
• "How is this measure calculated?"
  --> There are detail pages for over 500 measures and 170 attributes including formulas, time references and measure modifiers.
• "Can I use these attributes and measures together?
  --> Through the completely new documentation of the minubo data levels, you gain complete transparency over the relationship of attributes and measures.
• Let us know which topics we should cover next!

In calendar week 35 we will change the calculation of Contribution Margin II Rate and Contribution Margin III Rate!

Historically, these rates were defined as percent of the previous Contribution Margin Value. We adapt the calculation to be in line with common practice in the market and with the Commerce Reporting Standard. Hence, Contribution Margin Rates will now be based on Net Revenue. The calculations change to:

• "Contribution Margin II Rate" = "Contribution Margin II" / "Net Revenue"
• "Contribution Margin III Rate" = "Contribution Margin III" / "Net Revenue"

If the current calculation is still desired in your particular use case, please contact your Key Account Manager to request the addition. In any way, we are always keen on your feedback, so let us know what you think!

More average measures:

• Avg. Net Revenue per Item
• Avg. Net Revenue per Customer
• Avg. Contribution Margin I (OD)
• Avg. Contribution Margin I (ID,RD)
• Avg. Contribution Margin I per Item (OD)
• Avg. Contribution Margin I per Item (ID,RD)
• Avg. Contribution Margin I per Customer (OD)
• Avg. Contribution Margin II
• Avg. Contribution Margin II per Item
• Avg. Contribution Margin II per Customer
• Avg. Contribution Margin III
• Avg. Contribution Margin III per Item
• Avg. Contribution Margin III per Customer

New: Cost of Goods in Orders

Cost of Goods in Orders can now be delivered via several interfaces (e.g. Generic).

GDPR

We will soon publish a more detailed post regarding product-sided changes due to GDPR. For now, we just like to inform that we added an opt-in to the App to collect your agreement for tracking user behavior within the App.

Salesforce Commercecloud Cartridge

• Added setting to reload all customer profiles every x Days to ensure GDPR compliance.
• Added setting to load products from multiple catalogs for organizations with multiple relevant catalogs.
• Added feature to load prices only from specified price books to shorten load times.

Magento Interface

• Added shipping date
• Added customer first and last name
• Reads default product categories for product categories in minubo

New Data Model

We are busy to upgrade our current Dashboard features. As preparation we adjusted the old metric names from dashboards to the new measure names of the minubo data model. Due to this change you will see that widget presets and titles of existing widgets may have changed. We will also add a tool tip shortly to improve readability and allow for comparison of old and new measure name. We currently plan to release the new Dashboards in Q3 2018. With this upgrade all measures of the new minubo data model will be available in Dashboards as well.

minubo welcomes Spryker

We finished important steps for a Spryker integration. The new interface is a direct connection to the well-known commerce OS based on a live event stream.

minubo becomes real time

We made big steps towards real time processing of the event stream data in the Newstore environment! With real time, we cut the time from data collection to data analysis and thereby allow users to react in a more timely manner.

Generic interface improvements

The Generic Transaction Costs and Loyalty Points tables now allow data updates via Update Date. This reduces the necessary effort to update data by incremental data delivery.

Good to know

Predefined time periods now include "All time to yesterday" and "All time and next year". These time periods simplify analysis over large time frames with self-adjusting end of time period.

Improvements to the Data Model

• Offline Touchpoints: Marketing Costs can now be mapped to offline touchpoints. This is important for all customers who deliver offline touchpoints and want to analyze the ROI of their offline activities. Marketing costs for touchpoints can be delivered via the marketing cost interface and be mapped to orders or touchpoints through various marketing measures.
• Google Analytics Currency Conversion: Marketing Costs from Google Analytics profiles in a foreign currency other than the configurated minubo target currency can now be automatically converted into minubo target currency.

Improvements to the User Management

• User Re-activation: We finalized the login customer status management so that user administrators on the customer side can safely activate and re-activate users via the user management system within the settings area in the app.

We finally release Custom Heartbeats.

In the Heartbeats section you know find the "Configuration" area where you can crate new custom defined heartbeat alerts via "Create New Config":

For data-driven organizations, monitoring relevant business metrics and processes plays a crucial role. However, it takes a lot of time to design and implement an automated alerting system.

With the further development of the Heartbeat feature, known as the new Heartbeat Configurator, it is now possible to define your own alerts and align them to individual use cases – tailored to your own personal work routine: You define exactly which aspect of your business you want to monitor, with which key figure, over which period of time, and once the conditions for the alarm have been met, you are proactively informed by the Heartbeat.

Set up your new custom heartbeat now: https://app.minubo.com/analytics/area.page#/insightstream/configs/configs/new

In case you have questions you find help here: https://docs.google.com/a/trewys.de/document/d/1nxFH2oQ3rB51MvtfuYRPHxiXQr18gMmGhOLHfQkCMgY/edit?usp=sharing

Further questions? Contact us at support@minubo.com

New measures

• "Order Profit" is the expected profit from an order before invoicing. When the time between order and invoice is large, this measure supports profit forecasting!
• "Original Merchandise Value (SKU Level) (excl TAX)" is the original merchandise value excluding tax of each SKU. This measure is particularly relevant for US customers as list prices are typically specified without tax.
• We continue out phasing the old measure model by deactivating old feeds / web pivots to force migration to the new measure model.

More Data

• Stores / POS: Stores have been added to the sales channel hierarchy. Each store can be specified by name, with two generic store attributes and an owner.
• Transaction Costs: Fulfillment and payment costs can now be delivered via the generic interface for each invoice position.
• Amazon FBA / FBM costs: The Amazon FBA FBM cost interface now includes additional fees of type Refund and Chargeback for complete cost overview.

Tech update

• We moved the minubo app to Elastic Search 6 to increase load performance for our users and save time in the daily processing jobs.

We are close to releasing a new feature:

Custom heartbeats allow you to monitor your favorite Key Performance Indicators and to get alarms whenever your alert condition is met.

For example, monitor the return rate of top-performing products and get notified when something really needs your attention!

Contact your Key Account Manager to be the first to use custom heartbeats!

We are still busy migrating to new measure names, further implementing our rights & roles permission system and improving our Store Monitor App.

Interface Improvements

• The generic interface now support to deliver original merchandise value per item on the sales order position. This is a crucial steps towards easier integration of multiple price lists.
• Generic enrichment now has an option to overwrite all values of a target field with empty before enriching. Before, enriching only some values of a field would lead to a mixture of old and new values.
• The ETL process now handles multiple cost interfaces now which allows you to integrate costs from as many sources as you like.