Merchandising Campaign Management Software Indonesia

It covers a campaign from set-up to results. You create the campaign with its dates, attach the stores and POSM items it applies to, and then follow coverage and scores on the Campaign Dashboard.

The campaign form takes a name, start and end dates, an optional campaign code, and two uploaded files, one of store codes and one of POSM codes. Codes the system cannot match are listed back on the form. You can also tick Send Notification, and stores or POSM items can be removed later through another file upload.

Yes, in the Campaign Management module the owner creates the campaign personally. That removes the need to email a request and an Excel template to a helpdesk and wait for a supervisor to configure it by hand. The module works from purchase order data that comes from your own ERP, so it is set up per customer once that integration is in place.

A planned campaign comes out of your marketing plan: you pick the plan line it belongs to, it carries that line's objective, and its planned months, outlet counts and contribution shares are recorded with it. An ad hoc campaign sits outside the plan and suits new launches, gaps in the market or unplanned schemes. Both are created in the same wizard and feed the same field tracking once they are live.

Summary tiles at the top show campaign totals and coverage. A monthly table lists campaigns, total outlets, covered outlets, visits done and coverage percentage, and a second table breaks the figures down by campaign, with planned, unplanned and total visits. The options panel adds filters and downloadable reports.

Scoring parameters are defined for each campaign, and every parameter has a weight, a reference image of success and a written guideline of up to 500 characters. Where audits are enabled, a reviewer compares the photo a field user submitted with the guideline and records a percentage score and a comment. When two campaigns run at one outlet, each is scored separately.

The campaign form has a Send Notification option, and the campaign list shows how it was set for each campaign. In the Campaign Management module, the person who owns an approved purchase order is also notified that it is ready to be turned into a campaign. Field users then find the campaign in the mobile app, listed with its days remaining, its date range and the POSM types it needs.

A campaign covers whichever store codes you upload, so one campaign can span outlets across Java and the other islands, while field teams work from the mobile app. Each customer gets a separate instance with its own brands, outlet lists and enabled modules, and custom modules can be built where the standard flow does not fit. Pricing depends on user count, modules and customisation scope, so a short demo is the easiest way to size it.