Knowledge & Solutions

MPANDO HUB connects contractors, subcontractors, suppliers and real estate teams across project and site management, purchasing, goods receipt and inventory, subcontract work, crews, property sales CRM and operational finance. Available modules and permissions are matched to the company’s agreed setup.

A requirement can progress through requests for quotation, offer comparison, approval and ordering. Delivery, goods receipt, stock movement and allocation are tracked as distinct events. Creating an order or uploading an invoice does not by itself mean that materials have been received or consumed.

The professional trade network supports authorised company and partner workflows. Contractors, subcontractors and suppliers participate through their relevant work, quotation and delivery records. Access is determined by company, project, role and enabled modules.

Teams can work with customers, property inventory, offers, reservations and project presentations within their configured workspace. Shared portfolio access and sales approvals depend on permissions. A visual presentation and an authorised sales transaction remain different actions.

Project teams can follow work packages, attendance and progress-payment information alongside operational financial records and reports. Local payroll, statutory accounting and tax requirements must be assessed for the deployment; they are not assumed to be certified merely because a finance module is available.

Supported drawing and quantity workflows, AI assistance and communication features are scoped during the demonstration. File formats, data access, providers and human approval requirements are clarified. Ask to see the specific workflow your team intends to use rather than assuming every integration is included.

Choose the first workflow, team size and company roles. Demonstrate it with sample data, agree permissions and setup, then define onboarding, training, support and acceptance criteria. Existing members continue to sign in at mpando.tr; this website introduces the product and supports enquiries.

The duration depends on the product, installation or service. Ask for the applicable written terms with your proposal; the covered scope, start date, conditions and claim route should be clear before you order. A single duration is not applied to every product or project.

Demonstrate one complete workflow: a site requirement, supplier quotations, approval, order, partial delivery, goods receipt and the related financial record. Repeat it with contractor, subcontractor and supplier roles. Check what each person can see, who approves exceptions and how corrections are recorded. Agree the required modules before onboarding.

Share sample files with sensitive information removed, the fields you need and the system that owns each record. Import formats, identifiers, duplicates, balances and any integrations are assessed for the agreed scope. Begin with a controlled sample and reconcile the result before transferring a wider dataset.

The proposal depends on company structure, enabled modules, users and partner roles, project volume, data preparation, integrations, training and support. Ask which setup and ongoing costs are included, how changes are charged and what counts as acceptance. A tailored quotation is more useful than a price that hides these assumptions.

Company, project, role and module permissions define the intended access. Demonstrate a supplier quotation, a subcontractor task and a restricted financial view with different accounts. Agree device and connection requirements, data export, hosting, retention and support arrangements during assessment; offline operation and specific certifications are not assumed.

MPANDO HUB is the construction management software and trade network product of MPANDO GLOBAL Inc. It connects contractors, subcontractors, suppliers and property professionals around shared project workflows. MPANDO GLOBAL Inc. is a multi-sector corporate group also providing specialist solutions through MFABER and MTWIN.

Yes. A multi-country project starts with the company and project structure, partner roles, working languages, units, currencies and required reports. These are reviewed during implementation. Product website languages do not, by themselves, confirm every language or local tax feature in the member application. Demonstrate the required setup and agree local accounting interfaces before rollout.

Keep the ordered, delivered, accepted and used quantities separate. For example, if 100 items were ordered and 60 arrived, including 10 damaged items, the team should be able to explain the 40 outstanding items, 50 accepted items and 10 awaiting a decision. Use this scenario in your HUB demonstration and agree who records discrepancies, accepts materials and approves any return.

A new inquiry starts a follow-up process. It does not reserve a unit or record a completed sale. In the configured CRM workflow, review the customer, responsible consultant, unit, offer and approval steps separately. Agree who can change availability, approve a reservation and confirm contract or payment information, so that marketing activity and commercial commitments remain clear.

Retain the original scope and identify the revision, quantities, price effect, schedule effect and approval responsibility. A revised quotation should be assessed before it is treated as an approved order or instruction to proceed. In the demonstration, follow a change through the affected project and purchasing records and confirm which approvals your setup requires.

A requirement can progress through requests for quotation, offer comparison, approval and ordering. Delivery, goods receipt, inventory movement and allocation are tracked as distinct events. Creating an order or uploading an invoice does not by itself mean that materials have been received or consumed.

Site tracking may focus on field activities; construction ERP requirements can extend to purchasing, inventory, teams and financial records. Review the required records, approvals, company/project access and requested accounting connections in a HUB demonstration.

Trace a site requirement through a request for quotation, supplier comparison, purchase order and partial goods receipt. Then review a subcontract work package and a customer/property example in sales CRM. Identify the responsible role, approval and reporting need for each record.

Define the task, permitted data, users, provider and expected output. Use examples that allow the team to check the answer against its source. Agree how uncertain or incomplete information is handled and which actions require human approval. The proposed workflow should be demonstrated for the enabled modules, not inferred from a general AI label.

A suggested answer or draft is separate from an external message, purchase approval or financial action. Confirm who reviews the content and authorizes each consequential step. Communication channels, provider permissions and delivery evidence are part of the agreed integration scope. Ask to see the approval and correction process in the demonstration.

Provide a supported file, drawing revision, scale, units, layer information and the measurement rules relevant to the work. Include a known dimension for checking the import. Identify exclusions, openings and any assumptions that affect quantities. File compatibility and the required review workflow are confirmed in the demonstration.

