Aehr Test Systems' 2026 Q3 Earnings Call: Capacity Claims and Memory Order Uncertainty Spark Contradictions

Date of Call: Apr 7, 2026

Financials Results

• Revenue: $10.3 million, down 44% from $18.3 million prior year period
• EPS: Non-GAAP net loss of $0.05 per diluted share, compared to net income of $0.07 per diluted share in the prior year
• Gross Margin: 36.5% Non-GAAP, compared to 42.7% a year ago

Guidance:

• Full-year fiscal 2026 revenue expected on the high side of the $45 million-$50 million range.
• Non-GAAP net loss per diluted share expected between negative $0.13 and negative $0.09 for the full fiscal year.
• Expect to return to profitability on a non-GAAP basis in the fourth quarter of fiscal 2026.
• Expect gross margin to improve with increased manufacturing activity.
• Bookings for second half of fiscal year expected on the high side of the $60 million-$80 million range.

Business Commentary:

Strong Bookings and Backlog Growth:

• Aehr Test Systems reported quarterly bookings of $37.2 million for Q3 fiscal 2026, significantly higher than $6.2 million in Q2, with an additional $12.2 million in bookings received in the first five weeks of Q4. This resulted in an effective backlog of $50.9 million, a record for the company.
• The growth was driven by multiple purchase orders for FOX systems, WaferPaks, and FOX WaferPak Auto Aligners from customers in AI, silicon photonics, and silicon carbide applications.

Wafer-Level Burn-In Demand:

• The company received a $14 million follow-on production order for FOX-XP wafer-level burn-in systems and a new major order for silicon photonics, highlighting strong demand in this segment.
• The demand is driven by the increasing complexity and power requirements of semiconductor devices, especially AI processors, necessitating comprehensive testing and burn-in solutions for reliability.

Package-Level Burn-In Expansion:

• Aehr Test Systems secured a production order with a hyperscale customer for the next generation of high-power AI processors, expanding its installed base and consumable opportunities.
• The growth is attributed to the customer's need to ensure reliability and performance of advanced multi-chip packages used in AI and data center applications.

Memory Market Opportunities:

• The company is progressing in engagements with key memory suppliers, focusing on developing new memory-optimized blades for its FOX systems to support High Bandwidth Memory (HBM) and other memory standards.
• This is driven by the aggressive roadmap transitions in HBM standards and the need for cost-effective, high-volume burn-in solutions for memory devices used in AI GPUs.

Manufacturing Capacity Expansion:

• Aehr Test Systems is increasing its manufacturing capacity by utilizing a contract manufacturer, aiming to produce over 20 additional Sonoma systems per month.
• This expansion is necessary to support the growing demand for its burn-in systems and to facilitate future growth in both wafer-level and package-level burn-in solutions.

Sentiment Analysis:

Overall Tone: Positive

• CEO stated, "We’re very pleased with the strong momentum in our business across multiple market segments, highlighted by more than $37 million in quarterly bookings and a book-to-bill ratio exceeding 3.5x." Also noted, "We believe we’re well positioned to exit the fiscal year...with a strong backlog and deliver significant revenue growth in fiscal 2027."

Q&A:

• Question from Mark Schutter (William Blair): Congrats on all the progress, especially with the hyperscaler. I’m curious how you guys are looking at this internally and what percentage of GPUs or ASICs or XPUs do you think are burnt in today? How do you guys size the vector space?
  Response: Management is surprised by how many devices are not yet in production burn-in; estimates suggest only ~5-20% of certain devices like ASICs are currently burned in, but the trend is moving strongly toward adoption due to increasing device power and the availability of cost-effective solutions like Aehr's.

• Question from Mark Schutter (William Blair): To zero in a bit on your hyperscaler customer, can you bring us a little into the room a bit here and what was the decision process to go with package level, right? Not wafer level anymore, it’s package level versus wafer level. Do you see a transition potentially with this customer to move to wafer level?
  Response: The customer initially chose package-level burn-in, but as they ramp new devices, there is a progression and interest in moving to wafer-level burn-in for certain products, especially when cost-effectiveness and yield benefits are clear, as seen with the third-generation device discussions.

