Returns & Refunds

Returns & Satisfaction Guarantee

At MicroFreshly, your satisfaction is our priority. Because microgreens are harvested fresh and are highly perishable, we do not accept physical returns. However, we fully stand behind the quality of every order and are committed to making things right if an issue occurs.

Do You Accept Returns or Offer Refunds?

Due to the perishable nature of microgreens, returns are not accepted. That said, if there is an issue related to quality, freshness, or order accuracy, we will gladly offer a replacement, store credit, or refund, depending on the situation.

Our goal is to ensure you receive products that meet the standards you expect and deserve.

What Qualifies for a Replacement, Credit, or Refund?

You may be eligible if your order:

  • Arrives damaged or spoiled
  • Contains incorrect or missing items
  • Does not meet our quality or freshness standards

To help us resolve the issue quickly, please report any concerns within 24 hours of delivery, ideally with photos of the product and packaging.

What Does NOT Qualify for Refunds or Credits?

The following situations are not eligible:

  • Improper storage or delayed refrigeration after delivery
  • Product misuse or handling after receipt
  • Custom grow orders or special requests once production has started

Our Commitment

We grow, harvest, and deliver with care, and we take pride in our service. If something isn’t right, reach out—we’re here to help and will always aim for a fair and reasonable resolution.

How to Report an Issue

If you experience an issue with your order, please contact us within 24 hours of delivery by emailing info@microfreshly.com or through our website contact form. Including photos of the product and packaging will help us resolve the issue more quickly.

Refund Processing

Approved refunds are issued to the original payment method or as store credit, depending on the situation. Refunds are typically processed within 3–5 business days after approval. Shipping fees are non-refundable unless the issue was caused by an error on our part.