The details behind the decision.

MudaGen is designed for planners, procurement and buying teams, inventory managers and warehouse leaders who need a clearer view of material availability and the next action to take. Manufacturing and distribution are the initial focus. We assess your material mix, plants, data and workflows during discovery.

MudaGen works alongside your ERP. The ERP remains the system of record for materials and transactions. MudaGen brings stock, demand, receipt timing and supplier behavior into a decision workflow, then can submit authorized actions through an ERP connection configured for your company.

Explore Inventory overview, material-specific actions, supplier timing, inventory-policy scenarios and decision tracking with fictional materials and plants. Public chat is available without ChatGPT sign-in, subject to limits. Deeper inventory AI reviews use limited reviewer invitations. The ERP automation page simulates purchasing and stock-transfer workflows; it does not connect to a customer ERP.

Yes. The inventory workflow presents policy proposals based on the available demand and supplier timing evidence. Review those assumptions alongside coverage, variability and your operating constraints. A proposed policy change is distinct from an urgent early-delivery request and is approved before becoming a customer’s operating baseline.

Compare planned lead time with observed order-to-receipt history. Repeated delays may support more protection or a longer planning assumption; consistently earlier receipts may support a shorter one. Review the spread and quality of the history, not only the average. Supplier behavior informs a proposal rather than guaranteeing a future date.

Yes. The sample workflow includes production, accessory shipments, kitting, interplant transfers, service, maintenance and direct fulfillment. Keep those uses tied to the material and plant, and avoid counting the same transfer or kit event twice. Detailed reservations and priorities follow the data and business rules agreed for your deployment.

An immediate timing shortage and a new-order proposal answer different questions. Existing supply may be sufficient in total but arrive too late. The right near-term action could be an earlier partial receipt or a feasible transfer, rather than adding another purchase order. Review the material-specific quantity and date in the action.

The current inventory experience uses the supplied demand history and planning assumptions to evaluate availability and policy scenarios. Forecasting requirements, seasonality, promotions, intermittent demand and forecast validation need to be scoped explicitly for a customer project. The current demo should not be treated as a validated forecasting service.

Those are planned expansion areas for the MudaGen platform. The current starting point is inventory intelligence and material decisions. We agree future-module availability and commitments separately; there is no public release-date promise for capacity analysis or production scheduling.

Multi-plant inventory context is part of the product workflow. A customer rollout defines the sites, legal entities, material identifiers, units and access boundaries. Start with a focused scope if useful, then expand once the data reconciliation and operating process are proven.

We first assess your ERP product and version, available interfaces and security requirements. A pilot can start with approved Excel or CSV exports. A connected deployment can use scheduled exchanges, approved APIs or your integration middleware. Mapping, refresh behavior, access, testing and writeback are agreed before production use.

Yes. Bring your ERP product, version and intended workflows to discovery. We assess the relevant data and transaction interfaces with your IT team. These are assessment paths, not a claim that MudaGen already has a certified or pre-built connector for every version. Compatibility and effort are confirmed against your environment.

Typically: material master, plant and storage-location identifiers, base units, usable stock, demand history or dated requirements, open purchasing documents, expected and actual receipts, and supplier lead times. Cost and stock-policy fields support additional analysis. We agree the minimum useful data set for the pilot instead of requesting everything by default.

No single column order is required. The import workflow supports structured Excel and CSV files, SAP-style names and reviewed column mapping. AI-assisted interpretation can help with unfamiliar headings when explicitly requested. The user still validates dates, units, identifiers and required fields before the analysis is trusted.

The refresh schedule depends on the agreed source interface and business cadence. An export-based pilot is a snapshot. A direct or scheduled integration can refresh at the frequency supported and approved by your ERP team. We specify data freshness, failure alerts and reconciliation rather than calling every integration real time.

Yes, a warehouse or integration-layer feed can be included in discovery. We agree which system owns inventory availability, warehouse tasks and receipts. MudaGen can coordinate authorized ERP actions while physical picking, transport and receiving continue through the facility’s approved execution process.

As an initial scoping guide, a focused read-only pilot may be planned for 2–4 weeks after usable data and access are available. A connected rollout can be scoped in a 6–12+ week planning window; custom interfaces and multi-site controls can take longer. These are proposed planning ranges, not guaranteed delivery times. Discovery produces your actual milestones and responsibilities.

Yes. Define a plant, material group, user team and recurring decision problem. Agree the data, success measures and acceptance process. A focused pilot helps validate both the recommendations and the practical fit before extending the scope or enabling ERP execution. Pilot fees and terms are included in your proposal.

The workflow identifies affected records and the specific checks needed. Missing values should not silently become zero. Before production, we reconcile totals with the source system, validate sample materials and agree who resolves issues. A record needing verification remains visible rather than becoming an unsupported recommendation.

