Fulfillment Policy
Last updated: March 29, 2026
This Fulfillment Policy explains how JD Webcraft Web Development Services (“JD Webcraft,” “we,” “us,” “our”) delivers services and digital products, including timelines, payments, revisions, cancellations, refunds, and migration/transfer requests. This policy is designed to support payment processor requirements and sets expectations for delivery.
Fulfillment Support Email: hello@jdwebcraft.com
Business Location: Davao City, Philippines 8000
1. What we fulfill
A. Services (primary)
We provide web-related services which may include (depending on your proposal): web design, WordPress development, e-commerce builds, maintenance/retainers, SEO add-ons, and hosting/domain support where included.
B. Digital products (if offered)
We may offer downloadable digital products (e.g., templates, guides, resources). Delivery terms are in Section 12.
2. How an order is placed (services)
A service order is confirmed only when both are completed:
- You sign the contract / service agreement (or formally accept our proposal), and
- You pay the required initial invoice/first payment.
No project slot is reserved until the initial payment clears.
3. Payment terms (services)
Unless your proposal states otherwise, our standard payment structure is:
- 40% initial payment (to start work and reserve capacity)
- 30% before first revision phase (typically after initial build/draft delivery)
- 30% after the website is launched (final payment due upon go-live)
Accepted currencies
USD and PHP
Accepted payment methods
Third-party payment methods such as Wise, PayPal, Payoneer, GCash, Maya, and local bank transfer. We do not collect payment card details directly on our site.
Late fees and payment delays (updated)
- If a payment phase remains unpaid after 5 business days from the due date, a 2% late fee may be applied to the overdue installment for that payment phase (to the extent permitted by applicable law).
- If payment is not received after 5 business days, we may pause work and/or withhold deliverables until the account is brought current. Any pause will extend the delivery timeline accordingly.
4. Project start date and delivery timelines
A. When the timeline starts
Your timeline begins on the Project Start Date, which is the date when we have received all of the following:
- Signed agreement/acceptance
- Cleared initial payment (40%)
- Required onboarding essentials (minimum: project goals + page list + brand assets and/or content plan)
B. Typical delivery windows (estimates)
These are typical ranges; final timelines depend on scope, content readiness, and responsiveness.
- Simple site (1–3 pages): 1–2 weeks
- Standard business site (5–15 pages): 2–4 weeks
- E-commerce website: 2–4 weeks
C. No “rush delivery”
We do not offer a “rush delivery” guarantee. We may finish earlier when possible, but we prioritize quality and stability.
5. Client delay policy (timeline pauses)
If required client inputs (content, approvals, access, feedback) are not provided within 10 business days, the project timeline may be paused until we receive what’s needed. Restarting may affect your place in the production queue.
7. Revisions vs. new scope (scope changes)
To prevent confusion and delays, we separate revisions (fine-tuning within agreed scope) from change requests/new scope (adds/modifies baseline deliverables). In general: revisions refine what was agreed; scope changes add or alter what was agreed.
A. What usually counts as a “revision” (within scope)
Examples (as long as it stays within the approved layout/plan):
- Text edits, swapping images/icons, minor spacing adjustments
- Small UI tweaks (button style, font sizing, alignment)
- Reordering existing sections on a page
- Minor color refinements within brand palette
- Replacing provided content with updated content (same structure)
- Fixing bugs or inconsistencies vs. approved design
B. What usually counts as “new scope / change request”
Examples:
- Adding new pages not in the agreed page list
- Adding new major sections after a page/layout is approved
- New features/integrations (booking system, membership, multilingual, advanced filters, custom dashboards, automation, CRM, etc.)
- Major redesign after approval (new layout direction, new UX structure)
- Significant content rework or rewriting not included in scope
- Extra rounds of revisions beyond what your proposal includes (if applicable)
Scope changes typically require a written change approval and may impact fees and timeline.
Revision rounds: The number of included revision rounds is defined in your proposal/contract. If not specified, we will confirm the revision allowance in writing before build begins.
8. Delivery, launch, handover, and acceptance
A. What counts as “fulfillment/delivery” for services
Depending on your plan and scope, fulfillment may include:
- A staging site (preview link) ready for review
- Site launched live on your domain/hosting
- Admin credentials handed over (or access granted)
- Basic walkthrough/training session (if included)
B. Acceptance window
After we submit a deliverable for review, you agree to review and respond within a reasonable timeframe. If we do not receive feedback within the agreed review window (or a reasonable time), the deliverable may be treated as accepted so the project can progress.
C. Post-launch support
We provide post-launch support for up to 90 days, depending on the plan/package. Support scope (bug fixes vs improvements) follows your agreement.
D. Backups
Backups are included, but frequency depends on project scope and hosting environment. If you require a specific backup schedule, it must be stated in your plan.
9. Cancellations and refunds (services)
A. Non-refundable initial payment (with legal exceptions)
The initial payment is generally non-refundable because it reserves capacity and covers onboarding/initial work. However, refunds may still apply where required by law or if JD Webcraft is unable to deliver the agreed service as promised (case-by-case). Non-refundable terms are generally stronger when they are clear and reasonable and reflect real costs rather than penalties.
B. Mid-project cancellation by the client
If you cancel after work has started:
- The initial payment is typically retained, and
- You will be charged for work completed up to the cancellation date (pro-rated or milestone-based), with any unpaid balance due.
C. If we cancel (rare)
If JD Webcraft must cancel the project for reasons not caused by client breach, we will provide an appropriate resolution, which may include refunding the unused portion of fees paid (depending on work already completed).
10. Retainer fulfillment (monthly)
If you are on a monthly retainer:
- Fulfillment occurs through ongoing services delivered during the billing month (as defined in the retainer agreement).
- Unused retainer time is not refundable and does not roll over unless explicitly stated in writing.
11. Chargebacks and payment disputes
Before filing a chargeback, you agree to contact hello@jdwebcraft.com so we can resolve the issue quickly. We may provide proof of work delivered (messages, approvals, staging links, project files, timestamps, invoices) to payment processors when disputes arise.
Chargebacks filed for completed or in-progress work may be treated as a contract dispute and could result in immediate suspension of access/support until resolved.
12. Digital product fulfillment (if sold)
A) Delivery method
Digital products are fulfilled by:
- Instant download, and/or
- Email delivery link, and/or
- Account/portal access (if implemented)
B) Refunds for digital products
Because digital products are delivered immediately and cannot be “returned,” digital product purchases are generally non-refundable. Exceptions may be made if:
- the product was not delivered due to a technical issue we cannot resolve, or
- the file is materially defective and we cannot provide a working replacement.
13. Hosting/domain inclusions (if applicable)
Some packages may include hosting/domain support; inclusions depend on your plan. If hosting/domain is included:
- The client owns the hosting account and domain unless agreed otherwise.
- Third-party provider uptime and outages are outside our control.
14. Migration/transfer requests and fees
If you request migration away from our setup or between providers/platforms, a migration fee may apply.
Typical migration cost ranges
Migration pricing varies by complexity—from small/basic moves to complex e-commerce or platform re-builds. For budgeting, you’ll commonly see ranges like:
- Basic WordPress migrations: roughly $200–$400
- Business sites with integrations: roughly $300–$1,000
- E-commerce migrations: roughly $800–$3,000+
Suggested JD Webcraft approach (simple + fair)
We recommend pricing migrations as:
- Base migration fee (covers planning, full backup, transfer, DNS guidance, testing)
- Add-ons for complexity (e-commerce, memberships, multilingual, heavy integrations, redirect mapping, email deliverability, custom code)
15. Contact
For fulfillment, delivery, cancellation, or refund questions:
hello@jdwebcraft.com