• Question from Christian Schwab (Craig-Hallum): Have you had enough time to give some thought to the range of potential outcomes over a multi-year timeframe...?
  Response: Yes, management has thought about multi-year potential, describing the total addressable market (TAM) as multi-hundreds of millions to billions of dollars annually across package and wafer-level burn-in, with significant growth opportunities in AI, memory, and other segments.

• Question from Maxwell Michaelis (Lake Street Capital Markets): We look at the demand environment from the package level and wafer level. Demand seems strong on both sides of the business here, but to me, it looks like wafer level is outpacing on the demand side and maybe the order side. Can you let me know if I’m wrong there?
  Response: While demand is strong for both, wafer-level engagements can be more complex and involve a learning process, whereas package-level decisions are often easier and faster. Over time, wafer-level adoption is increasing as customers become more familiar with the solutions.

• Question from Larry Chlebina (Chlebina Capital): Your contract manufacturer that you’re starting up, when does that start, and when will it be fully capable of doing your 20 Sonomas a month?
  Response: First products are expected to ship this quarter (through May), with full readiness by late summer to support the anticipated Sonoma ramp. This is in addition to Fremont production, which will continue for large volume orders and FOX products.

• Question from Larry Chlebina (Chlebina Capital): Did I hear you say that your first expected XP sales to an HBM customer will be this calendar year or next fiscal year, 2027?
  Response: Management was cautious on timing but indicated discussions with HBM customers are active and promising, with potential overlap between flash and HBM engagements. An order would be a significant uptick.

Contradiction Point 1

Manufacturing Capacity Target

Contradictory statements on system manufacturing capacity relative to demand forecasts.

Larry Chlebina (Chlebina Capital) - Larry Chlebina (Chlebina Capital)

2026Q3: Full capacity is targeted by late summer to support the expected Sonoma ramp. - Gayn Erickson(CEO)

When will the new contract manufacturer reach full capacity of producing 20 Sonoma systems monthly, and will production stay in Fremont? - Christian Schwab (Craig-Hallum)

20260109-2026 Q2: The company has capacity to manufacture up to 20 systems per month... if needed, though this exceeds current forecasts. - Gayn Erickson(CEO)

Contradiction Point 2

Customer Order Timeline for Memory Market

Inconsistency regarding the expected timing for the first order from a key memory customer.

Did Larry Chlebina (Chlebina Capital) participate in the earnings call? - Larry Chlebina (Chlebina Capital)

2026Q3: An order would be a 'good uptick,' but specific timing depends on finalizing development agreements... - Gayn Erickson(CEO)

