Architectural Guide to OSP Product Configuration
When building items in Edlio Payments (OSP), bookkeepers frequently ask whether to configure options using Product Variations or Custom Form Fields, how to schedule automatic sales windows, and how to safeguard transaction accounting. This guide outlines the strategic decision framework for optimal product setup.
đĄ Best-Practice Adoption Tip: Follow this rule of thumb: If the choice changes the price or tracks inventory per sku, use Variations. If the choice is informational (such as custom engraving text, emergency contact info, or a permission agreement), use Form Fields.
â ď¸ Price Type Rule for Variations: Product Variations require Fixed Pricing. Items with Variable Pricing (where the purchaser enters their own dollar amount, such as open donations) cannot be used with variations and will not appear in variation setup.
Decision Matrix: Variations vs. Form Fields
Requirement | Recommended Tool | Common School Examples |
Options change the item price (Fixed Pricing only) | Product Variations | Apparel sizing with plus-size surcharges, ticket tiers (Adult vs. Student vs. VIP). Requires Price Type: Fixed. |
Collecting text, dates, or answers | Custom Form Fields | Student ID confirmation, homeroom teacher, dietary restrictions, emergency contact name and phone. |
Bulk purchase discounts | Volume Pricing | PE Uniform bundles (buy shirt + shorts for discount), multi-sibling athletic camp registration. |
Managing Sales Windows and Expirations
Avoid leaving stale products visible in your store by configuring automatic sales windows:
Date Available: Sets the exact morning the item becomes visible and purchasable.
End Date: Sets the exact cutoff date and time. When the end date passes, the item automatically moves out of the active store view, preventing late payments for catering headcounts, yearbook orders, or bus seat reservations.
Related Articles