A drawing-derived quantity needs review against the design version, measurement method, openings, waste allowance and selected material specification. Confirm who approves the quantity and any recipe or bill-of-materials assumptions. Importing a file is a starting point for controlled review, not proof that every resulting quantity is approved for ordering.

Relate the financial question to the underlying project, work package, purchase, receipt or sales event. Review the document, amount, currency, period and approval state together. Operational reports are most useful when teams can distinguish a planned commitment, a received item, a posted record and a completed payment.

Begin by defining the authoritative system, required fields, identifiers, currencies, periods and reconciliation rules. Assess the proposed export or integration during scoping and test a sample before wider use. Statutory reporting, payroll and local tax compliance require their own confirmed solution and are not implied by operational financial reporting.

Compare the same specification, quantity and unit, then review delivery, freight, taxes, payment terms, validity and proposed alternatives. Keep exclusions visible. The lowest unit price may describe a different delivered scope. Use a sample request with two offers in the HUB demo and agree who can approve a supplier or a changed condition.

A historical price provides context; it is not a current quotation. Check the date, currency, quantity, specification and delivery terms before using it for a new decision. Ask the supplier to confirm the current offer and follow the approval step before creating a purchase commitment.

A directory primarily lists businesses. HUB's trade-network approach relates authorized participants to a specific requirement, quotation, work package or delivery process. The useful starting point is the task and the responsible companies. Confirm the participation, approval and visibility rules for the network your company will use.

Access must be defined for each company, project, role and record type. Demonstrate separate contractor, subcontractor and supplier accounts, including a record each must not see. Agree who invites participants and approves access changes. Participation in the same project does not mean every participant should see all commercial information.

Connect the person or crew, date, project, work package, recorded time and approving supervisor. Clarify corrections, exceptions and the period being reviewed. Demonstrate a missing entry and a corrected entry before agreeing the operational workflow; a recorded hour does not by itself prove accepted work or a payroll payment.

Attendance explains the recorded time; progress describes the work achieved. Review them against the same work package while preserving their different units and approval rules. Agree the evidence used by site supervision and commercial teams. Payroll calculations and employment obligations are assessed separately for the country and setup.

No. An invoice describes a commercial document; goods receipt records the physical acceptance of materials. Relate the order, delivery information, counted quantity and any damage or shortage. Keep the person accepting the delivery distinct from the person reviewing the financial document when your process requires separate approvals.

Stock describes materials held at a location. Allocation or issue assigns them to a team or purpose. Consumption records their use. Demonstrate a movement from receipt to storage, issue, use and any return. Agree the unit, location and evidence needed for each step so an issue is not automatically reported as completed work.

Use a stable project and unit identifier, an agreed source for availability and the fields approved for presentation. Define how the visual model maps to the business record, how updates arrive and who resolves a mismatch. The connection is scoped and tested separately from producing the 3D model.

Agree how the presentation signals the age or absence of data and where the salesperson confirms current availability. Test a changed unit, a restricted price and an unavailable connection. Do not treat a viewable unit as a confirmed reservation. The commercial transaction remains subject to the relevant permissions and approvals.

Use the project and work package, date, responsible team, progress description, related drawing revision and supporting evidence. Distinguish completed work from an estimate or an item awaiting approval. A useful demonstration follows one field update through technical review and shows how the team returns to the supporting record.

Start with a consistent project, block and work breakdown structure. Assign the people responsible for each scope and decide which management views must combine information across sites. Review an overdue item and a revised drawing in a sample project, then agree the permissions and reports required for your rollout.

Confirm the inquiry source, customer details, responsible adviser, project interest, next action and timing. Connect meetings, notes and offers to the same customer context while preserving access rules. The demonstration should show how an unassigned inquiry becomes an accountable follow-up, not merely how a contact is stored.

Use a stable unit identifier and clear availability states. Agree who may issue an offer, approve a reservation, release a unit and confirm a sale. Review expired or withdrawn offers and changes to price or payment assumptions. A draft document, a signed contract and a recorded payment need distinct evidence and responsibilities.

Define who owns each listing or unit record, which colleagues or partners may view it and who approves changes. Connect customer requirements and follow-up to the relevant property context. In the demo, review the same property from two roles and confirm the approved scope for sharing, offers and client information.

The required workspace should distinguish general listings from a developer's controlled unit inventory. Confirm the identifiers, availability source, adviser assignment and approval steps for each use case. Discuss how the agency receives updates and hands a qualified inquiry to the responsible project team; public listing access is not authority to reserve a unit.

List companies, projects, roles, record types and sensitive commercial fields. Demonstrate allowed and denied actions with separate contractor, subcontractor and supplier accounts. Agree who grants, reviews and revokes access, and how changes in project responsibility are handled. A role name alone is not proof of correct access.

Specify support contact, working language, operating hours where agreed, incident reporting, export requirements, retention and responsibilities at termination. Clarify hosting and backup arrangements and the evidence available for them. Response times, recovery commitments and specific certifications should appear in the agreed terms when required.

Define location, drawings and revision, quantities, measurement method, included materials, labour responsibilities, access, programme and acceptance evidence. Identify interfaces with other trades and who approves changes. A clear scope makes quotations comparable and provides a better basis for reviewing progress and commercial entitlement.

No. Quotation acceptance, work completion, progress assessment, financial approval and payment are separate events. Use a demonstration covering partial progress and a disputed quantity. Agree who verifies the work, which documents support the assessment and which financial steps require their own approval.