Okay, let's see. The user wants me to rewrite the input into one concise earnings-call question. The input is: "Will the first sales to an HBM memory customer occur in calendar 2026 or fiscal 2027?" First, I need to check the rules. The output must be exactly one line, only the final question text, end with a question mark if possible. No explanations or prefaces. If the input isn't a question or is too vague, output it as-is.The input is already a question. It's asking about the timing of first sales to an HBM memory customer, specifying two timeframes: calendar 2026 or fiscal 2027. The terms "calendar" and "fiscal" are important here. The user wants it concise. Maybe "HBM memory customer" can be simplified? But "HBM" is a specific term, probably referring to High Bandwidth Memory, so it's better to keep it as is.Is there a way to make it more concise without losing meaning? The original question is already pretty concise. Maybe combine the two timeframes into a single phrase. Instead of "calendar 2026 or fiscal 2027," perhaps "calendar 2026 versus fiscal 2027." But the original uses "or," so maybe that's okay. Wait, the original uses "calendar" and "fiscal" years. The question is whether the first sales will happen in either of those. The user might want to know if it's one or the other. The original question is clear. I don't see a need to change it. The input is already a valid, clear question. So according to the rules, if it's already a clear question, do I need to modify it? The instruction says to rewrite into one concise question. But if the input is already a clear question, maybe output as-is. Wait, the rules say: "If the input is NOT a question, is too vague, or lacks enough information to form a clear earnings-call question, output the input EXACTLY as-is, with no modification." Since the input is a clear question, perhaps I should leave it as is. But the user says "rewrite the input into one concise earnings-call question." So maybe even if it's a question, they want it rewritten to be more concise. Let me check the example. Suppose the input is a question but can be made more concise. For example, "What are the sales numbers for the last quarter?" could be "What were Q4 sales?" But in this case, the original question is already pretty concise. Maybe there's no need to change. However, the user might want to ensure that the output is exactly one line and ends with a question mark. The original ends with a question mark, so that's good. The output must be exactly one line. The original is one line. So perhaps the correct output is the input itself. Because it's already a clear, concise question. Therefore, according to the rules, since it's a valid question, output as-is. Wait, but the instruction says "rewrite the input into ONE concise earnings-call question." So maybe even if it's a question, we need to make it as concise as possible. Let me check the original again. The original is: "Will the first sales to an HBM memory customer occur in calendar 2026 or fiscal 2027?" Maybe "HBM memory customer" can be shortened to "HBM customer" since "HBM" implies memory. Also, "occur in" could be "happen in" but that's not shorter. Alternatively, "Will first HBM memory sales to a customer occur in calendar 2026 or fiscal 2027?" But that's rephrasing. However, the original is already clear. Maybe the user wants to avoid redundancy. The original says "sales to an HBM memory customer." Since HBM is High Bandwidth Memory, maybe "HBM customer" is sufficient. So "Will the first sales to an HBM customer occur in calendar 2026 or fiscal 2027?" That's slightly shorter. But is that acceptable? The original specifies "HBM memory customer," but "HBM" is a type of memory, so "HBM customer" might be enough. However, changing the input could alter the meaning. The user might want to keep the original phrasing. Since the input is already a clear question, perhaps the correct action is to output it as-is. Because the rules state that if it's a valid question, you don't need to modify. Wait, the rules say: "If the input is NOT a question, is too vague, or lacks enough information to form a clear earnings-call question, output the input EXACTLY as-is, with no modification." So if it is a valid question - Larry Chlebina (Chlebina Capital)

20260109-2026 Q2: The customer is expected to provide feedback and potentially place an order within the next few months. - Gayn Erickson(CEO)

Contradiction Point 3

Multi-Year Forecast Certainty and Growth Outlook

Shift from cautious, near-term outlook to more confident, long-term TAM focus.

Christian Schwab (Craig-Hallum) - Christian Schwab (Craig-Hallum)

2026Q3: The underlying TAMs are enormous, with billions of dollars spent annually on burn-in... - Gayn Erickson(CEO)

What are the potential multi-year outcomes considering growth in target markets and possible entry into the memory market? - Christian Schwab (Craig-Hallum Capital Group LLC, Research Division)

2026Q1: The company is confident in future orders but withholding specific guidance due to ongoing tariff uncertainty. - Gayn Erickson(CEO)

Contradiction Point 4

Order Visibility and Engagement Status for HBF/Memory Customer

Inconsistent portrayal of engagement progress and order certainty with a key memory customer.

Larry Chlebina (Chlebina Capital) - Larry Chlebina (Chlebina Capital)

2026Q3: The company is engaged in discussions with HBM customers... An order would be a 'good uptick,' but specific timing depends on finalizing development agreements... - Gayn Erickson(CEO)

