Product and implementation guide
Define what is being tracked
The Inventory application is the business-facing ArcApps inventory offering. The public Mart storefront is a separate sample demonstration, not a live stock or payment service. Confirm your operational scope, including item records, locations, purchasing or sales-related requirements, directly with the team. Do not treat sample prices or products as an offer or confirmed availability.
Example: a pack and a single unit
A business receives notebooks in packs and sells individual books. Choose the base unit and document any conversion before importing quantities. Six packs of ten plus four loose notebooks represent sixty-four individual units, not six. Identify the person authorized to maintain units and item codes so staff do not create duplicates during ordinary work.
Prepare and reconcile opening balances
Set a count date and explain how movements during counting are recorded. Review unusual differences and preserve approval evidence. Valuation and accounting treatment require your qualified financial adviser; an implementation template does not determine those rules. Test imports in a separate environment and confirm whether repeating an import replaces or adds quantities.
Operate with controlled corrections
Rehearse a receipt, issue and approved adjustment through the supported workflow. Confirm references, audit visibility and access rights. Agree how an unknown item or discrepancy reaches the responsible owner. Read the opening balance guide before migration, and use the Mart demo only for its clearly labeled sample browsing and enquiry journey.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support