Frequently asked questions

itrackSCM is a supply-chain and retail-planning application that helps organisations analyse sales, inventory and operational data and make better planning decisions.

Depending on the modules subscribed to, it may support forecasting, requirement planning, merchandise and store classification, allocation, replenishment, inter-store transfers, inventory optimisation and related processes.

itrackSCM is intended for business organisations and authorised members of their teams, including teams in:

• Merchandising;
• Supply planning;
• Demand planning;
• Inventory management;
• Procurement;
• Production;
• Retail operations;
• Warehouse;
• Finance; and
• Management.

No. itrackSCM is primarily a planning and decision-support platform. It may use data exported from an ERP, point-of-sale system, warehouse-management system, e-commerce platform or other business system, but it does not replace the Customer’s ERP, transaction-processing, WMS or accounting systems.

Modules may include:

• Merchandise Classification;
• Demand Planning (Sales Forecasting);
• Requirements Planning;
• Merchandise Intelligence;
• Promotions Intelligence;
• Store Classification;
• Store Allocation;
• Store Replenishment;
• Inter-Store Transfer;
• Sales and Operations Planning.

Availability depends on the Customer’s subscription and implementation status.

Yes, subject to the commercial plan offered by UnoSkills.

Some modules may depend on prerequisite data or another module. These dependencies will be explained in the proposal or implementation plan.

Data requirements vary by module and may include:

• Item Master;
• Store Master;
• Channel Mapping Master;
• Historical Sales Data;
• Store Inventory;
• Warehouse Inventory;
• Open purchase or production orders;
• Lead times;
• Inventory norms;
• Event or promotion calendars;
• Allocation requirements; and
• Customer-defined planning rules.

Templates and field definitions will be provided during implementation.

The recommended history depends on the planning objective and statistical model.

As a general principle:

• Shorter history (less than 12 months) may support basic forecasting or operational planning;
• 12 months may support initial trend analysis;
• 18 to 24 months is preferable for stronger seasonal analysis; and
• Longer, consistent history generally improves model evaluation.

Customer should review the resulting confidence and limitations.

Incorrect or incomplete data may result in incorrect Outputs. itrackSCM may identify common validation issues, but automated validation cannot detect every commercial or operational error. The Customer remains responsible for ensuring that its source data is accurate.

Depending on the module and user permissions, data may be:

• replaced;
• cleared and reloaded;
• corrected in the Customer’s source system and re-uploaded; or
• manually moderated through an approved workflow.

Replacing historical data may affect previously generated results.

The Customer retains ownership of its own Data. UnoSkills receives only the limited rights required to host, process, validate, analyse and provide support the data for providing itrackSCM services.

No forecasting system can guarantee accurate future demand. Forecasts are estimates based on historical data, selected models, business rules and assumptions.

Actual sales may differ because of:

• Competitor activity;
• Pricing changes;
• Supply constraints;
• Economic conditions;
• Stockouts; and
• Other factors not contained in the data.

The Customer should review and moderate forecasts before using them for procurement commitments.

Not unless a specific integration and automated workflow has been expressly agreed.

Under the standard service, itrackSCM generates recommendations or approved output files. The Customer remains responsible for approving and executing orders, allocations, replenishments or transfers in its ERP or operational system.

The Customer’s authorised planner or decision-maker must review the recommendations before implementation. The Customer should verify data, quantities, store constraints, warehouse constraints, supplier capacity, cash-flow impact and other relevant business conditions.

Yes, planners may moderate or override recommendations. The Application may record the system recommendation, planner adjustment and final approved quantity. The Customer remains responsible for reviewing and approving all overrides.

No, itrackSCM is a decision-support system for supply chain and retail planning. Its output must be verified by the Customer team before using it for any reporting purposes.

The Customer should define an internal approval process involving appropriate merchandising, supply-chain, finance, procurement and management personnel. itrackSCM does not replace the Customer’s delegation-of-authority or approval policies.

Outputs are recommendations based on available data and assumptions. Business results may vary. The Customer is responsible for reviewing recommendations before implementation and considering factors not fully captured in the Application.