Okay, let me try to figure out how to handle this. The user wants me to rewrite the input into a single concise earnings-call question. The input is: "Will the first sales to an HBM memory customer occur in calendar 2026 or fiscal 2027?" First, I need to check if the input is already a clear question. It is, so the next step is to make sure it's concise. The original question is pretty straightforward, but maybe I can make it more concise without losing meaning. The key elements here are "first sales," "HBM memory customer," and the two time frames: calendar 2026 vs. fiscal 2027.I should check if "HBM memory customer" is the correct term. HBM usually stands for High Bandwidth Memory, so that's specific. The user might be referring to a company's customer in that sector. The original question is asking about when the first sales will happen, giving two options. The original question uses "calendar 2026" and "fiscal 2027." Depending on the company's fiscal year, fiscal 2027 might start before calendar 2026 ends. For example, if a company's fiscal year starts in July, fiscal 2027 would include July 2026 to June 2027. So the question is distinguishing between the calendar year and the fiscal year. The task is to make this into one concise question. The original is already a single question, but maybe it can be phrased more succinctly. Let me see. The user wants exactly one line, no prefaces, just the question ending with a question mark if possible. Is there any redundancy? "Will the first sales to an HBM memory customer occur in calendar 2026 or fiscal 2027?" The words "an" before HBM memory customer is correct. Maybe "HBM memory customer" can be shortened? If HBM is a known term in the industry, perhaps it's okay. Alternatively, maybe "HBM customer" is sufficient if the context is clear. But the original specifies "memory," so maybe that's important. The user's instruction says to output exactly as-is if it's not a question, too vague, or lacks info. Since the original is a clear question with specific time frames, I can proceed to rewrite if possible.Wait, the original is already a question. The task is to rewrite it into one concise earnings-call question. So maybe the user wants it to be even more concise. Let me check the length. The original is 19 words. Maybe it can be shortened. For example, "When will the first sales to an HBM memory customer occur: calendar 2026 or fiscal 2027?" That's 17 words. But the original uses "occur in" which is correct. Alternatively, "Will first HBM memory customer sales occur in calendar 2026 or fiscal 2027?" That's 14 words. But does that lose any meaning? "First sales to an HBM memory customer" becomes "first HBM memory customer sales." It's slightly different but still conveys the same meaning. However, the original uses "first sales to an HBM memory customer," which is more precise. The rewritten version might be acceptable. But the user's example might prefer the original structure. Since the user says to output exactly as-is if it's a clear question, but if a rewrite is possible, end with a question mark. The original ends with a question mark, so if the rewrite is possible, it must end with one. The original is already a valid question. The user's instruction says if the input is a clear question, rewrite it into one concise question. So perhaps the original is acceptable, but maybe there's a more concise way. Alternatively, maybe the user wants to combine the two time frames into a single question. The original does that with "or." So perhaps it's already concise. Maybe the answer is to leave it as is because it's already a clear, concise question. However, the user might expect some rephrasing. Wait, the user's instruction says "Rewrite the input into ONE concise earnings-call question." So the input is a question, and we need to rewrite it into a more concise version. Let me try again. Original: "Will the first sales to an HBM memory customer occur in calendar 2026 or fiscal 2027?" Possible rewrite: "When will the first HBM memory customer sales occur: calendar 2026 or fiscal 2027?" But the user's example might prefer the original. Alternatively, maybe the original is already the most concise. Since the user says to output exactly as-is if it's a - Christian Schwab (Craig-Hallum Capital Group LLC, Research Division)

2026Q1: A recent evaluation is for a processor with volume production expected by end of calendar 2026, requiring tools in that timeframe. Early indicators will be customer enthusiasm and successful evaluations, with the potential for large production orders... - Gayn Erickson(CEO)

Contradiction Point 5

Naming of 10% Customers

Contradiction on the company's policy for disclosing 10% customer names.

Christian Schwab (Craig-Hallum) - Christian Schwab (Craig-Hallum)

2026Q3: The updated customer list on the slide reflects current customers from the Incal package part burn-in business, not prospects. - Gayn Erickson(CEO)

Are the marquee names on the recent investor deck slide current/previous customers or prospective customers (e.g., new AI or silicon photonics customers)? - Christian Schwab (Craig-Hallum Capital Group LLC)

2025Q4: No, the new SEC rules do not require naming 10% customers, so the company will not name them unless there was a prior agreement with the customer to do so. - Gayn Erickson(CEO)