We scope onboarding around the users and workflows in your project, including data review, action ownership, AI use and approval handling. Training, launch support, ongoing support hours and response commitments are set in the proposal. We do not assume a 24/7 service or a particular SLA unless it is explicitly agreed.

Yes, in an ERP-connected deployment. Configure MudaGen to submit authorized orders, transfer documents or planning updates after the required approval, or within pre-approved company policies. Exact document support, permissions and exception handling are tested with your ERP team. The public demo simulates these transactions.

Yes. Approval-led execution is a service option. Your process defines who can authorize a transaction and under which limits. You can keep some workflows advisory, require approval for others and permit policy-led automation for routine cases. These controls are configured and validated for the customer deployment.

Failure handling is part of integration design: validate before submission, avoid duplicate documents, capture references and reconcile the ERP result. An uncertain result should be checked before retrying. We test the agreed failure and escalation paths in a non-production environment before enabling execution.

A connected deployment can initiate an authorized stock-transfer document and coordinate the system workflow. Physical movement still requires the warehouse or logistics process: picking, handling, transport and receipt. The public demo illustrates the document and approval steps without moving real stock.

The inventory logic produces data-based guidance such as coverage, timing gaps and proposed quantities. Generative AI explains the situation, compares eligible alternatives and helps a user explore the decision in conversation. It should preserve the evidence rather than invent a new stock balance or unsupported date.

A recorded rejection reason can provide relevant context for a later review. In the public demo, that feedback is bounded, inspectable and stored in the browser; it is not autonomous model retraining. Shared company memory, permissions, expiry and evaluation are a separately scoped part of a production implementation.

Public website and demo chat do not require a ChatGPT account. Users can type or choose Voice, allow microphone access, stop recording and review the transcript before sending. Spoken replies use the browser’s speech service. Chat and voice use MudaGen’s API connection and are subject to request limits.

The public product keeps deeper AI recommendation generation manual. Dashboard navigation and spreadsheet upload do not trigger background recommendation batches. Text and voice chat are explicit actions with separate limits. For a company deployment, agree generation policies, volume assumptions and usage costs in the commercial scope.

Contact us for a tailored quote. There is no published standard rate yet. Pricing depends on the company’s scope, material and plant footprint, user needs, integration work, automation level and support. We separate the agreed subscription, implementation and AI usage assumptions in the proposal.

Our goal is to make AI inventory management accessible to more businesses. Start with a focused use case, avoid unnecessary scope and make the recurring and implementation costs clear. We aim to compete on practical value and affordability; we do not claim a verified lowest price across every competitor.

The public sample demo is free to explore. A pilot using your data, implementation services, subscription terms and any minimum commitment are agreed in a customer proposal. No standard production trial period or public contract term has been announced.

Production security is agreed with your IT team before connecting company data. Review user and company boundaries, service permissions, hosting region, retention, provider handling, audit needs and recovery expectations. The public demo uses fictional inventory and is not the place to upload confidential business records.

MudaGen does not currently claim SOC 2 or ISO 27001 certification. SSO, regional hosting, security assurance and other enterprise requirements must be reviewed and confirmed for the proposed customer deployment. We make contractual commitments only when the corresponding controls and service scope are agreed.

A sent chat question includes its text and bounded recent conversation. Voice audio is sent for transcription after Stop. Public inventory answers use supplied sample records. Deeper recommendation requests use selected sample context. The website’s contact form is not sent to AI. Customer data handling and AI provider configuration are agreed separately before a company rollout.

Data ownership, permitted processing, export, retention and deletion are agreed in the customer contract and data-handling scope. Your ERP remains the system of record. Before onboarding, define the records held by MudaGen and the exit process. For website contact data, use the contact form to request access or deletion.

MudaGen focuses on the operational path from material-specific evidence to a clear next action and follow-through. The approach combines inventory logic, on-demand generative AI, decision feedback and customer-configured ERP execution. Evaluate that fit against your own use cases, integration effort and total cost rather than assuming every platform has the same scope.

The interactive inventory product and company website are available to explore today. The demo includes material actions, supplier timing, policy scenarios, decision tracking and live text and voice AI. ERP-connected customer deployments require implementation. Capacity analysis and production planning are planned expansion areas. We do not present the demo as proof of completed enterprise rollouts.

Agree a baseline and a pilot scorecard: shortage exposure, exception age, planner and buyer time, expedite cost, excess inventory and accepted actions with verified outcomes. Separate released working capital from recurring expense savings. Customer-specific results need validation; MudaGen does not publish an unverified savings promise.

Yes. Choose the relevant topic on the contact page and tell us what you would like to discuss. We can arrange a product, business or integration conversation. Funding, traction, customer references and commercial projections are discussed directly when available rather than inferred from the public demo.