Questions? We've got answers.

PartyShare provides the marketplace experience, account tools, listing discovery, messaging, and the supported booking workflow. The vendor shown on each listing owns or controls the inventory and is responsible for the listing details, availability, pickup or delivery, and fulfillment. Review the listing and vendor-specific terms before you request or confirm a booking. Contact PartyShare support when the marketplace flow, payment record, or an unresolved transaction issue requires help.

Instant Booking is available only when a listing has earned that configuration and the selected details pass current availability and policy checks. Request to Book sends the renter’s proposed booking to the vendor for action. Request a Quote is intended for details that require pricing or fulfillment review. Follow the action shown on the listing and do not assume every item is instantly bookable. Contact support if the displayed method and next step conflict.

Useful questions include what is included, dimensions, quantities, delivery eligibility, setup requirements, access limitations, timing, and any vendor-specific policy that is not already clear. Keep transaction details in PartyShare messaging so the parties and support team can refer to the same record. A vendor remains responsible for answering questions about its inventory and fulfillment. Contact PartyShare support for platform errors, prohibited requests, or an unresolved transaction issue.

During Phase 1, a transaction must remain within one vendor boundary even when it contains several items from that vendor. Do not describe one unified multi-vendor checkout as a launch feature. Review the confirmation for the vendor, items, quantities, fulfillment method, amounts, and next steps. Separate vendors require separate transaction records unless PartyShare formally changes the Phase 1 architecture. Contact support immediately if a confirmation is missing or contains the wrong vendor or items.

The vendor is responsible for the pickup location, approved pickup window, identity or order verification, inventory handoff, and any listing-specific instructions. The renter should arrive as agreed, inspect the items, confirm quantities and included accessories, and document material condition issues before leaving. PartyShare provides the transaction record and support pathway but does not operate every pickup location. Contact support if the confirmed instructions are missing or the parties cannot resolve a handoff problem.

Each vendor controls its service area, delivery method, fee structure, delivery window, minimum order, setup or breakdown options, and access requirements. Review all disclosed charges and conditions before committing, including stairs, elevators, loading restrictions, parking, exact-address eligibility, and whether setup is included or optional. PartyShare displays the vendor’s supported configuration and records the selection. Message the vendor before booking when access or setup is complex, and contact support when the confirmed terms are not honored.

Compare the items with the booking record, confirm variants and accessories, and note visible wear or damage that could later be disputed. Capture clear photos at handoff and again at return when the workflow supports them. The vendor is responsible for presenting the correct inventory and recording its condition; the renter is responsible for promptly documenting discrepancies. Use the order record or messaging for written notice. Contact support when the parties cannot resolve a material mismatch or safety concern.

Eligibility should be based on the approved business, identity, category, geography, inventory, fulfillment, and policy requirements rather than account creation alone. Vendors must provide truthful business and service-area information and operate only where they can fulfill. PartyShare may prioritize categories and locations with verified demand or supply gaps. Start the vendor application and provide the requested details. Contact Vendor Success when the business model, inventory ownership, or service area does not fit the standard form.

The onboarding program should collect the approved business name, address or service information, contact details, identity and payment onboarding status, provider profile, fulfillment configuration, and policy choices. Verification is not a blanket guarantee about every vendor or item; PartyShare should describe only the checks actually completed. Follow the progress tracker and resolve missing requirements. Contact Vendor Success when a verification step fails or when the business cannot provide a required record.

PartyShare’s blueprint recommends a 100-point readiness model and an 85-point threshold, but verification, payment onboarding, fulfillment terms, policies, and current availability remain mandatory even when the score is high. A vendor is not launch-ready merely because it created an account or one draft listing. Complete the progress checklist, publish the required viable catalog, and pass a test inquiry or transaction. Vendor Success should review exceptions before the vendor is promoted.

Choose the correct category, write a factual title and description, identify included items, add specifications, quantities and variants, configure pricing, select pickup or delivery, add lead time and buffers, choose approved policy settings, upload useful images, and preview the result. A listing below the quality threshold should remain a draft or enter review rather than appear publicly. Contact Vendor Success for catalog assistance or a field that does not fit the inventory.

The title should name the rentable item without stuffing locations, claims, or repeated keywords. The description should explain what is included, important dimensions or capacity, event uses, visible limitations, and fulfillment details that are not captured elsewhere. Use structured attributes for variants, specifications, and operational rules instead of hiding mandatory information in prose. Choose the approved taxonomy and request a category review rather than forcing the item into an inaccurate category.

Provide one clean primary image, multiple helpful angles, scale or setup context where useful, included accessories, and visible wear when relevant. Avoid large watermarks, unrelated scenes, duplicate images, poor lighting, and text-heavy graphics. Stock photography may be acceptable only when the policy permits it and the image cannot be mistaken for the exact item, condition, or included setup. Replace any image that fails quality review or creates a false expectation.

Set the base rental duration and price, additional-day rules, quantity tiers, variant pricing, and optional add-ons in the designated fields. Add-ons should be genuinely optional and should describe what the renter receives. Do not hide unavoidable charges or use an add-on to bypass required fee fields. Test a realistic renter-facing order and confirm the itemization. Contact Vendor Success when pricing depends on complex labor, delivery, or a custom quote rather than a standard rule.

Before pickup or delivery, inspect and photograph the inventory, confirm accessories, quantities, address or pickup location, access restrictions, timing, and contact person. At handoff, verify the renter or order, record the time, and capture the required acknowledgement. At return, inspect promptly and photograph exceptions before opening a supported claim. PartyShare supplies the workflow and record; the vendor remains responsible for accurate and safe fulfillment. Contact Vendor Success for any failed handoff or material exception.

Every vendor who joins during the beta gets a commission holiday: 0% commission until either 6 months have passed since your account was created or your completed bookings reach $5,000 — whichever comes first. Only completed bookings count (accepted, paid, and fulfilled); cancelled, declined, expired, and refunded bookings never count toward the $5,000. Volume is measured on the booking subtotal, before taxes, delivery, and other fees. After either limit is reached, standard commission applies to new bookings going forward — it never changes what you already earned on a confirmed booking.

The launch sequence prioritizes credible local supply and completed, successfully fulfilled bookings rather than registrations or traffic alone. PartyShare will open only supported DMV geographies and categories, monitor early transactions, correct recurring problems, and expand one dimension at a time. Beta participants may receive concierge assistance and be asked for feedback. Limited availability is intentional and should not be described as universal market coverage.

Stable FAQ IDs should remain unchanged when display wording improves. High-risk payment, policy, verification, safety, and contract answers require the appropriate human review before publication. Search data, support contacts, onboarding errors, and repeated escalations should feed the correction queue. Meaningful updates should change the reviewed date and trigger schema, link, analytics, and regression checks. Unresolved answers should remain unpublished instead of being filled with assumptions.

The vendor is responsible for accurate listing details, stock, service area, fulfillment options, included services, and the approved policy choice shown for the transaction. PartyShare is responsible for the marketplace controls, consistent disclosures, and support process, not for making every vendor identical. Compare the exact listing and checkout details rather than relying on a general FAQ. Contact support when a vendor-specific term conflicts with PartyShare’s controlling terms or changes after commitment.

Ask the vendor about item dimensions, included accessories, availability, pickup or delivery execution, setup, and listing-specific operational details. Ask PartyShare about account access, payment records, status errors, off-platform requests, policy interpretation, unresolved transaction problems, disputes, and safety escalation. During beta, PartyShare may monitor early bookings more closely and provide concierge help. That support does not transfer the vendor’s obligation to fulfill accurately.