Any liability will be governed by the applicable contract and limitation-of-liability provisions.

No. Your customer data is not made available to another customer. All customer workspaces are logically separated. Access is restricted according to account, system and user permissions.

UnoSkills retains the ownership of itrackSCM, including its software, algorithms, workflows, templates, Documentation, user interface and generic planning logic.

The Customer retains ownership of its own data, trademarks, policies and Customer-specific documents.

The hosting location and cloud service provider will be communicated in the applicable proposal, security documentation or Order Form.

Where the Customer requires a specific hosting region or data-localisation arrangement, this must be agreed before implementation and may require additional charges.

Reasonable security controls may include:

• Secure user authentication;
• Role-based access;
• Encryption in transit;
• Access restrictions;
• Logging and monitoring;
• Backups;
• Controlled administrative access; and
• Incident-response procedures.

The Customer must also protect its user accounts, employee devices, networks and downloaded reports.

No. Each Authorised User should use a separate login. Sharing credentials reduces accountability and may expose the Customer to security risks. Additional user licences may be requested where required.

Yes, role-based access is available in the subscribed version. The Customer is responsible for deciding which users should have access to uploads, reports, moderation, approvals and administrative functions.

The Customer should promptly request removal or deactivation of the employee’s account and ensure that any Customer devices, files and credentials are recovered.

Integration may be possible through:

• File uploads;
• Secure file exchange;
• APIs;
• Database interfaces; or
• Customised connectors.

Integration scope, frequency, security, development cost and responsibilities must be agreed separately.

Currently only the manual upload option is available. The standard implementation may begin with controlled file uploads. Automated integration may be introduced after data structures, validation rules and business processes are stabilised. It may have additional charges.

Yes, depending on the contracted architecture and configuration. The subscription may include restrictions on the number of legal entities, workspaces, brands, stores, warehouses or users.

The Application may support multiple business verticals and channels where the required data and channel mappings are available. Planning rules may differ by channel and must be configured appropriately.

Certain parameters and business rules may be configured within the standard Application. Material changes to algorithms, workflows or reports may be treated as customisation and may require a separate commercial proposal and mutually agreed timelines for implementation.

Yes. UnoSkills may update the Application for security, legal compliance, improved performance, bug correction and product development. Reasonable efforts will be made not to materially reduce the core functionality of subscribed modules during an active paid term.

Run history and data retention depend on the subscribed plan, storage policy and module configuration. Customers should download important approved reports and maintain copies in their internal systems where required.

UnoSkills will use reasonable efforts to provide advance notice for planned maintenance expected to cause material disruption. Emergency security or stability maintenance may be performed without advance notice.

Standard support typically covers:

• Login and account issues;
• Clarification of templates;
• Assistance with standard workflows;
• Investigation of reproducible application errors;
• Correction of confirmed software defects; and
• Support in Output evaluation to make decisions.

Consulting and customisation may be separately chargeable.

The Customer should provide:

• Company or workspace name;
• Module name;
• Run date or reference;
• Description of the issue;
• Screenshots;
• Relevant error message;
• Sample affected records; and
• Steps required to reproduce the issue.

Issues should be reported to tech@unoskills.com.

Response times depend on the severity of the issue. Any committed response or resolution times will be stated in the Service Level Agreement or Order Form.

No, unless expressly included. UnoSkills may help identify apparent data-quality issues, but correction of the Customer’s ERP, POS, WMS or source records remains the Customer’s responsibility. UnoSkills provides consulting services which can help in correcting the base data.

Access may be suspended after notice if payment remains overdue. Suspension does not cancel unpaid invoices or other contractual obligations.

Cancellation rights depend on the Order Form. Unless otherwise agreed, committed subscription fees are non-refundable even if the Customer stops using the Application before the end of the term.

The Customer should export required reports before expiry. Customer Data may remain available for a limited post-termination period of 90 days, after which it may be deleted or anonymised, subject to legal requirements and backup-retention cycles.

A standard export may be provided where technically available. Custom migration, restructuring, transformation or extraction of historical records may require additional professional-service charges.