內容簡介
Sidcraft Commerce 將 Sidcraft Page Builder 轉變為完整的網路商店，無需依賴 WooCommerce 或其他電子商務外掛，提供簡易的產品設計與管理功能，讓使用者輕鬆建立線上商店。
【主要功能】
• 產品設計與管理：可在 Sidcraft Page Builder 中新增及編輯產品
• 驗證顧客評價：顧客可留下帶有「驗證購買」標籤的評價
• 圖片標籤：為產品添加 HOT、POPULAR、Sale 等標籤
• 商品選項：提供尺寸、附加選項及特殊指示
• 優惠券功能：設定折扣百分比或固定金額的優惠券
• 數位下載：支援銷售電子書、音樂、軟體等數位產品
外掛標籤
開發者團隊
② 後台搜尋「Sidcraft Commerce for Sidcraft Page Builder」→ 直接安裝（推薦）
原文外掛簡介
Sidcraft Commerce turns Sidcraft Page Builder into a complete store. It needs only Sidcraft Page Builder — no WooCommerce or other e-commerce plugin.
Design products in Sidcraft Page Builder: Add New Product opens the builder, and its Product data panel sets the price, sale price, SKU, stock, badge, categories, image and short description. Existing products get “Edit with Sidcraft Page Builder”.
Products with prices, sale prices (shown above the struck-through regular price), SKU, stock tracking, featured flag and categories.
Verified-customer ratings and reviews: shoppers click a star, enter their order number and order email, and write a review. Reviews show with a “Verified purchase” badge, a rating breakdown and the average on the product page.
Image badges per product (HOT, POPULAR, Sale, Clearance) and an automatic “Sold Out” label on out-of-stock products.
Item options: sizes, extras, spice levels or special instructions on any product, each choice optionally adding to the price (for example “Large +4”, “Extra cheese +1.50”). Choices show in the cart, checkout, emails and the order screen.
Coupons: a percentage off or a fixed amount off, with optional minimum spend, expiry date and usage limit.
Cart stored server-side per visitor; prices are always recalculated from the product.
Payments: PayPal with Pay in 4 (Pay Later) and Venmo; Stripe for cards, Apple Pay, Google Pay, Klarna, Afterpay / Clearpay and Affirm; Razorpay and PayU for India (UPI, cards, netbanking, wallets); Mercado Pago for Latin America (cards, Pix, boleto, OXXO, installments). Customers pay on each provider’s secure page or buttons; card numbers never touch your site.
Digital downloads: sell e-books, music, software, courses or printables. Tick “Downloadable” on a product and add one or more files (upload them, pick them from the media library or link to files hosted elsewhere), with an optional download limit and expiry. Tick “Virtual” for products with nothing to ship: a cart of virtual products skips the shipping cost and the address fields.
Each buyer gets a private link per file on the order-received page, in the order emails and on a My downloads page (My Downloads Unit or [sidccofo_downloads]). Access starts when the order is paid (or when it is marked Completed), pauses when it is cancelled or refunded, and past buyers get files you add later. On the order screen, change downloads left and expiry, revoke or restore access, give access to another product’s files, see the download history and email the links again. Store → Download log lists every order with downloads.
Download security: uploads go to a protected folder with random file names; files are only served from approved folders and in file types WordPress allows; force download (resumable), X-Sendfile / X-Accel-Redirect / X-LiteSpeed-Location or redirect; optional login or email confirmation before downloading; optional IP logging, included in WordPress’s personal data export and erase tools.
Gift cards: sell them as products (preset amounts and/or a custom amount, recipient, message, optional send date) or issue them by hand. Recipients get an email with the code; customers redeem one or more cards in the cart or at checkout, and unused balance stays on the card.
Shipment tracking: add tracking numbers on the order screen. Links are built automatically for Australia Post, Canada Post, City-Link Express, DHL, DPD, Fastway South Africa, FedEx, OnTrac, Parcelforce, Polish carriers (Poczta Polska, InPost, DPD Polska, DHL Parcel Polska, GLS), Royal Mail, SAPO, TNT Express (consignment and reference), UPS and USPS, or use any carrier with a custom link.
Developers can add any payment method (a local bank, a regional wallet, a proprietary system) by extending one PHP class; settings, return and webhook URLs are provided. See docs/example-gateway.php.
Orders in the admin with statuses, history and stock reserved when the order is placed. Two buyers cannot both take the last unit. Cancelled and Refunded put the remaining units back. A dispute keeps them reserved until it is lost.
Partial refunds record the amount and return only the quantities you name. A refund that covers the order total marks the order Refunded. Stripe and PayPal refund and dispute notifications are applied once.
Guest checkout can create an account, and a later login with the same email attaches guest orders placed on 1.0.9 or newer.
Store → Export catalog downloads products, categories, prices, SKU, stock and item options as JSON, without the page-builder layout.
Order emails to the customer and the shop owner, including a “Your order has shipped” email with tracking links.
Events and tickets (new in 1.2.0): Events menu with date and time, venue, address and map, online details (Zoom, Google Meet, any link), organiser, WhatsApp chat and group links, and any number of ticket types.
Ticket and inventory control: event-wide capacity plus per-ticket limits, minimum and maximum per order, sales start and end, and tiered prices by attendee type (Adult, Child, Student, VIP…). Dynamic pricing rules per ticket: early-bird and late prices by date, demand prices (“after 75%”), and group rates (“qty 5”).
Tickets are sold through hidden product placeholders, so the store’s checkout, currency, taxes, coupons, gift cards, stock locking, refunds and every payment method work for tickets.
Attendee details at checkout: name, email and phone per ticket, plus custom fields (text, long text, email, phone, number, date, dropdown, choose one, checkboxes and file uploads, stored privately).
Automated delivery: paid orders issue tickets with unique codes, QR codes and/or Code 128 barcodes. Buyers get an email with embedded QR codes, PDF tickets and a calendar file; attendees can get their own copy; reminder emails go out before the event; optional WhatsApp Cloud API message.
Check-in: scan the QR code with any phone camera (staff see a Check in button), use the Check-in screen with the device camera or a USB scanner, or check in from the Attendees list. Cancelled or refunded orders cancel their tickets; partial refunds cancel just the refunded tickets.
Calendars: “Add to Google Calendar” and .ics links, plus a subscription feed that Google Calendar, Apple Calendar and Outlook keep in sync. Zoom meetings can be created automatically with a Zoom Server-to-Server OAuth app.
Display events with Units for Sidcraft Page Builder, Gutenberg blocks or shortcodes: Event List, Event Calendar, Event Details, Event Tickets, Event Map and My Tickets ([sidccofo_event_list], [sidccofo_event_calendar], [sidccofo_event_tickets event_id="123"]…). Attendees list with CSV export.
Commerce Units for Sidcraft: Product Grid, Add to Cart, Product Price, Stock Status, Product Rating, Product Reviews, Mini Cart, Cart, Checkout and Order Confirmation, plus a quick-view popup. Every Unit also works as a shortcode, e.g. [sidccofo_product_grid source="on_sale" limit="8"].
Pages stay cacheable: assets load only where a Unit is used, the cart badge fills in after load, and Cart/Checkout pages are marked no-cache automatically.
Themes can override any template by copying it from templates/ into yourtheme/sidcraft-commerce/.
External services
Payment providers are contacted only when a store owner enables them under Store → Settings → Payments and a customer chooses them at checkout (or when the provider sends a notification about a payment). Each receives what it needs to take the payment: the order ID, total and currency, and the customer’s name, email and, where the provider requires it, phone and address.
PayPal – when PayPal is enabled, the plugin sends order line items (product names, SKUs, prices, quantities), the order total, shipping, coupon discount, currency and the order ID to PayPal’s REST API (api-m.paypal.com, or api-m.sandbox.paypal.com in sandbox mode) to create and capture the payment, and to verify PayPal webhooks. This happens only when a customer chooses PayPal at checkout, or when PayPal sends a webhook. With “On-page buttons” on, the checkout page also loads PayPal’s JavaScript SDK from www.paypal.com to show the PayPal, Pay Later and Venmo buttons and the Pay in 4 message. PayPal terms: https://www.paypal.com/legalhub/useragreement-full — privacy: https://www.paypal.com/myaccount/privacy/privacyhub
Stripe (cards, Apple Pay, Google Pay, Klarna, Afterpay / Clearpay, Affirm) — When Sidcraft Builder Pro installed api.stripe.com creates a Checkout Session for the order total and is asked again to confirm the payment; Stripe sends signed webhooks back. The customer pays on checkout.stripe.com. Terms: https://stripe.com/legal/ssa — privacy: https://stripe.com/privacy
Razorpay – When Sidcraft Builder Pro installed api.razorpay.com creates a payment link for the order total and is asked again to confirm it; Razorpay sends signed webhooks back. Terms: https://razorpay.com/terms/ — privacy: https://razorpay.com/privacy/
PayU India – When Sidcraft Builder Pro installed the checkout form is posted to secure.payu.in (test.payu.in in test mode); payments are confirmed with PayU’s verify_payment API on info.payu.in. Terms: https://payu.in/tnc-new/ — privacy: https://payu.in/payu-payments-privacy-statement
Mercado Pago – When Sidcraft Builder Pro installed api.mercadopago.com creates a Checkout Pro preference for the order total; payments are read back from the same API when the customer returns or a notification arrives. Terms: https://www.mercadopago.com.ar/developers/en/docs/resources/legal/terms-and-conditions — privacy: https://www.mercadopago.com/privacy/privacy-notice/1.1
Events (optional; used only when the store owner sets them up):
Google Maps – event pages with a venue embed a map from maps.google.com (or the Google Maps Embed API at www.google.com/maps/embed when a key is entered), which receives the venue address or coordinates and the visitor’s IP address. Terms: https://cloud.google.com/maps-platform/terms — privacy: https://policies.google.com/privacy
OpenStreetMap – when chosen instead, the map is embedded from www.openstreetmap.org with the venue coordinates. Terms: https://wiki.osmfoundation.org/wiki/Terms_of_Use — privacy: https://osmfoundation.org/wiki/Privacy_Policy
Google Calendar – “Add to Google Calendar” and “Subscribe” are plain links to calendar.google.com, opened only when a visitor clicks them; they carry the event name, time, place and description.
Zoom – only when Zoom credentials are entered under Events → Settings and “Create the Zoom meeting for me” is ticked, the event name, start time, time zone, duration and summary are sent to zoom.us (OAuth) and api.zoom.us to create or update the meeting. Terms: https://www.zoom.com/en/trust/terms/ — privacy: https://www.zoom.com/en/trust/privacy/
WhatsApp Cloud API (Meta) – only when enabled under Events → Settings, the buyer’s phone number, first name, event name, date and ticket link are sent to graph.facebook.com when tickets are issued. Terms: https://www.whatsapp.com/legal/business-terms — privacy: https://www.whatsapp.com/legal/privacy-policy
WhatsApp links – “Chat on WhatsApp”, “Share on WhatsApp” and group links are plain links to wa.me / chat.whatsapp.com, opened only when clicked.
Developers: add-ons
Sidcraft Commerce is built to be extended by other plugins: a restaurant menu, bookings, a print shop. Add-ons can add item options in code, register their own order statuses (for example Preparing, Ready for pickup, Out for delivery, each with its own customer email), add checkout fields (pickup time, delivery notes), block ordering outside opening hours, add Units for Sidcraft Page Builder, settings sections and emails. The guide is in docs/ADDONS.md, with a complete restaurant example in docs/example-addon.php.
Developers: custom payment gateways
Extend \SidcraftCommerce\Payments\Gateway (the equivalent of WooCommerce’s WC_Payment_Gateway) and add it with the sidcraft_commerce_gateways filter. Implement get_id(), get_default_title() and process_payment(); return fields from get_settings_fields() and they appear on Store → Settings → Payments. return_url() and webhook_url() point at ready-made REST routes that call your handle_return() and handle_webhook(); remote_json() calls JSON APIs; $order->payment_complete() marks an order paid. A complete, commented example is in docs/example-gateway.php.
