Service Scope & Customer Approval
Clear project information helps customers and the SellForge service team understand what is being purchased and how the work will be delivered. This page describes the documentation and review process for custom ecommerce services.
What your service scope should identify
Every custom service order should have a written, project-specific scope associated with its order number. Before purchasing or authorizing work, review the following information with your service team:
- Service name and description of the work.
- Included deliverables and their expected format.
- Number and type of revisions, where applicable.
- Estimated timeframe, milestones and dependencies.
- Customer responsibilities, including information and approvals.
- Required access and minimum necessary permissions.
- Work, features, expenses or ongoing support that are excluded.
- Observable completion criteria for the agreed deliverables.
- The process for requesting and approving additional work.
Service invoices and project references
A SellForge Service Invoice pays for work to be completed after payment. The invoice title alone is not a detailed project description. Confirm the service description and written scope associated with your purchase. Order and invoice information should identify the relevant project or scope reference so both sides can refer to the same work.
Review and confirmation before work starts
Check that the scope accurately describes your requested service, included items and exclusions. Ask for clarification if anything is missing or unclear. Confirm the agreed scope through the documented communication channel used for your project before work begins. Keep a copy of the scope and your confirmation. A payment record alone should not be used as a substitute for a clear scope record.
Customer information and access
Review which materials, permissions, technical information and decisions are required from you. Provide accurate information and notify your service contact of relevant changes. Use an appropriate secure access method and grant only the permissions needed for the agreed work. Do not send passwords, security codes or full payment-card details by email or chat.
Estimated timeframe and dependencies
The project scope should identify the estimated timeframe and any prerequisites, such as receipt of required information, access, customer decisions or third-party availability. Confirm whether the estimate begins at payment, receipt of prerequisites or another agreed milestone. If a dependency or proposed change affects timing, discuss and document the revised estimate with your service team. This page does not set a universal delivery deadline.
Assigned service contact
Some services may be fulfilled directly through SellForge, while certain projects may be handled by ecommerce specialists, strategists, developers or service professionals working through the organization. Where applicable, confirm your assigned service contact and communication channel. Purchases and service invoice documentation identify SellForge or the applicable service name rather than an individual specialist's personal name.
Changes and additional work
Requests outside the original scope may require a separate quote or additional payment. Before additional work proceeds, review the proposed deliverables, exclusions, price and effect on timing. Document your explicit confirmation of the proposed changes and retain the original and revised scope versions. A request for a change should not be treated as approval of an unspecified additional charge.
Revisions
Where revisions are included, the scope should explain how many are included, what they cover and how to submit feedback. If revisions are not specified, ask your service team before purchase. New features or work beyond the agreed deliverables should be discussed through the scope-change process rather than assumed to be included.
Completion criteria and customer review
The scope should define how the agreed deliverables will be checked. At delivery, review the completion summary and delivered items against those criteria. Confirm receipt and identify any missing, inaccessible or incorrect items with specific details. Payment, a sent completion message or customer silence alone does not establish customer acknowledgment. Keep completion records and actual customer responses separate.
Questions or scope concerns
If you believe work does not match the agreed scope, contact your assigned service team or email sellforge339@gmail.com with your order number, scope reference and a description of the concern. Include relevant non-sensitive screenshots or examples. Contacting SellForge first, where possible, provides an opportunity to investigate and resolve the issue directly.
Related purchase information
Review the specific product or service description, delivery information and applicable Terms of Service, Refund Policy and Privacy Policy alongside your written scope. This page explains project documentation and does not replace those policies or establish new refund, cancellation or payment-dispute restrictions.