1. Nature of Delivery

Forrentech delivers services rather than physical goods. Therefore, the term “shipping” refers mainly to the electronic delivery of digital services, project files, reports, source code, software, documentation, or access to completed work.

2. Services Covered

This policy applies to Forrentech’s services, including but not limited to:

• Custom software development
• Website development
• Mobile application development
• SaaS development
• AI and automation solutions
• Technical consulting
• Architecture and security audits
• UI/UX design
• Maintenance and support
• Deployment and DevOps services
• Dedicated development resources
• Technical documentation
• Digital reports and project files

3. Delivery Methods

Depending on the nature of the service, Forrentech may deliver work through:

• Email
• GitHub, GitLab, Bitbucket, or other code repositories
• Cloud hosting platforms
• Client servers
• Project management tools
• Shared drives
• Video calls or screen-sharing sessions
• PDF reports or documentation
• Live website, application, dashboard, or software deployment
• Other mutually agreed digital channels
• The exact delivery method will depend on the project requirements and will be agreed with the client.

4. Delivery Timeline

Estimated delivery timelines will be mentioned in the proposal, quotation, invoice, contract, email, or written communication.

Delivery timelines may vary depending on:

• Project scope and complexity
• Client responsiveness
• Timely feedback and approvals
• Availability of required content, data, credentials, and access
• Change requests
• Third-party service delays
• Technical dependencies
• Testing and quality assurance requirements
• Unexpected technical issues
• Forrentech will make reasonable efforts to meet agreed timelines and communicate any major delays where applicable.

5. Client Responsibilities

To ensure smooth and timely delivery, the client is responsible for providing:

• Complete project requirements
• Timely feedback and approvals
• Required branding, content, data, and assets
• Access to hosting, domains, APIs, servers, repositories, or third-party tools where needed
• Accurate business and technical information
• A clear point of contact
• Any required legal, compliance, or business approvals
• Delays caused by missing information, unclear requirements, delayed approvals, or lack of access may extend the project timeline.

6. Acceptance of Deliverables

A deliverable will be considered accepted when:

• The client confirms approval in writing.
• The deliverable is deployed, shared, or handed over.
• The client starts using the deliverable.
• The client does not report any major issue within the agreed review period.
• The deliverable meets the agreed scope and specifications.
• Minor bugs, adjustments, or revisions do not invalidate delivery if the core agreed work has been completed.

7. Revisions and Change Requests

Revisions are provided according to the agreed project scope.

Any changes, additions, modifications, redesigns, new features, or extra work outside the agreed scope may require additional time and cost.

Forrentech will communicate additional charges before starting out-of-scope work.

8. Physical Shipping

Forrentech does not normally ship physical goods.

If physical items, documents, merchandise, hardware, or printed materials are ever shipped as part of a specific arrangement, shipping charges, courier timelines, delivery responsibility, customs duties, taxes, and risk of loss will be agreed separately in writing.

9. Support After Delivery

Post-delivery support, bug fixing, maintenance, or warranty periods may be provided if agreed in writing.

Support does not include:

• New features
• Major changes
• Third-party service issues
• Hosting or server problems outside Forrentech’s control
• Issues caused by unauthorized changes
• Client-side misuse
• Content changes
• Business logic changes not included in the original scope
• Additional support may be provided under a separate maintenance plan or service agreement.

10. Delivery Confirmation

Forrentech may confirm delivery through email, project management updates, repository commits, deployment links, shared documents, or written communication.

Once delivery is confirmed, the client is responsible for reviewing the work and reporting any issues within the agreed review period.