PortionMargin

Support

Find the right support path without sending app data automatically.

Use this page to choose a support category, prepare safer details, and separate local app data from the launch support email path.

Before sharing details

The current support page does not send website form data.

PortionMargin quote details, ingredient costs, customer notes, business settings, and pricing assumptions remain local to the app by default. This static support page has no form, CRM, ticketing system, backend, or automated chat assistant.

Launch support is email-only at support@portionmargin.com. Include only the smallest detail needed to explain the issue. Avoid sending sensitive customer, quote, ingredient, or business data unless it is needed for the request.

Email support

Support categories

Match the question to the smallest useful context.

Calculations

Check the entered costs, labor, overhead, extras, target margin, rounding, and quote validity before relying on the total.

Ingredients

Review package cost, unit, recipe usage, conversion assumptions, and whether an ingredient price is outdated.

Quotes

Compare internal review details with the customer-safe quote output before sharing price, validity, or customer notes.

Invoices and user-authored terms

Add and review your own invoice notes, payment terms, tax wording, or legal text. PortionMargin does not provide legal templates or jurisdiction-specific clauses.

History

Confirm the saved quote, reused order context, and copied values still match the current customer request.

Settings and defaults

Review business details, quote defaults, visibility choices, and whether default assumptions still fit the order.

Privacy and local data

Distinguish app-local quote, customer, ingredient, and business data from any details a user chooses to provide through the launch support email path.

App Store purchase or billing

Use Apple purchase history and App Store subscription tools for billing questions; PortionMargin support should not receive card numbers or payment credentials.

Bug reports

Record the app version, device model, iOS version, screen name, and a short reproducible sequence without including private customer details.

Support priority

Separate current app help from optional feedback or update interest.

Use the support categories for app issues that block pricing, quote review, saved context, billing review, or bug diagnosis. Optional feedback, feature ideas, and update-interest messages belong to the non-urgent feedback route, not the support path.

Open Feedback and updates

Guided triage

Prepare a support note locally before emailing support.

  1. 1

    Choose the category

    Start with calculations, ingredients, quotes, history, settings/defaults, privacy/local data, App Store purchase or billing, or bug reports.

  2. 2

    Describe only the needed context

    Include the screen, expected behavior, actual behavior, and whether the issue repeats. Keep customer names, business secrets, ingredient supplier details, and quote values out unless they are essential.

  3. 3

    Email support when needed

    The support email opens your email app with a short template. Sending the message is your choice, and app-local data remains on your device unless you include it.